youtube-dl restored after GitHub reverses DMCA takedown

GitHub has reinstated the popular youtube-dl project after receiving new information that led the company to reverse its earlier DMCA takedown. The platform says the additional details showed the project was not circumventing a technical protection measure (TPM), and the decision aligns with its stated priority of supporting open source developers.

The original takedown, which the RIAA requested, drew widespread frustration from developers in part because youtube-dl has many legitimate uses beyond any potentially infringing ones. GitHub acknowledges that frustration and has outlined several concrete changes to how it will handle future anti-circumvention claims, along with a $1 million fund to help developers facing unwarranted Section 1201 takedowns.

Why the takedown happened

The DMCA requires platforms like GitHub to comply with the law, even when it produces outcomes the company finds unfair to developers. The youtube-dl notice fell under a relatively rare category of DMCA claim: anti-circumvention, as defined under Section 1201.

Most takedown notices GitHub processes allege straightforward copyright infringement. Section 1201 claims are different. The law, which dates to the late 1990s, makes it illegal to distribute technology that bypasses technical measures controlling access to copyrighted works, even if that same technology has substantial non-infringing uses. No similar provision in ordinary copyright law would reach that far.

Anti-circumvention claims make up less than two percent of the DMCA takedowns GitHub processes, and the youtube-dl case was unusual even within that small category.

Code with legitimate purposes

youtube-dl's code can be used to access copyrighted material, but it also serves legitimate and socially valuable functions: changing playback speed for accessibility, preserving evidence for human rights work, assisting journalists with fact-checking, and downloading Creative Commons-licensed or public domain videos.

After the initial takedown, GitHub was able to reinstate a fork of the project when its owner applied a patch addressing the notice's allegations. The maintainer of the main youtube-dl project later submitted a similar patch addressing infringement claims based on unit tests that referenced copyrighted videos. Following that, and after GitHub received new information showing the project does not violate Section 1201's anti-circumvention provisions, the company restored youtube-dl and will offer reinstatement to all its forks.

How GitHub's DMCA process already worked

GitHub's DMCA Takedown Policy was designed with developers in mind, and the company says its existing process already included several protections that exceed its legal obligations:

  • Complete notices required before action: GitHub says it distinguishes between code that merely could be used infringingly and code designed for a specific infringing purpose. It also recognizes that code providing access to copyrighted content may still be lawful—for example, under fair use.
  • A higher bar for Section 1201 claims: Complainants must provide additional information specific to circumvention, describing the technical measures at issue and how the project is designed to bypass them.
  • Notice to repository owners: Affected owners are notified and given options to dispute the claim or modify their code to address the allegations.
  • Transparency: Every processed DMCA notice or counter notice is published in the DMCA repository.

Changes to anti-circumvention review

Going forward, GitHub is overhauling its process for Section 1201 claims. Any credible anti-circumvention takedown claim will now be subject to a multi-stage review before a repository is removed:

  1. Technical experts—including independent specialists retained by GitHub when appropriate—will verify that the project actually circumvents a TPM as described in the claim.
  2. Legal experts will scrutinize the claim to reject unwarranted requests or those exceeding the DMCA's boundaries.
  3. Ambiguous claims will be resolved in the developer's favor; the repository stays up unless there is clear evidence of illegal circumvention.
  4. If the claim is complete, legal, and technically valid, the repository owner will be contacted and given a chance to respond or make changes. GitHub will attempt a second contact if there's no response.
  5. Only after those steps are completed will a repository be taken down.
  6. After a takedown, GitHub will continue attempting to reach the owner to allow them to address the claim and restore the repository.
  7. Owners of taken-down repositories can still export their issues, PRs, and other data that excludes the alleged circumvention code, where legally possible.
  8. Trust and Safety response to such cases will be treated as a top priority so claims are resolved quickly.

All of this happens at GitHub's own cost. The company says it will document and open source the process so other code-hosting platforms can adopt similar practices.

Developer defense fund

Developers who face takedown claims or other intellectual property disputes often rely on non-profits such as the Software Freedom Law Center and the Electronic Frontier Foundation for legal support. But pushing back against an unwarranted takedown can still expose developers to personal liability and legal costs.

To address that, GitHub will establish and donate $1 million to a developer defense fund aimed at protecting open source developers from unwarranted Section 1201 takedown claims. The company says it will work with other community members to set up the fund.

Working to change the law

GitHub acknowledges that process improvements can only go so far while the DMCA itself remains unchanged. The company points to its successful multi-year effort to prevent the EU copyright directive from mandating upload filters for software development as an example of what advocacy can achieve, and says it's applying those lessons to the U.S. as broader DMCA reform is discussed.

GitHub is also engaging with the U.S. Copyright Office's eighth triennial review of exceptions to Section 1201's anti-circumvention provisions, and encourages developers who believe the law is overly restrictive to contact the Copyright Office directly.