Slashdot Mirror
LimeWire to Block Copyrighted Work
An anonymous reader writes "Slyck is reporting that LimeWire is working on new code that will block non-licensed material. The new code checks to see if shared material is licensed, if it is not, the LimeWire client will politely inform the user, 'LimeWire can't determine if one or more files have been published under a suitable license. These files will not be shared.'" From the article: "Approximately 3 to 5 days ago, LimeWire developers began working on two new branches, cc_reverify_interval-branch and cc-publish-branch. The code in the first branch works to verify that every file shared has a license. If this is not the case, the file will not be shared. The second branch is for publishing one's own work without a license. According to the release notes, individuals can attach a Collective Commons license if the work is either their own or have permission to distribute the work ... According to a LimeWire beta tester who informed Slyck of this news, this feature is already complete. Developers are simply waiting for the signal to integrate these branches with the main branch, providing Mark Gorton, CEO of LimeWire, decides to go through with this."
...Limewire use will plummet.
Circumcision is child abuse.
The powerpoint presentation was a little murky at this point, the slide in question had the following:
1) Read unknown filename and attributes
2) ????
3) Display error message
4) Profit
They are leaving it to the developers who spent 3 hours handwaving and making grand gestures whilst all the time crossing their toes and hoping they didn't get either fired or berated by the OSS community peers.
liqbase
FBI: Do you have permission from the National Football League and the American Broadcasting Company to record this viewing of Monday Night Football? Peter: Ummm. I only have permission from ABC.
the Courage - Sincere Mistake
... and so on...
BetaVille - Giant in Tokyo
Deleture - Like to dislike you
False Medicine - Special J
The Cops - Every inhale you take
Filenames may vary.
Assuming this does what it advertises, I don't see how this poses a problem. Everyone knows that P2P is mostly used for swapping music by independent artists, as well as large, legal files such as Linux distributions. It isn't a problem to tag these files appropriately.
RIAA: But look, we found these modified versions that bypass it!
LimeWire: Sorry, man, that's not our code. Go yell at them, not us.
Or if you prefer a more geekoid version:
LimeWire (waves hand): This is not the code you are looking for.
RIAA: This is not the code we are looking for.
LimeWire: Our code is clean
RIAA: Their code is clean.
LimeWire: Move along
RIAA: Move along
Karma: Frotzed (mostly due to the Frobozz Magic Karma Company)
But the bad news is that the pendulum has a blade on its end, and is slowly but surely coming closer and closer to our collective body that is chained to the floor in a dark pit while ravenous rats tear away at our flesh. Poe had some incredible foresight, didn't he?
Quid festinatio swallonis est aetherfuga inonusti?
Africus aut Europaeus?
Nowhere. The Limewire fork will be out faster than all use pirates can say 'arrrgh me hearties'
Pre-canned Evolution Links for all those Slashdot holy wars.
And the final -10% are often miscalculated, anyway.
This is what the evil bit is for. All illegal files should have the evil bit turned on.