If it was copyrighted material that he shared/linked to publicly, then it makes sense. If, however, it was private files that he hadn't shared with anyone else, well, then this is a HUGE deal.
That doesn't even make sense... but then again, much of copyright law doesn't either.
edit: on further reading of his tweets, it appears that he shared link to the file with another person. So while Dropbox might be overstepping a bit, imho it seems that their action was justified (assuming that the DMCA complaint was originally justified).
edit2: Dropbox response https://twitter.com/dropbox_support/statuses/450176566375366...
@darrellwhitelaw replies that's what he meant, only sharing is disabled.
Good find, that clarifies a lot.
Dropbox asked the author to take down the app, and now Dropbox does additional consistency checks to prevent this use case.
EDIT: Dropship: http://en.wikipedia.org/wiki/Dropship_(software)
This is either a bug on dropbox where the message shows to anyone having some flagged file(s), or he was sharing copyrighted content and conveniently emptied the folder before taking the screen capture to paint dropbox in a worse light.
"Certain files in this folder cannot be shared due to a takedown request with the DMCA"
I interpret that as he has some copyrighted files in his private folder which he is trying to make shared/public.
Perhaps dropbox has previously gotten a takedown request for those files (when shared by some other user), and to comply with the request is preventing anyone else from sharing the files in the future.
Besides, what might be copyright infringement to one user might be legitimate usage to another. For example, you might have an illegal copy of an ebook in your folder, but I have the same copy, but mine was paid for. Should I lose access to mine? OReilly books don't have DRM, so it's possible it could happen.
While technically true, I think it is very rare that a file is DMCAd for one user while another is sharing it legitimately. Rare enough that a trip to customer service is warranted.
> For example, you might have an illegal copy of an ebook in your folder, but I have the same copy, but mine was paid for. Should I lose access to mine?
Note that the discussion here revolves around sharing, not having personal access. So while you should (and would with Dropboxs current system) retain your own access to the files, you shouldn't be able to share it, which seems reasonable to me.
The message is quite cleverly constructed, as it doesn't actually say that there is a DMCA takedown request against the file (because there isn't). It just says that there has been a takedown request sometime, possibly(probably) against some other file/url.
However, as stated, the DMCA isn't currently meant to take down the file and keep it down forever. It's meant to kill links one at at time.
Bigger organizations want it to take a file down and keep it down forever, which is what's being kicked around now as being a possible reinterpretation of the DMCA, which is crazy.
Respect Dropbox TOS and your files will not be deleted.
Share some copyrighted material and deal with the consequences.
By the way you can encrypt files before sending them to the cloud, but in order to share them with a third party you'd have to give your keys, which makes little sense.
Example, my wife and I are physically separated (let's say she is in Europe for a week) and she wants a copy of "Frozen" that I just ripped from the DVD I own. (It's a long plane ride home.)
Making a copy is fair use, and putting a copy on her computer is not illegal.
Dropbox is treading a fine line. If they fuck with my files, I will drop them fast.
(One of the properties of Tahoe is managing the keys to decrypt data completely outside of the servers, so that the servers never have any knowledge of what they're storing.)
Don't do illegal shit on Dropbox; problem solved.
let's say you have a TC volume of 5GB that contains your personal notes in txt files. You edit one txt file and Dropbox will have to synchronize 5GB of data.
I prefer encrypting files one by one, e.g. using Cloudfogger.