GitHub Defies RIAA Takedown Notice

GitHub has reinstated the code for a project previously removed following a demand from the RIAA, after determining the organization’s DMCA claim lacked justification. YouTube-dl, a program enabling users to download videos from streaming platforms for offline access, is once again operational – and GitHub is revising its policies and allocating a million dollars to a legal defense fund to address similar challenges in the future.

The situation arose in mid-October when the RIAA submitted a DMCA notice to GitHub, alleging that YouTube-dl infringed upon copyright law by both offering a means to bypass DRM and by featuring examples of potentially infringing songs within its documentation.

GitHub, similar to many technology companies, generally accepts the validity of complaints originating from established sources like the RIAA, and initially acted on the claim by removing YouTube-dl and publishing the notification.

Many observers pointed out that characterizing this project as a tool for circumventing DRM is comparable to labeling a recording device as an instrument for music piracy. Its applications extend far beyond that, encompassing areas such as research, accessibility, and integration with other applications to facilitate features like watch-later lists, among other uses.

A derivative version of YouTube-dl, excluding the references to popular YouTube videos used as examples, was quickly brought online. However, after receiving a communication from the Electronic Frontier Foundation, a digital rights advocacy group, GitHub recognized an error in its initial response.

As detailed in the EFF’s letter (and likely suspected by GitHub’s technical team), the YouTube-dl project did not violate the DMCA. The RIAA’s assertion that the documentation suggested song piracy was simply a test, streaming brief excerpts of videos to demonstrate the software’s functionality – a practice protected under fair use principles.

Furthermore, the RIAA misinterpreted the functionality of YouTube and YouTube-dl, incorrectly identifying a portion of the video site’s code as encryption and claiming the tool unlawfully bypassed it, thus violating section 1201 of the DMCA. They also cited a legal case to support this interpretation.

In reality, as the EFF explained, the code performs no such action, and the way YouTube-dl’s agent “views” a video is indistinguishable from a regular user’s activity. All processes occur openly and without the use of hidden code or unauthorized access. The EFF also noted that the referenced court case was flawed and, being a German ruling, not applicable under U.S. law.

GitHub, seemingly acknowledging its hasty and complete acquiescence to the RIAA’s poorly substantiated claim, announced several policy changes to prevent similar incidents going forward.

Firstly, all copyright claims based on section 1201 – which are inherently questionable – will undergo thorough technical and legal scrutiny, with independent review if necessary, to verify their accuracy. If the findings are inconclusive, the project will remain accessible during the investigation. If a violation is suspected, developers will have an opportunity to address the concerns before any removal. And even if a takedown occurs, developers will retain access to crucial data, such as pull requests and bug reports.

Secondly, GitHub is establishing a $1 million developer defense fund to assist developers on the platform against unfounded section 1201 claims. Many independent or amateur developers may abandon their projects when faced with potential legal battles, a result that those abusing the DMCA often anticipate.

Thirdly, the company will continue its advocacy efforts to revise the DMCA and similar legislation worldwide, with a particular focus on section 1201, with further announcements expected shortly.

This situation has a positive resolution, and while DMCA abuse remains a significant and ongoing concern, the RIAA was unsuccessful in this instance. Until legal reforms are enacted, this issue will persist, but continued awareness and assertive communication will be essential in the meantime.