View Single Post
Old 16 Aug 2017, 05:46 AM   #14
ioneja
Cornerstone of the Community
 
Join Date: Jul 2011
Posts: 713
Quote:
Originally Posted by janusz View Post
Why? Just curious....
For a bunch of reasons, but here are two big ones, for starters:

1) In the most practical sense, email attachment sizes are not standardized across email providers, which make it a pain in the neck, even today, in 2017. For example, as far as I recall, Office 365 is 150MB, Gmail is 25MB, Yahoo is 25MB, FastMail is 50MB last time I checked, Runbox is 130MB (which translates to 100MB since that's the encoded maximum), AOL (yes, still used by many people) is 25MB, Zoho Mail is 20MB. Yandex 25MB, iCould 20MB. And on and on.... Since no one can really agree on a standard size, it's by default very limited and causes confusion and issues across the board. Stick to around 10-15MB and you are safe with just about everyone.

2) Using email for large files is very inefficient for bandwidth and storage. Here's one example of what I mean:

If I want to sent a 100MB video file to 10 people via email, I can easily chew up massively more bandwidth and/or storage than a streaming/sharing service, for example. Once I send it, that's 10 copies of that data -- encoded (which is about 30% larger BTW) that is sent out. Boom. Huge waste off the bat. Then there will be 10 unique copies stored in 10 separate accounts on various servers, depending on the recipients. More waste. Then, each time that video is played, most email clients will download the whole thing locally, and if you don't save it locally, each time you view it, it will download the whole thing again. We're talking incredible inefficiency. Think of how many copies are actually sitting out there on so many hard drives... and then if people start forwarding and replying with inline attachments... we're just chewing up space like crazy... tons and tons of copies just floating around like dead weight. It doesn't make sense. Even backups of the local and/or remote email database (again, depending on the client and service you are using) -- you are potentially inflating backup storage with multiple copies of a big file... over and over, across every recipient of the file, ever. Just crazy.

Not to mention you've TOTALLY lost control of that file with no hope of putting that genie back in bottle, or at least restricting its distribution or auditing it's trail.

I mean, it gets pretty nasty when we start dealing with cell phone data bandwidth and streaming time/quality and general limits on cell phone plans... just as another point of consideration.

But compare all that to using a simple file sharing service like Dropbox. Now, Dropbox has a couple of ways of sharing a file... so this example is just one possible scenario I could paint... so for this let's say the recipient does NOT have a Dropbox account, so you would send them a shared link for them to download or view the file. Using the same scenario above... you send a LINK to 10 people, NOT the actual file. Right there you've saved a huge amount of bandwidth from the start. Your email client is sending a LINK and nothing else, saving 10 copies right there. Then, on their end, their email server is only storing a LINK. Again, massive savings. Then, on top of that, Dropbox creates a low-res streaming version of the video clip for you to save bandwidth so that if you are on your cell phone then you can actually watch a version of it, and even skip around -- so it doesn't even download the whole file unless you WANT to... thus saving even more bandwidth and storage for those that don't end up looking at the file. The savings are incredible... which ultimately translates to time and money.

In fact, how many times have you sent a file to 10 people and only 2 people looked at it? With email, their server and/or email client already has a copy of it, and they haven't even bothered to look at it. In this example, only 2 people access the Dropbox shared file.

Then think of the backups and forwards... you are backing up and forwarding just a link to the file... not the file itself. The logic goes on and on. Again, that's just one approach with file sharing via Dropbox... you have other methods within Dropbox that DO make unique copies on their hard drives as well. But even then, the data savings is notable with email.

In the most practical sense in my business, as a media producer, I have access to terabytes upon terabytes of video footage from my phone for my clients, and I can share any clip I want to with merely a link, that shows up near-instantly, and uses comparatively NO bandwidth unless my client wants to view some or all of a specific clip. My email is kept to minimal resources and a large file is accessed only when needed, using zero local storage (unless I want to download it).

So really, there is no comparison. Just for those two basic reasons alone, anything bigger than 25MB makes NO sense to me to send via email. First, because you don't know if the recipient's email server can handle it, and second, it just wastes energy, bandwidth, storage, and ultimately money. And if you are dealing with a recipient on limited data plans it can actually become a nightmare.

On top of that, file sharing systems have become very elaborate so that very useful tracking, delivery, feedback systems, management, security, auditing and other cool features are available now in some of those services... things that most email services are just inherently not good at. A very useful advantage of using a great file sharing system is good security that requires additional authentication to view a file. For example, a video clip meant just for a client can be restricted in some services to a specific login and expiration, and I can track exactly how many times the file has been accessed and by whom. It's not perfect, since the client can still do something stupid with the large file if they can download it locally, but it puts one extra layer of auditing in place that doesn't exist with email. Once you send a large file via email, on the other hand, you literally have NO auditing or control over the file again, with no idea what happened with it. This is especially important when dealing with things that have liability or privacy concerns.

The features are all over the map for each of these services, but two of the most powerful ones are box.com and hightail.com, both of which I've used for massive projects with clients. Dropbox Plus and Dropbox for Business have some of those similar features, but not quite as advanced in some key areas. Google Drive and OneDrive have some decent flexibility too, but I get very frustrated with them as they have some specific limitations for auditing and deliverability. If you want to go the privacy direction, then SpiderOak has some excellent features... the list goes on.

In my experience, once you get above about 10MB, the immediacy and convenience of email starts hitting obstacles, with increasingly diminishing returns as you increase attachment size. Once you go above 25MB, you lose Gmail and other major providers... and once you pass 50MB you've lost most of the big players. Once you go over 100MB you are just chewing up bandwidth and file storage like crazy, and it doesn't make much sense. At least not when even Dropbox can handle files that are theoretically unlimited, up to the capacity of your storage.

Just my two bits.

Last edited by ioneja : 16 Aug 2017 at 05:51 AM.
ioneja is offline   Reply With Quote