i can say it takes a lot more effort than one might expect... newsletters need email conformation - slowing you down more than you expect also those emails do not have attachments... all images are links - so emails are REALLY small speaking from experience as i person that attempted i started from 2012 to show people that deleting emails in totally useless activity to save inbox space - especially on gmail currently the email box is at 357k+ emails with 11,81 GB of data being used up by emails i have stopped the experiment and deleted some as for some reason i like to use this meme email address from time to time
I think I know why each e-mail takes up more space than you expected. E-mail was originally specified to only send plain text, so attachments are bodged in by converting the binary files to text using Base64 encoding. Per Wikipedia, this “causes an overhead of 33-37%”.
@@silicalnz besides the canonical 1/3 overhead of base64 the only other overhead of the encoding is max 2 bytes for the padding for each encoding. That is, you should make different attachments each consisting of 1 byte that gets encoded into 4 bytes. Depending on the actual implementation, there could be an overhead also for the line breaks (which, incidentally, are present in SMTP base64 for some reason), but I'd argue that the multipart MIME encoding overhead of the different attachments way surpasses that line breaks overhead; not sure if the MIME overhead is accounted in the user limit, but I suspect it is not, given the empirical results showed in the video. TLDR: send more attachments in a single email
472 emails in 471 seconds is actually EXACTLY 1 email per second, not slightly better. This is because of the fencepost error in which we accidentally counted the duration of the events and forgot that the first event takes no (or minimal) time. To use a simple example, if you had managed two get 2 emails in 1 second, it could be because of the fact that the first email hit at 0 seconds (by definition) and the second email hit at 1 second (ignoring the details of exactly how Google handles 60 emails per minute throttling, which is relevant to the example, but not in practice when dealing with continuous periods of time over 60 seconds in length). So if we consider the first email to have hit at 0 seconds in (which is the definition used in the video), then after 471 seconds, we added an additional 471 emails.
0:00 is where the first second begins, and 0:01 is actually the start of the 2nd second. the final time of 7:51 ends inside the 472nd second, so it's 472 emails inside 472 seconds
@@Player-fg4ubincredibly horrible take. he didn't pick apart a joke, he gave useful information that might be interesting to someone watching a DEV CHANNEL. you can't just spam this phrase everywhere and expect it to work. to the comment op, good info
haha wheee i hope google doesn't erase all trace of me from the internet for this one haha really though :) let me know which enterprise software speedrun i should do next
You don't even need to upload it, you can be added to a shared drive and copy a 15 gig file to your drive, a TAS would probably be like 2 seconds long lol
Simple speak: Files get bigger when sent as an email. Yes, it is stupid. (Only while in an email. When you download them they are the small size again)
@@jurgennicht4626 nah it's not stupid. Base64 encoding was made for sending binary data over ascii-only protocols. SMTP was made before we even had images to send, obviously it wasn't designed with it in mind. It's actually a really fine way of extending an existing standard without altering it.
@@roshibomb4247 afaic for historical reasons only. It's just the safe way to transmit non-text data (or arbitrary data where you can't know whether it is Text or not) via a system that was designed to transmit text only. But the specification might still mandate it
More likely, a bunch of "giant" i.e long unicode characters to take up a lot of space. We can only include a 25MB attachment but we should be able to fill the rest with a lot of characters to reach the other 25 megabytes for the max of 50MB per email. It might be possible to send 2 large attachments to fill that up, but I don't know if this is possible and I have not finished watching the video
Memories of overloading Minecraft chunks by writing books that were filled with a bunch of obscure and obnoxious unicode characters, then saving hundreds of them in chests in the chunk
Definitely would and I was surprised why he didn't think of this. I imagine that's because there is probably a character limit. But if we could fill up the entire body of the email to reach 50mb this would definitely be faster, I'm sure a character limit would make this impossible, but filling up to the character limit would definitely make each email larger. I imagine he thought of this, and there must've been a roadblock. Unsure why it wasn't at least mentioned though
I initially misunderstood "giant unicode characters" as meaning "increasing the font size of the characters" and was very confused as to how you thought that would help for a second lol
I must admit, when I clicked on this video I thought it was going to be about signing up to as many email lists and spam phishing emails as possible. Still interesting and watched through!
1:14 Does Gmail only track the last sender when preventing forwarding? If so, couldn't you set up three mail boxes that forward to each other in circles?
About 5:02 I think it is because of the weird way attachments work in e-mail. Because e-mail must always be backwards compatible, emails only include text. Attachments were patched onto that, you must also convert attachment files into text. You might think: "I'll just convert the bytes to their responding ASCII character and send it after some attachment header" but email only supports printable characters, so bytes like 0x00 or 0x02 can't be written. That means there is some other clever, but not so efficient way to convert bytes to text.
Amazon SES is a really useful service if you spend 5 weeks setting up the proper controls and testing before turning it into a production version. For small things, it is basically not the right tool.
tldr: mind goblin deez nuts blank goblin or ________ goblin or as many mtg players have agreed mind goblin is a mtg card released in unfinity and is one of the cards responsible for all sticker and attraction cards being banned basically everywhere except commander. mind goblin is a sticker card that let you put a name sticker on it when it enters and as mind was one of the available names for on a sticker a lot of people refer to it as mind goblin as it adds mana based on vowels in it's name mind goblin is not the optimal choice but the funniest. Previous unsets were silver border which means they weren't allowed to be played outside of unset draft and that didn't make wotc enough money so to try and sell the set to commander players they instead made the cards black border and any cards that went too far were given an acorn to denote they were illegal which wouldn't be too bad if wotc didn't have promos of some of the cards with and without acorns and when the set released some cards were misprinted with the acorn when not supposed to have it and without when they were supposed to have it. A little while later players figured out mind goblin was actually a pretty powerful goblin card with the right sticker sets you could guarantee go at least neutral on mana and sometimes positive so it started seeing play in legacy and in pauper all that glitters started seeing play as you need a sticker deck to play mind goblin and an attraction deck to play all that glitters you were at a competitive disadvantage not bringing that deck as it told people you weren't playing the deck which eventually lead to wotc admitting the cards weren't supposed to see play outside of commander and banning them in not only legacy but also vintage which is a great dishonour you have to be a true design mistake to be banned in vintage and the first vintage ban since 2020 when lurrus was banned which is a whole different bag of design mistakes
On SES vs. Gmail: Sending an email through SES is slower because AWS routes requests through multiple APIs, using the public internet to query GCP, which increases the steps. On the other hand, Gmail is faster since everything stays within Google's infrastructure, so emails don't leave their network. At worst, emails might be in different data centers, but still within the same private network. Using different IPs for each email account might also help avoid anti-spam filters and slightly speed up email delivery.
Nah this wouldn't explain "multiple hours delay", they probably just have "experiences" of SES, guided by spammers, often scammers, bombarding people's inboxes...
1:23 isn't it possible to use 3 mailboxes? Box A forwards to Box B, Box B forwards to Box C, and Box C forwards it to Box A again. So a maillbox will not forward it directly back to the sender. Unless there is some forwarding history in the mail headers, this might work?
I remember when the inbox capacity would grow by the minute. You would receive a large email and the next day you had not free spacec than before. We thought it would grow forever 😅
So if you can't forward emails back to the sender, how about forwarding them to a third inbox that would in turn forward it to the sender? You'd get three full inboxes out of a single email sent!
And it's wrong anyway because 15 GB is 15,360 MB, not 15,000. 15,360 / 50 rounded up is 308, so it would be 5 minutes and 8 seconds as the theoretical fastest time.
It should be 15GB/(50MB*60per minute). And obv you have to multiply by 60, else you have no time reference. 60 per minute ~ 1 per second. So 50MB/s is 3000MB/minute, so 15000MB/5minutes
genuinely almost commented "wow the far-off fire alarm sounds really set the mood" but noticed no one else was commenting about them. it was my upstairs neighbors 😂 we're fine. smells like burning plastic so the dishwasher probably ate something it wasn't supposed to
at 4:40, the increased size is probably explained by the attachment being base64 encoded. That's how they made attachments fit into the originally plain text email protocol, at the cost of the size being increased by 1/3rd.
Being GMail it shares its storage space with Google Drive, so you could cheat by uploading large files to your GDrive to use up space. An easy way of doing this is uploading a reasonably sized file and making copies using the built-in "Make a Copy" function on the Drive which will just take seconds even for multiple GB files, doing a fewer larger files at once will also be quicker than doing more smaller files of the same overall size.
i just cleaned my gmail all the way as fast as I could, using an autoclicker. Then I get this recommended as soon as I open RUclips. I love how people, especially software devs, will do anything just to see if they can
Like that one other comment said, filling the emails with text instead of an attachment might be more useful, as the 50mb cap applies to the entire email (including text) and not attachments.
Developers : I'm lazy so i'm optimizing everything to waste as little time as possible Also developers : I've got some spare time, let's answer a stupid question nobody asked except my overthinking self
Just get a video that is 15gb and connect the google account to google photos. Then the video will upload and the 15gb will be full in less than a minute
Still watching the video so you may have addressed this or I missed it, but the reason why SES probably didn't work until the day after is that it's a spam prevention method. It's to prevent spammers from just signing up for email services and spamming users very quickly. They have to have the account for at least ~24 hours before email is actually treated normally. What you saw is that in action, there's basically nothing you can do except wait for a while and eventually it will start working.
This is such a fortunate coincidence, I was just learning about the gmail API! How did you create multiple gmails without having to use two-step verification for a web app password?
Call me crazy, but can't you send an email with a 25mb attachement and 25mb of text? It already looks like it allows emails over 25mb, so you can probably get to the 50mb limit pretty easily.
Try Google API to first create drafts with attachments and just copy the draft emails if that is an option Then bulk send the draft email. May be that will again improve the speedrun time.
I did look at hosting something myself (not mailcow specifically) but found that many cloud providers block SMTP port 25 specifically. Setting up all the DNS and dealing with IP reputation also seemed like a lot of work and also just fairly arcane, especially knowing that gmail could decide at any point to not accept more emails. Using an existing service like SES and the gmail API seemed like it would be more reliable, but given unlimited time and patience I’d like to revisit self-hosting a service capable of 50MB sends!
The extra data may be because email attachments sent over smtp are base64'ed. If Gmail is keeping the original message then that would increase the storage used.
I remember when i made my first gmail account in 2009ish they had a ticker saying how much storage youd get, and it was like 7gb or something. Seemed like more than you would ever need for email. I remember if you signed up at a certain time, later on that number would be higher so you would have less capacity in your inbox versus if you signed up later. But then we all got like 15 GB or something. I don't remember the exact number that they do right now. But I'm close to filling mine as well. Guess I'll have to start archiving some old stuff.
I wonder if you could pad the body of the emails with some pre-generated string of characters to fill up the rest of the email size. It would be a lot of text, but if you generated it before starting to send and always used the same text it should be pretty quick.
I wonder if you make the text of the email you're sending filled with lots of text and formatting things if it'll take up more space. I've heard of text messages that crash phones bc they contain so much data, I believe it was switching between characters of different languages which go from right to left, meaning it had to change the way it dealt with text every character. I wonder if this could be used to reach even over 50MB as the limit is only for attachments, but the storage contains all the emails.
I was expecting a speedrun of signing up for newsletters and posting hot take comments with your email public
Me too ... me too
Same. I enjoyed this, but I still really wanna see someone rush to sign up for newsletters en masse.
@@soniccookie655same
same.. i was a little disappointed when it wasn't
i can say it takes a lot more effort than one might expect...
newsletters need email conformation - slowing you down more than you expect
also those emails do not have attachments... all images are links - so emails are REALLY small
speaking from experience as i person that attempted i started from 2012 to show people that deleting emails in totally useless activity to save inbox space - especially on gmail
currently the email box is at 357k+ emails with 11,81 GB of data being used up by emails
i have stopped the experiment and deleted some as for some reason i like to use this meme email address from time to time
Should add a disclaimer that this is a TAS ;)
now do it manually
@@xonabytetook me a week. If you want only bot related emails maybe half a week
What is a TAS?
@@besterspieler2285Tool Assisted Speedrun.
@@besterspieler2285tool assisted speedrun
this is why I quit sending emails too many sweats
lmfao
same, and everyone's using bots now. Gmail seriously needs to up their anticheats and nerf attachments
I think I know why each e-mail takes up more space than you expected. E-mail was originally specified to only send plain text, so attachments are bodged in by converting the binary files to text using Base64 encoding.
Per Wikipedia, this “causes an overhead of 33-37%”.
Interesting
If only Gmail gzipped yo emails...
Came here to say this.
Wonder if there's ways to abuse that encoding so the b64 takes up even more space.
@@silicalnz besides the canonical 1/3 overhead of base64 the only other overhead of the encoding is max 2 bytes for the padding for each encoding. That is, you should make different attachments each consisting of 1 byte that gets encoded into 4 bytes. Depending on the actual implementation, there could be an overhead also for the line breaks (which, incidentally, are present in SMTP base64 for some reason), but I'd argue that the multipart MIME encoding overhead of the different attachments way surpasses that line breaks overhead; not sure if the MIME overhead is accounted in the user limit, but I suspect it is not, given the empirical results showed in the video.
TLDR: send more attachments in a single email
Gmail Speedrun 100% TAS (Glitchless)
Gerg?!
gerg
no way
Hi _gerg
facts gerg
472 emails in 471 seconds is actually EXACTLY 1 email per second, not slightly better. This is because of the fencepost error in which we accidentally counted the duration of the events and forgot that the first event takes no (or minimal) time.
To use a simple example, if you had managed two get 2 emails in 1 second, it could be because of the fact that the first email hit at 0 seconds (by definition) and the second email hit at 1 second (ignoring the details of exactly how Google handles 60 emails per minute throttling, which is relevant to the example, but not in practice when dealing with continuous periods of time over 60 seconds in length). So if we consider the first email to have hit at 0 seconds in (which is the definition used in the video), then after 471 seconds, we added an additional 471 emails.
0:00 is where the first second begins, and 0:01 is actually the start of the 2nd second. the final time of 7:51 ends inside the 472nd second, so it's 472 emails inside 472 seconds
you must be very fun in parties
@@Player-fg4ubincredibly horrible take. he didn't pick apart a joke, he gave useful information that might be interesting to someone watching a DEV CHANNEL. you can't just spam this phrase everywhere and expect it to work.
to the comment op, good info
@@HyperLexusyou must be very fun at parties
😂@@ilirx1509
we got ranked email before GTA 6
wtf hes alive i didnt know you could do that
I mean we've known about "casual email" for a while now
youve been gone for 2 years
TBF the leaker will probably complete his sentence before GTA 6 releases
my god it was unexpected seeing you
haha wheee i hope google doesn't erase all trace of me from the internet for this one haha really though :)
let me know which enterprise software speedrun i should do next
speedrun cancelling an adobe subscription
@@iquemediaimpossible%
not a speedrun but try making like the largest github repo ever (I just made it up pls prove me wrong)
You probably also could have uploaded a 15GB file to google drive to fill up your free google storage space which is shared with Gmail
Speedrun getting banned for using chatgpt
Sounds like fun but... I'm pretty sure gmail shares storage with google drive, so to fill your inbox you just need to upload 15gb file to google drive
it does lol
Bro decided to hack into the matrix 💀
He's really running Any% glitchless, GDrive is too OP
Any% with Exploits
You don't even need to upload it, you can be added to a shared drive and copy a 15 gig file to your drive, a TAS would probably be like 2 seconds long lol
Who else thought he was going to subscribe to as many spam emails as possible with a Livesplit timer?
32MB instead of 25 might be caused by base64 encoding (which increases size by a third) because oft course SMTP is not binary safe
same thought. Base64 is 4/3 the size that fits.
Simple speak: Files get bigger when sent as an email. Yes, it is stupid. (Only while in an email. When you download them they are the small size again)
@@jurgennicht4626 nah it's not stupid. Base64 encoding was made for sending binary data over ascii-only protocols. SMTP was made before we even had images to send, obviously it wasn't designed with it in mind. It's actually a really fine way of extending an existing standard without altering it.
Out of curiosity: Is it fully stupid? Or is there some "smart" reason (say, security) for it to have been decided to be this way?
@@roshibomb4247 afaic for historical reasons only. It's just the safe way to transmit non-text data (or arbitrary data where you can't know whether it is Text or not) via a system that was designed to transmit text only. But the specification might still mandate it
I wonder if filling the email content with giant unicode characters would increase the size of the emails.
You mean font-size:72 and higher? :O
More likely, a bunch of "giant" i.e long unicode characters to take up a lot of space. We can only include a 25MB attachment but we should be able to fill the rest with a lot of characters to reach the other 25 megabytes for the max of 50MB per email.
It might be possible to send 2 large attachments to fill that up, but I don't know if this is possible and I have not finished watching the video
Memories of overloading Minecraft chunks by writing books that were filled with a bunch of obscure and obnoxious unicode characters, then saving hundreds of them in chests in the chunk
Definitely would and I was surprised why he didn't think of this. I imagine that's because there is probably a character limit. But if we could fill up the entire body of the email to reach 50mb this would definitely be faster, I'm sure a character limit would make this impossible, but filling up to the character limit would definitely make each email larger.
I imagine he thought of this, and there must've been a roadblock. Unsure why it wasn't at least mentioned though
I initially misunderstood "giant unicode characters" as meaning "increasing the font size of the characters" and was very confused as to how you thought that would help for a second lol
I must admit, when I clicked on this video I thought it was going to be about signing up to as many email lists and spam phishing emails as possible. Still interesting and watched through!
1:14 Does Gmail only track the last sender when preventing forwarding? If so, couldn't you set up three mail boxes that forward to each other in circles?
1:29
@@mr.vladislav5746 thats not what hes askig it is different
@@curtisclewett5249 at 1:29 he explained that all kinds of infinite loops have been patched
it will probably use email IDs/things like that
@@curtisclewett5249 that was exactly what he was asking - at my timestamp the video author explains that all kinds of infinite loops have been patched
"it was very late so I went to bed" clock shows 9:30PM, next scene 9AM the next day, you really grinded for this video huh? respect
About 5:02 I think it is because of the weird way attachments work in e-mail. Because e-mail must always be backwards compatible, emails only include text. Attachments were patched onto that, you must also convert attachment files into text. You might think: "I'll just convert the bytes to their responding ASCII character and send it after some attachment header" but email only supports printable characters, so bytes like 0x00 or 0x02 can't be written. That means there is some other clever, but not so efficient way to convert bytes to text.
This video was absolute PEAK. Im subscribing right away
I can hear the summoning salt intro music starting to play in the background already
time to self-host
It sounds so good, but self hosting email is more than a fulltime job... 😂
(If you need to send/receive emails from the big three...) Outside that it is not so bad, aside from spam.
hi ari i fully agree
heck yeah
@@rkan2 i host email for myself, my business and my clients. It is not
Took me almost 13 years but here we go, google won't let me receive emails anymore. IRONICALLY recommended this video to me too.
Hell yeah, man. Keep up the good work!
This is why I quit emailing, too many sweats.
I love the engineering of the solutions. I told my partner: I would love to work with this guy! It should be so fun!
im impressed at your ability to make many accounts without being yelled at for a verifying phone number needed to keep the email alive
4:04 Unexpected factorial
I love you dev detour. Never stop uploading these are so much fun
so this is where all the good email addresses are going
Amazon SES is a really useful service if you spend 5 weeks setting up the proper controls and testing before turning it into a production version. For small things, it is basically not the right tool.
so "Simple"
WHERE IS MY UNLIMITED STORAGE, GOOGLE?!
do you remember the unlimited google photos storage? good times
@@ゾカリクゾ it was to train their AI
Remember, Dev Detour ISNT unhappy and loves life. He has NO plans of ending it soon
Was expecting the 472 gmail accounts all sending 1 email in 1 second ha! great vid!
Love that you used the caterpillar song, that always gets stuck in my head
Obligatory "What's Mind Goblin?"
Mind goblin deez nuts
not much what’s up with you
tldr: mind goblin deez nuts
blank goblin or ________ goblin or as many mtg players have agreed mind goblin is a mtg card released in unfinity and is one of the cards responsible for all sticker and attraction cards being banned basically everywhere except commander. mind goblin is a sticker card that let you put a name sticker on it when it enters and as mind was one of the available names for on a sticker a lot of people refer to it as mind goblin as it adds mana based on vowels in it's name mind goblin is not the optimal choice but the funniest. Previous unsets were silver border which means they weren't allowed to be played outside of unset draft and that didn't make wotc enough money so to try and sell the set to commander players they instead made the cards black border and any cards that went too far were given an acorn to denote they were illegal which wouldn't be too bad if wotc didn't have promos of some of the cards with and without acorns and when the set released some cards were misprinted with the acorn when not supposed to have it and without when they were supposed to have it. A little while later players figured out mind goblin was actually a pretty powerful goblin card with the right sticker sets you could guarantee go at least neutral on mana and sometimes positive so it started seeing play in legacy and in pauper all that glitters started seeing play as you need a sticker deck to play mind goblin and an attraction deck to play all that glitters you were at a competitive disadvantage not bringing that deck as it told people you weren't playing the deck which eventually lead to wotc admitting the cards weren't supposed to see play outside of commander and banning them in not only legacy but also vintage which is a great dishonour you have to be a true design mistake to be banned in vintage and the first vintage ban since 2020 when lurrus was banned which is a whole different bag of design mistakes
mind goblin deez nutssss? also: you like Wendy's?
Hearing rumors of cc skip in the community, cant wait for sub 4
What you need to do to increase the email size is make ~2000~50 gmails and forward the email until the message is at the maximum size.
These Gmail inboxes are very innocently named!
IS THAT A SONG THAT PLAYS WHEN YOU ENCOUNTER A CATERPILLAR??? That made my day, small internet world
On SES vs. Gmail:
Sending an email through SES is slower because AWS routes requests through multiple APIs, using the public internet to query GCP, which increases the steps.
On the other hand, Gmail is faster since everything stays within Google's infrastructure, so emails don't leave their network. At worst, emails might be in different data centers, but still within the same private network.
Using different IPs for each email account might also help avoid anti-spam filters and slightly speed up email delivery.
Nah this wouldn't explain "multiple hours delay", they probably just have "experiences" of SES, guided by spammers, often scammers, bombarding people's inboxes...
this one dude who woke up and decided to be productive for the day.
the product:
The best video to watch while I’m eating😂
1:23 isn't it possible to use 3 mailboxes? Box A forwards to Box B, Box B forwards to Box C, and Box C forwards it to Box A again.
So a maillbox will not forward it directly back to the sender. Unless there is some forwarding history in the mail headers, this might work?
This is such an underrated video, you only got 24k subs, you deserve more!
There isn’t actually a hard cutoff. I’m about 6gb over and they keep giving me
this is delightfully stupid, I love it. please do more
We got Gmail speedrun before GTA 6
please seek professional help
He did but they didn't respond to his emails
@@Johnnyvtg heeeeheeheheheeheeeeee bwahahahahahaha
Good thinking! Reaching out to Google's professionals should be able to help the community with this category!
i mean you could just fill the 18mb needed with 18 million letters in the message body
Attachments in email are base64 encoded and thus take up more storage than you'd expect
This video is useless. That’s exactly why I clicked and am so entertained rn
I remember when the inbox capacity would grow by the minute. You would receive a large email and the next day you had not free spacec than before. We thought it would grow forever 😅
Next up on Dev Tour:
Gmail 100 precent speedrun
So if you can't forward emails back to the sender, how about forwarding them to a third inbox that would in turn forward it to the sender? You'd get three full inboxes out of a single email sent!
Can't wait to see you on Summoning Salt!
oh so YOU'RE the reason i wasn't able to register chronicligma
0:42 the math is wrong. There no need to multiply by 60. If you multiply by 60, you'll end up with 5 hours instead of the 5 minutes shown.
15000MB/50MB * 1 seconds = 300 seconds. They were close but not quite.
And it's wrong anyway because 15 GB is 15,360 MB, not 15,000. 15,360 / 50 rounded up is 308, so it would be 5 minutes and 8 seconds as the theoretical fastest time.
@@awesomelink23471 giga = 1000 mega, as defined by SI
@@awesomelink234715GB is 15000MB. 15GiB is 15360MiB
It should be 15GB/(50MB*60per minute). And obv you have to multiply by 60, else you have no time reference. 60 per minute ~ 1 per second. So 50MB/s is 3000MB/minute, so 15000MB/5minutes
genuinely almost commented "wow the far-off fire alarm sounds really set the mood" but noticed no one else was commenting about them. it was my upstairs neighbors 😂 we're fine. smells like burning plastic so the dishwasher probably ate something it wasn't supposed to
Nope I hear the alarm too
at 4:40, the increased size is probably explained by the attachment being base64 encoded. That's how they made attachments fit into the originally plain text email protocol, at the cost of the size being increased by 1/3rd.
Gives me tom7’s “harder drives” vibes; big fan!
great stuff. Nothing like project based learning to find the limits of SES and GMAIL cooperation.
Don't know why I just watched a 13 minute video of a guy sending e-mails to himself, but I'll admit, it was quite entertaining.
Add 20 MB in the body.
Being GMail it shares its storage space with Google Drive, so you could cheat by uploading large files to your GDrive to use up space. An easy way of doing this is uploading a reasonably sized file and making copies using the built-in "Make a Copy" function on the Drive which will just take seconds even for multiple GB files, doing a fewer larger files at once will also be quicker than doing more smaller files of the same overall size.
I love the idea of speed running Gmail. Great video
Wouldnt a 25mb body be exactly what you need to compliment a 25mb attachment?
Your google photos, drive and mail storage are linked. So its possible to fill drive with very large (compared to 50 mb) files faster
Email is entirely plain text. Binary attachments are based encoded, which increases their size by about 1/3. 25GB * 1/3 is about 8MB.
i just cleaned my gmail all the way as fast as I could, using an autoclicker. Then I get this recommended as soon as I open RUclips. I love how people, especially software devs, will do anything just to see if they can
Like that one other comment said, filling the emails with text instead of an attachment might be more useful, as the 50mb cap applies to the entire email (including text) and not attachments.
Bro you earned a sub.
malding at aws was too relatable
Ah yes, a billion dollar company unable to do the only job it does, sounds familiar.
2:07 The way I read the rule, it looked like you could send 2x25MB attachments in a single email. That said, I have not tested it.
What if you just connect via IMAP and upload a bunch of emails instead of sending to an email address?
Developers : I'm lazy so i'm optimizing everything to waste as little time as possible
Also developers : I've got some spare time, let's answer a stupid question nobody asked except my overthinking self
Just get a video that is 15gb and connect the google account to google photos. Then the video will upload and the 15gb will be full in less than a minute
The extra space is because of BASE64 ENCODING.
Youre welcome.
Just try setting up 3 emails forwarding in a loop
At 1:29 he seems to explain that all kinds of loops have been “patched” by Google
10:33 Wouldn't running it on the same computer work, or implementing multithreading? CPUs have multiple cores for reasons lol
Now this! Is quality content.
FYI increasing the limit for SES is basically writing a single sentence and it mostly gets auto approved
The domain at 7:43 genuinely cracked me up!
Im actually so glad to see a speedrun that is interesting, and wastes googles time and data
Still watching the video so you may have addressed this or I missed it, but the reason why SES probably didn't work until the day after is that it's a spam prevention method. It's to prevent spammers from just signing up for email services and spamming users very quickly. They have to have the account for at least ~24 hours before email is actually treated normally. What you saw is that in action, there's basically nothing you can do except wait for a while and eventually it will start working.
This is such a fortunate coincidence, I was just learning about the gmail API! How did you create multiple gmails without having to use two-step verification for a web app password?
Call me crazy, but can't you send an email with a 25mb attachement and 25mb of text? It already looks like it allows emails over 25mb, so you can probably get to the 50mb limit pretty easily.
15 GB is the storage limit.
i think the total of sending isn't allowed to be above 25MB before encoding. and the 50MB is a hard limit, and is after encoding
'You absolute SERF'.
we are speedrunning gmail before gta 6
4:56 This is likely because attachments must be ASCII encoded before sending, due to historical reasons
it was a really cool watch, thanks
my first thought you mention forwarding is that instead of 2 mails sending back and forth, a 3rd mail to make it a triangle and a circle of forwarding
Microsoft 365 can be configured to support a lot larger attachments
Try Google API to first create drafts with attachments and just copy the draft emails if that is an option
Then bulk send the draft email. May be that will again improve the speedrun time.
why not host your own mail service using something like mailcow and automate it using that?
I did look at hosting something myself (not mailcow specifically) but found that many cloud providers block SMTP port 25 specifically. Setting up all the DNS and dealing with IP reputation also seemed like a lot of work and also just fairly arcane, especially knowing that gmail could decide at any point to not accept more emails. Using an existing service like SES and the gmail API seemed like it would be more reliable, but given unlimited time and patience I’d like to revisit self-hosting a service capable of 50MB sends!
4:53 the small text…
Good catch
I believe the sent inbox also counts towards storage, so if you set up auto forwarding and auto response you'd get a few extra MB out of that.
I think you could make it closer to the theoretical limit if you sent the mail with your own mail server. I'd be happy to collab on a part 2.
The extra data may be because email attachments sent over smtp are base64'ed. If Gmail is keeping the original message then that would increase the storage used.
I remember when i made my first gmail account in 2009ish they had a ticker saying how much storage youd get, and it was like 7gb or something. Seemed like more than you would ever need for email. I remember if you signed up at a certain time, later on that number would be higher so you would have less capacity in your inbox versus if you signed up later. But then we all got like 15 GB or something. I don't remember the exact number that they do right now. But I'm close to filling mine as well. Guess I'll have to start archiving some old stuff.
I wonder if you could pad the body of the emails with some pre-generated string of characters to fill up the rest of the email size. It would be a lot of text, but if you generated it before starting to send and always used the same text it should be pretty quick.
I wonder if you make the text of the email you're sending filled with lots of text and formatting things if it'll take up more space. I've heard of text messages that crash phones bc they contain so much data, I believe it was switching between characters of different languages which go from right to left, meaning it had to change the way it dealt with text every character. I wonder if this could be used to reach even over 50MB as the limit is only for attachments, but the storage contains all the emails.