Skip to main content

Stop using Dropbox to send a file

Dropbox.  It's becoming the household name for the way to transfer files, and I don't understand why.


Overview: A small client gets installed on computer A and computer B.  Files added to computer A are synced to the Dropbox cloud server, which then syncs the files to Computer B (and any other subscribed computers). The presence of the files on the Dropbox cloud server has the side benefit of being able to easily access the files online, and even share URLs for people to access the files without the Dropbox software.  It went a long way toward solving the problem of "I need have access to my files on many different computers, tablets and my phone, and occasionally make these files accessible to the customer".  However, it's simple installation and accessible marketing seems to have led it into another use case, and not necessarily one that it is good for:  sending files to other users.

There have been countless online services, yousendit.com, megaupload.com, filestube.com, to name a few, which do a pretty good job of this use case: "I have a 2 GB file, I need to send it to joebob@aol.com."  However, it seems like most people don't like uploading the file to a website, getting a URL, and then pasting this into an e-mail.  Perhaps it's the extra steps, perhaps it's a concern about putting the file on a third-party site (which is ironic, as Dropbox does the same thing, but for some reason people don't get this).

The possible issues with using Dropbox this way are many.  Here are a few:

  • Dropbox is a comparatively long-term relationship, as opposed to e-mailing a URL. Once a shared dropbox folder is on your systems, it will be there until one of you removes it, which requires some consideration.
  • When you have a Dropbox folder with someone, the folders stay sync'd.  The idea of sending a file this way implies that either of you will remove the file after the transaction.  If this is done by the sending party, the receiving party had better have copied the file somewhere outside of the shared folder.  Likewise, if it's done by the recipient, the sender had better be expecting it.  If it's done by no one, you now have a file there with no clear owner, which will eventually become either out-of-date or irrelevant, and that might be a complicated situation when it comes time to clean up.
  • Dropbox sharing with other users doesn't scale well.  Once you start sharing with a number of people, it's difficult to keep track of which folders were shared, with whom, and whether the elimination of a folder on your system will impact others in a negative way.
  • Dropboxes grow in size on the sender's computer - keeping files in a Dropbox so that they are available to others means that you have to have sufficient room to store those files, which may mean having duplicate copies, if you wish to freeze a file's version for example.
  • Dropboxes grow in size on the recipients's computer - imagine what happens when your dropbox buddy "drops" a 2GB file on your system drive, that has 1GB free.  This happened to my friend a few months ago when he wasn't even around, and it wasn't pretty.  When trying to mitigate the lack of space situation, he ended up deleting some huge files from the shared folder, which of course deleted them from the sharer's computer as well!
I have no problem with using a URL to share particular files or folders in a Dropbox, other than the caveat that anyone who knows the correct URL can access your "private" files (something a lot of people don't seem to acknowledge).  The transfer of a URL in an e-mail is non-committal enough that I'm not going to worry if someone can't get the file when I deleted or moved it a month from now.  I just don't like the trend I'm seeing of people installing Dropbox clients, just so they can get a shared folder a business associate sent them.  

Comments

Popular posts from this blog

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* f...

An Alternative Take on AI Doom and Gloom

 I've purposely held my tongue until now on commenting about "AI" (or, more specifically as has come to be known, GAN or Generative Adversarial Networks).  It seems like it is very in-style to complain about how it has made a real mess of things, it is displacing jobs, the product it creates lacks soul, it's going to get smart and kill us all, etc. etc.  But I'm not here to do any of that. Rather I am going to remind everyone of how amazing a phenomenon it is to watch a disruptive technology becoming democratized From the time of its (seeming) introduction to the public at large, around November of 2022, to late 2023, the growth and adoption rate has been nothing short of explosive. It features the fastest adoption rate of any new technology ever, by a broad margin.  To give a reference, the adoption rate for AI image and text generation, real-world uses, in just 12 months is comparable to all of that of the another disruptive technology, the World Wide Web, takin...

RANT TIME: Why do replies to a message I sent go to my spam folder?

Despite what one would think/hope, sending a message to a given address does not inherently give Google a high confidence that a reply from this address is expected (and, for example, that it should bypass spam checks). I have confirmed with Google's tech support that there is no way to automatically have this happen. The user can do the following: 1. Add the address to your contacts list in Gmail. 2. Check spam folder for replies, and mark it as "not spam" if something ends up there, which should influence the fate of future replies received. I can also approve an address at the domain level, i.e. if it is a big vendor or similar. I've had to do this with several of our Chinese vendors. I regularly ask engineering and purchasing to give me a list of the supplies we deal with, so I can approve them as a preventative measure. For what it's worth, all of the false positive instances of reply -> spam we have experienced have involved the sender's email server ...