4 ms·
I could diasgree about the unit tests because I could argue the script only circumvents copy controls, not access controls (if any member of the public can acce
by 1vuio0pswjnm7 6y ago
I could diasgree about the unit tests because I could argue the script only circumvents copy controls, not access controls (if any member of the public can access those videos on YouTube). Because the RIAA letter provided no location of an infringing copy to be taken down, I can argue the letter cannot be a section 512 notice. Further, the content taken down by Github in response to this letter was not an infringing copy.
It is not clear that the unit tests, if performed, amounted to anything more than fair use. Under the DMCA, it is not necessarily infringement for the script author to circumvent copy controls; section 1201 prohibits sharing copy control circumvention technology with others but does not prohbit the act of copy control circumvention.
If one wanted to make the argument that DMCA 512 safe harbor applies to a section 1201 notice, then I am surprised there has been no mention of "material that is the subject of infringing activity". This language is found in section 512 and in many standard DMCA notice instructions, e.g., Microsoft's
https://www.microsoft.com/info/MSDMCA.html https://www.microsoft.com/info/MSDMCA.html
The youtube-dl script itself is not infringing material. However is it "material that is the subject of infringing activity". If the script only works to circumvent copy controls not access controls, then those unit tests, i.e., the making of unauthorised copies, that may have been performed by the developers, i.e., suspected "infringing activity", are subject to a defense of fair use. If it is fair use then it is not infringing activity and the script cannot be "material that is the subject of infringing activity".