Here's my rebuttal: http://turtlapp.tumblr.com/post/81222024691/how-turtl-has-no...
How Dropbox Knows When You’re Sharing Copyrighted Stuff
21–30 of 69 posts
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#22Yet another reason not to use cloud services. For start dropbox is infrastructure provider and they have no right to snoop inside your files. If they start blocking stuff at their own will they are judge and executor. Secondly there is lot of potential for abuse. Hacker could sneak hash collision into their database and essentially censor-ship any document he wants. And finally I do not understand why there has to be…
You clearly didn't read the article. It only applies to sharing files, not storing them. All of your arguments do not apply to shared files.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#23Yet another reason not to use cloud services. For start dropbox is infrastructure provider and they have no right to snoop inside your files. If they start blocking stuff at their own will they are judge and executor. Secondly there is lot of potential for abuse. Hacker could sneak hash collision into their database and essentially censor-ship any document he wants. And finally I do not understand why there has to be…
I don't think what you're arguing would be a problem. From the article:
"Only when a file is shared from user-to-user (or with the Internet at large) does the DMCA check system come into play"
"Some thought the original file was deleted from the user’s Dropbox — that’s not the case, either. Dropbox just blocks the file from being shared."
Personally I think cloud services are super convenient and the downside for most people is really small.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#24Yet another reason not to use cloud services. For start dropbox is infrastructure provider and they have no right to snoop inside your files. If they start blocking stuff at their own will they are judge and executor. Secondly there is lot of potential for abuse. Hacker could sneak hash collision into their database and essentially censor-ship any document he wants. And finally I do not understand why there has to be…
You could also just encrypt before uploading.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#25I was under the impression they knew, but didn't care. In the past I had uploaded GB-sized HDTV stuff and had it instantly uploaded and available to a friend. I figured they just hashed it, realized someone else already put it up, and added that file to my account or otherwise linked it into my account.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#26I've seen a lot of outrage about this on Twitter, what annoys me most is that these people who are outraged for the most part consider piracy to be acceptable. Then when a company tries to enforce copyright law and protect the rights of the content owners they go on a tirade that their personal privacy is being breached.
I know that the rights holders haven't been blameless in their history but piracy is still wrong and getting upset about people trying to stop it is wrong.
EDIT: I also think that Dropbox's method of detecting copyrighted files is a perfectly reasonable way of doing it. By now we all (should) know the rights we give up for the convenience we get when using consumer cloud services. I think Dropbox are well within their legal and moral rights to do this.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#27Earlier quoted context omitted.
That brings up an interesting question. At what point does a modified file no longer fall under copyright? If I had a copyrighted ebook and changed a single "o" to "0" I bet I could still be busted for distributing it (although it appears Dropbox would no longer automatically catch me). But what if I changed every single "o" to a "0"? Re-arranged words? Chapters? Upcased every lowercase letter? My guess is that's it'…
It would fall under the same rules as fair use. If the modified file is close enough to the original that it could deprive the creator of a sale, then it is certainly infringement. If you made it so different that it would not deprive the creator of a sale (for example, if you re-arranged every single word so that the words in the book were in an entirely random order), that would most likely be fair use.
It's not quite that simple, something can be a derivative work even if none of the original content remains and it's purpose changes dramatically. Generally speaking fan-fiction infringes copy-write when someone trys to make money off of it. However, the same work may be free and clear if you don't try and make money from it.
Teachers can generally copy something to use in class as an example. However, they may not copy the same content every year after that. Same action, but slightly different context.
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#28If you don't control them, they're not yours.
So if you don't control, say, your family they are not your family?
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#29Yet another reason not to use cloud services. For start dropbox is infrastructure provider and they have no right to snoop inside your files. If they start blocking stuff at their own will they are judge and executor. Secondly there is lot of potential for abuse. Hacker could sneak hash collision into their database and essentially censor-ship any document he wants. And finally I do not understand why there has to be…
You clearly didn't read the article. It only applies to sharing files, not storing them. All of your arguments do not apply to shared files.
It does apply, there is no evidence that receiver does not have a valid license. It could be even the same person using two accounts.
By this logic we should shutdown Github and SourceForge, until we "clear up some legal stuff".
Re: How Dropbox Knows When You’re Sharing Copyrighted Stuff
#30Here's my rebuttal: http://turtlapp.tumblr.com/post/81222024691/how-turtl-has-no...
Just curious, are you storing the keys? Or at the very least the login info from which you could regenerate the keys? If so, there's no reason a government couldn't ask for you to hand the info over, so even though this is a step more complex that Dropbox, it doesn't add too much security.
Now, if users provide their own key and it's never transmitted, that would be secure, but obviously the data would be un-decryptable if the key is lost.