[1] in https://github.com/github/dmca/blob/master/2020/05/2020-05-0... someone forked a permissively-licensed project; the original author made the project-closed source, then issued a DMCA takedown against the fork. That's clearly bogus: you can't revoke an open source license.
[2] in https://github.com/github/dmca/blob/master/2019/11/2019-11-2... Microsoft DMCAd a project that did something with Windows local licensing keys. I can see how Microsoft would prefer that this project not exist, but I see no infringement. Not everything that a big company dislikes is an infringement of copyright.
0: https://github.com/github/dmca/blob/master/2020/10/2020-10-0...
1: https://github.com/github/dmca/blob/master/2020/01/2020-01-1...
2: https://github.com/github/dmca/blob/master/2019/09/2019-09-0...
How in the world is Github allowing this?
Github basically has no choice here, they must take it down immediately and then they or the creator has to fight to get it back up.
The law is set up for DOS attacks.
btw, Popcorn time is a bit different situation. I would say bit torrent is more the problem, or at least the people who upload pirated content.
What is odd though is that it's the RIAA filing suit here and not google. Google has a real complaint, RIAA certainly does not.
It would be like if NYT went after a web client for saving news articles for offline reading.
Bizarre.
Probably not wanting to poke a hornets nest of the open source community.
Because Microsoft can afford lawyers to fight this, and random GitHub projects can't. It's an intimidation tactic.
The aim is fear.
I guess I’m nitpicking but it’s important that they’re not “filing suit”, possibly because they don’t care enough or don’t think they have a case. DMCA takedown is a sort of dispute resolution process mandated by law, it’s not a substitute for an actual lawsuit.
To prove tortious interference with a contract, a plaintiff must establish several elements, including that The defendant’s conduct led to a breach of the contract; and The plaintiff suffered damage as a result.
The question would be whether Github users suffered a breach of contract for having any of our repos potentially shut down for a reason that involves a third party's claims of violation of DMCA.
There's also unseen elements at play. If you're publishing semi-anonymously, the counter-claim process can deanonymize you.
Republishing the same content at a slightly different URL is the obvious, cheapest solution.
Very few people have been able to claim damages from false DMCA takedowns, although the DMCA specifically allows for it.
The same thing will probably happen here because this is not one of the purposes of DMCA takedown letters, period. Even if there are inappropriate test cases or something in the repo, or if they’re correct that youtube-dl bypasses DRM in violation of a different part of the DMCA, it’s still not a valid takedown because GitHub isn’t hosting anything the RIAA/those it represents own the copyright to. The correct way to do this is to go after the lead youtube-dl developer(s) and/or GitHub for facilitating infringement or whatever, but I don’t think RIAA wants to do that because they probably don’t have much/any legitimate grounds for legal claims against them, so they abuse the DMCA to look like they’re doing something.
Edit: for a more concrete picture of what happens next, read GitHub’s DMCA policy.[2] Basically youtube-dl can file a counter notice assuming they disagree with the claims, after that the RIAA has 10-14 days to get a court order or the repo goes back up.
[1] https://torrentfreak.com/github-reinstates-popcorn-time-code...
[2] https://docs.github.com/en/free-pro-team@latest/github/site-...