The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
61–70 of 292 posts
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#62The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#63To me the most interesting (and new to me) part is §Cease and Desist Notices: > Following our initial coverage, we learned that the pressure against YouTube-DL had already started weeks earlier in Germany. Law firm Rasch, which works with several major music industry players, sent out cease and desist orders in the hope of taking YouTube-DL offline. > Hosting service Uberspace was one of the recipients. The company h…
It's probably worth mentioning that Uberspace is based in Germany, not the United States, so may not feel the same risk from not obeying the DMCA as a US company.
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#64The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
I started downloading from youtube because of this. I haven't come across RIAA protected content but who knows what the future holds
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#65Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#66The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#67The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
As someone who uses youtube-dl for all the videos online, it's presence in any repos isn't as important as it may seem, because it breaks from time to time for some websites and you need to update it in order to keep using it, which is only easy if you keep it in your home directory so you can just run youtube-dl -U once it breaks.
I would no longer expect FDroid now to keep doing this if they risk a DCMA letter that takes out their entire repo.
And I would assume a shitton of users use yt-dl code through another GUI application, rather than directly through an EasyInstall/virtualenv/whatever. And will most py repos still dare to host/link this code if the risk is a DMCA letter to their ISP?
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#68The takedown didn't backfire at all just because some people decided to publish on Twitter a tarball that still happens to be hosted in many other places so there is absolutely no risk of it getting lost. The problem is that the project may not survive this. Major distributions for example will no longer carry the project and likely refuse to touch it even with a ten-foot pole (think media codecs situation). It will…
I have never been able to get youtube-dl to work with (both ubuntu / mint) distro packages. The packages always fall out of date due to youtube changing things, and you need to download it directly from the youtube-dl website regardless.
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#69I mean, it's nice that the Github CEO doesn't agree, but if the solution is to get it back on Github, then it isn't really a solution. Smaller projects won't get this kind of attention. What this whole episode should do is make it more common place to use tools like git-bug and mirror repos. Maybe someone will even write a tool to do so easily. But what I see happening is people just wanting the status quo to stay. U…
Re: RIAA’s YouTube-dl takedown ticks off developers and GitHub’s CEO
#70> GitHub’s CEO suggested that YouTube-DL won’t be reinstated in its original form. But, the software may be able to return without the rolling cipher circumvention code and the examples of how to download copyrighted material. Which is frustrating. Isn't the information needed to do this provided by youtube themselves? This isn't some private key that wasn't supposed to be public; it's literally given out every time…
I also find it laughable to claim that a session token is a "rolling cipher". If the claim is to be taken at face value, it would ban any form of scraping, as most sites invariably use some sort of session token.