As we’ve seen, this can lead to situations where GitHub is required to remove code-even if it has a multitude of non-infringing uses-if it is in fact designed to circumvent a TPM. Why did GitHub process this takedown in the first place?Īs a platform, we must comply with laws-even ones that we don’t think are fair for developers. In this post, we provide answers to common questions about the DMCA and why GitHub handled this case the way we did, describe why circumvention claims deserve special treatment, and share how we’re updating our policies and fighting to improve the law. We know developers want to understand what happened here, and want to know how GitHub will stand up for developers and refine our processes on these issues. And our reinstatement, based on new information that showed the project was not circumventing a technical protection measure (TPM), was inline with our values of putting developers first. Our actions were driven by processes required to comply with laws like the DMCA that put platforms like GitHub and developers in a difficult spot. And so we share developers’ frustration with this takedown-especially since this project has many legitimate purposes. Today we reinstated youtube-dl, a popular project on GitHub, after we received additional information about the project that enabled us to reverse a Digital Millennium Copyright Act (DMCA) takedown.Īt GitHub, our priority is supporting open source and the developer community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |