They reinstated the repo without going through the usual DMCA counter-notice process. Which would require youtube-dl to file a counter-notice, and then to wait some amount of time for the original complainer to respond, before reinstating the content.
I think there are few if any major other hosts who would have done this -- although perhaps with the example set here, more will going forward?
Honestly, I don't totally understand how you can get away with being as protective of the person receiving a takedown notice (in this case developer) as github has been, under the DMCA. It is unusual.
Compare for instance to gitlab.com's DMCA workflow. (Which it is amazingly awesome that gitlab has all their policies/workflows like this public and transparent, which github does not, true!). Following this workflow, youtube-dl would still be down, until/unless "there was a valid counter-notice and no response has been received from the plaintiff within 10 days of the counter-notice being forwarded"
So yes, I would say that github has already acted in a way to stand up for developers, in reinstating youtube-dl already, and in changing their policies for the future further. Even in their present actions, they seem to be really pushing at DMCA safe harbor allowances.
Yeah. The way I understand it GitHub is really putting their money where their mouth is. The easy way out is to push the liability onto the user by making them file a counter-notice. This way GitHub is taking on some liability.
I'm guessing youtube-dl might be a really strong case for GitHub if they'd happen to get sued, so it makes a lot of business sense to take a stand on it. The get much needed goodwill from the developer community and get to send a strong message they're not interested in being the messenger for weak DMCA claims.
GitHub/Microsoft management deserve credit for recognizing the long term value (to them) of pushing back hard against frivolous DMCA claims.
The thing is, Microsoft can actually afford a LOT of risk of legal bills in return of developer goodwill, apart from how strong a case it is. Especially since Github somehow seems to have been losing developer goodwill lately.
This is not a dig -- few companies can afford to take a legal risk that Microsoft can (even on a strong case, most companies couldn't afford the legal bills of standing up to RIAA), and it's GREAT that they are choosing to, setting a standard.
It will in fact be really hard for gitlab to do similar though, they can not afford a lawsuit from the RIAA like MS can. (And the RIAA is really unlikely to sue MS unless they really think they have to, cause they know they're outgunned_.
I think there are few if any major other hosts who would have done this -- although perhaps with the example set here, more will going forward?
Honestly, I don't totally understand how you can get away with being as protective of the person receiving a takedown notice (in this case developer) as github has been, under the DMCA. It is unusual.
Compare for instance to gitlab.com's DMCA workflow. (Which it is amazingly awesome that gitlab has all their policies/workflows like this public and transparent, which github does not, true!). Following this workflow, youtube-dl would still be down, until/unless "there was a valid counter-notice and no response has been received from the plaintiff within 10 days of the counter-notice being forwarded"
https://about.gitlab.com/handbook/engineering/security/opera...
So yes, I would say that github has already acted in a way to stand up for developers, in reinstating youtube-dl already, and in changing their policies for the future further. Even in their present actions, they seem to be really pushing at DMCA safe harbor allowances.