3 ms·
Neat idea, but the current version of the document just looks like a jumble of loosely related points, somewhat like the laundry list of demands that somebody c
by kijin 15y ago
Neat idea, but the current version of the document just looks like a jumble of loosely related points, somewhat like the laundry list of demands that somebody claiming to represent OWS posted on Reddit a few months ago. What does a damage cap on copyright infringement have to do with a general prohibition of censorship? Why does the document suddenly make up an arbitrary definition of derivative content? Closely related items should be placed together, but different topics should be grouped separately.
I'm also a bit skeptical about the way the document so quickly excludes "illegal data" from its purview. So much of the surveillance and censorship measures that people are worried about take place in the name of preventing and/or prosecuting illegal activity. Therefore, the scope of "illegal" must be very carefully defined in order to prevent gaping loopholes. Is downloading child porn "illegal" in the same way that uploading a copyrighted song is "illegal"? At the very least, cases involving damage claims in a civil suit should be distinguished from cases involving criminal prosecution.
Also, basing damages on the retail price of copyrighted works, multiplied by the number of copies produced, seems odd to me. If you upload 0.8% of a copyrighted file to 100 people over BitTorrent, how many copies have you produced? 0.8 copies? What if the infringed work is not on sale in the first place? What happens if you violate an open-source software license?
But I don't hang out on Reddit all that much, so maybe these apparent shortcomings have good reasons behind them?
- JumpCrisscross 15y agoIt's ironic that the effect of special interests, pork, and other forms of Congressional "trolling" writing a bill in Google Docs seeks to mock come home to roost regardless.