Live data from Hacker News

YouTube-dl has received a DMCA takedown from RIAA

github.com

871–880 of 1001 posts

Re: YouTube-dl has received a DMCA takedown from RIAA

#871

Everybody, go to PyPi: https://pypi.org/project/youtube_dl/#files Download the whl. Download the tar.gz. ???? Profit. Also, a recommendation for the youtube_dl crew is to use a self-hosted solution (if GitHub/GitLab/SourceForge wont do). Find a cheap Linux hosting provider and run Gitea on it: https://github.com/go-gitea/gitea It's the best tips I can give for now.

I was also able to apt install it on my distro, but the version I got was too old to actually work. So I cloned one of the git repos mentioned in this thread (Chinese copy) and ran it from there.

Re: YouTube-dl has received a DMCA takedown from RIAA

#873

Where can I find youtube-dl now? I'm ready to be a sponsor for the project to live further.

Search in this thread (across multiple pages), a number of people have posted mirrors. You can clone, rehost, and share.

It would be ironic if this backfires on them because of the Streisand effect.

Re: YouTube-dl has received a DMCA takedown from RIAA

#874

Earlier quoted context omitted.

What if collaboration on opensource projects (i.e. hosting, issues and their comments) was decentralized instead of relying on a central entity like Github? That would keep the developer base active and make DMCA takedowns ineffective.

> What if collaboration on opensource projects (i.e. hosting, issues and their comments) was decentralized instead of relying on a central entity like Github? That would keep the developer base active and make DMCA takedowns ineffective. But decentralisation would also make it harder to verify the code is legitimate. Would you trust a copy of something like this from an anonymous server?

Well, git commits can be signed by they're authors, verifying authenticity.

This would prove if malicious commits have been added to a mirrored repository.

Re: YouTube-dl has received a DMCA takedown from RIAA

#876
post #824

Your weekly reminder that 1. You should not have your development process on a centralized platform, at least not if you're doing anything that smells of copyright issues 2. If you do host on a centralized platform, have regular, decentralized backups of code and issue tracking. 3. Also, avoid US-centric hosting for this kind of thing. But really, refer to 1.

I'm a contributor to gallery-dl and it occurs to me this exact same scenario can happen there. So I at least set up a cron job to backup the issues in case it gets trolled. Its the only really problematic part to get taken down from Github.

Thanks ... your tool seems to be the solution for my problem :D

Re: YouTube-dl has received a DMCA takedown from RIAA

#877
post #105

Earlier quoted context omitted.

The fact that copyrighted works were included in the readme shows it was intended for that use, and the RIAA complaint will likely stand up to any legal scrutiny. Just because it can be used for legit purposes too won't matter in the slightest. I mean, Napster could have been used for legal means as well, and it got destroyed in court. The only chance tools like this have legally is when infringement is an "unintende…

"Napster could have been used for legal means as well, and it got destroyed in court." But Napster was a service run by an organization. youtube-dl is neither a service nor an organization. It's just some source code floating around the internet, to which volunteers contribute to. A very different situation. If anything, it's Youtube itself that's like Napster, and it's telling that the RIAA has gone after youtube-dl…

RIAA already went after YouTube. That’s why Google added the ability to scan for copywritten material. Google wanted YouTube to be a friendly place for people to view content. That meant playing ball with RIAA.

Re: YouTube-dl has received a DMCA takedown from RIAA

#879
post #37

Earlier quoted context omitted.

I was thinking the same thing: The next step following this line of thinking would be trying to ban all torrent clients, because they CAN be used to download copyrighted material. This is crazy.

Why stop with torrent clients? They should ban all browsers, because they CAN be used to download copyrighted materials!

Let's just ban internet protocol, while at it. :)

On a bit more serious note I wonder how much internet traffic is used for "illegal" purposes?

Post reply on HN