4 ms·
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.
by jedberg 13y ago
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.
- qwerta 13y agoIt 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".
- psc 13y agoI agree with you that there are cases in which Dropbox might pick up false positives. I think the DMCA should be updated with harsher penalties for improper takedown requests ("copyfraud"). Still, the policy Dropbox has seems pretty reasonable. And you can always choose to encrypt your files locally or even not use Dropbox. After all, it's a company competing in a relatively free market. But I think for most people Dropbox is a pretty good choice and this takedown policy shouldn't be a reason for them to stop using it.
- qwerta 13y agoI agree their policy is reasonable for filesharing service.. But it makes dropbox useless for me as backup storage or hosting provider. I would not trust filesystem or provider which randomly deletes/blocks my data.
- rz2k 13y agoIt makes sense that Dropbox wants to avoid the popularity that would come from being an easy way to distribute unauthorized content. However, takedown notices have been abused on YouTube to censor criticism, and dishonestly claim ownership. The problem could be even worse if what it covered wasn't limited to when links are posted publicly, but also covered shares between family members, colleagues, and friends. While distributing backups from your DVD collection to a colleague may not make sense, and that isn't much better than posting public links, qwerta has a point when it comes to the potential for someone unethical to abuse the system. I appreciate the challenges Dropbox faces with respect to copyright, and that it is easier to focus on making a viable business if a broad policy wastes less of their time on the issue. However, it's also a complicated when you've given a service read/write access to your hard drive—not necessarily because its reasonable to assume that Dropbox would take a legal risk like proactively deleting content on your computer, but because it's almost an unreasonable amount of trust you're granting them in the first place. Anyway, maybe you meant, "Not all of your arguments apply to shared files."