Jump to content

GitHub Defies Copyright Cops, Restores youtube-dl


steven36

Recommended Posts

Last month, GitHub removed a popular tool that is used to download videos from websites like YouTube after it received a DMCA takedown notice from the Recording Industry Association of America. For a moment, it seemed that GitHub might throw developers under the bus in the same fashion that Twitch has recently treated its streamers. But on Monday, GitHub went on the offense by reinstating the offending tool and saying it would take a more aggressive line on protecting developers’ projects.

 

ooBebmV.jpg

 

Youtube-dl is a command-line program that could, hypothetically, be used to make unauthorized copies of copyrighted material. This potential for abuse prompted the RIAA to send GitHub a scary takedown notice because that’s what the RIAA does all day. The software development platform complied with the notice and unleashed a user outcry over the loss of one of the most popular repositories on the site. Many developers started re-uploading the code to GitHub in protest. After taking some time to review the case, GitHub now says that youtube-dl is all good.

 

In a statement, GitHub’s Director of Platform Policy Abby Vollmer wrote that there are two reasons that it was able to reverse the decision. The first reason is that the RIAA cited one repo that used the youtube-dl source code and contained references to a few copyrighted songs on YouTube. This was only part of a unit test that the code performs. It listens to a few seconds of the song to verify that everything is working properly but it doesn’t download or distribute any material. Regardless, GitHub worked with the developer to patch out the references and stay on the safe side.

 

As for the primary youtube-dl source code, lawyers at the Electronic Frontier Foundation decided to represent the developers and presented an argument that satisfied GitHub’s concerns that the code circumvents technical measures to protect copyrighted material in violation of Section 1201 of the Digital Millennium Copyright Act. The EFF explained that youtube-dl doesn’t decrypt anything or breakthrough any anti-copying measures. From a technical standpoint, it isn’t much different than a web browser receiving information as intended, and there are plenty of fair use applications for making a copy of materials.

 

Among the “many legitimate purposes” for using youtube-dl, GitHub listed: “changing playback speeds for accessibility, preserving evidence in the fight for human rights, aiding journalists in fact-checking, and downloading Creative Commons-licensed or public domain videos.” The EFF cited some of the same practical uses and had a few unique additions to its list of benefits, saying that it could be used by “educators to save videos for classroom use, by YouTubers to save backup copies of their own uploaded videos, and by users worldwide to watch videos on hardware that can’t run a standard web browser, or to watch videos in their full resolution over slow or unreliable Internet connections.”

 

It’s nice to see GitHub evaluating the argument and moving forward without waiting for a legal process to play out, but the company went further in announcing a new eight-step process for evaluating claims related to Section 1201 that will err on the side of developers. GitHub is also establishing a million-dollar legal fund to provide assistance to open source developers fighting off unwarranted takedown notices. Mea culpa, mea culpa!

 

Finally, the company said that it would work to improve the law around DMCA notices and it will be “advocating specifically on the anti-circumvention provisions of the DMCA to promote developers’ freedom to build socially beneficial tools like youtube-dl.”

 

Along with today’s announcement, GitHub CEO Nat Friedman tweeted, “Section 1201 of the DMCA is broken and needs to be fixed. Developers should have the freedom to tinker.”

 

Source

Link to comment
Share on other sites


  • Replies 3
  • Views 907
  • Created
  • Last Reply
1 hour ago, zanderthunder said:

Victory to Github, RIAA is a loser.

It didn't matter if they reinstated  it or not  it was being  made at gitlab   the whole time it was  down at github .   I got 2 updates from gitlab . They should of never took it down to begin with because it don't break DRM and is used in lots of legit apps. It benefited githubs agenda  anything that really breaks drm was never restored . It still  more easy to fork  it on another site . People who want to code iffy software should use other  options  or at lest back every thing up  on a backup repo  somewhere  else.

 

Quote

Forks are not automatically being reinstated. Fork owners must re-fork from the parent repository. This is per an official email from GitHub Support.

 

GitHub has to review it. The best thing that came out of it was  Github setup a legal defense fund to fight against bogus DMCA . But  if the app really  is piracy it still  will be removed.  It's yet to be  seen will they become  better at fixing things than the fork youtube-dlc it has sites fixed  in it it that  broke in youtube-dl.  I  be switching back and forth.

 

Also the RIAA  has not lost yet this most likely means  if the can't get it banned they will go after  Google to use  real DRM  and you  will have to get your music  somewhere else  unless  they make a app  that break  it and  due to the shitty  quality  of there audio i only stream it and download it from other  places already. Only  i download  music videos  and  concerts  from YouTube  not audio  only any site  has better quality downloads  .

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...