El Reg reports
The US Copyright Office is asking the tech industry and members of the public to comment about the Digital Millennium Copyright Act (DMCA), and in particular the rules governing copyright infringement.
Section 512 of the DMCA gives ISPs and internet hosts immunity from prosecution if material that infringes copyright, such as music tracks, is taken down promptly if the entity owning the rights to it protests. "Repeat infringers" are penalized.
[...] The DMCA was signed into law in 1998, and since then flaws have been consistently pointed out in the legislation, not least with section 512. So the Copyright Office wants to know how to improve things.
"The Office will consider the costs and burdens of the notice-and-takedown process on large- and small-scale copyright owners, online service providers, and the general public", the request reads.
"The Office will also review how successfully section 512 addresses online infringement and protects against improper takedown notices. To aid in this effort, and to provide thorough assistance to Congress, the Office is seeking public input on a number of key questions."
In the request for responses, the Office posits 28 questions it would like answered, including how the legislation is working in practice, what legal precedents are affecting its operation, and whether takedown notices are effective. It also asks for any academic studies on the matter.
[...] The guidelines for submissions will be posted on February 1 and the open period for comments ends on March 21, so there's plenty of time to get a submission ready. How much good this will do, however, remains to be seen.
(Score: 0) by Anonymous Coward on Saturday January 09 2016, @03:17PM
> ...It is technically possible, but would be a HUGE burden.
Not that bad if you are willing to accept a partial solution. For just one example, check the first block/page of the file as it's being uploaded and see if that matches anything in the database of previously flagged/infringing files. I believe this is what ScribeD claims to do. Or look at the file length and checksum (or other easily computed "fingerprint"). If you get a match, flag for possible (C) violation, most of the kids uploading a copy aren't going to bother making small changes to the file. A slight improvement would be to compare using a few different offsets, in case the header changed length.
Google must do a lot more than this when they crawl the web and index it? Google is nice enough to send me an auto Alert which I have set for the book title and other related search strings.