I own one of the affected repositories, and submitted the original link to HN the moment I got an email notification about it from Github [1]. It's a shame we didn't get the discussion going earlier.
IANAL, but what the hell does a security POC (and an unofficial API derived from it) have to do copyrights? On what grounds did a repo get chosen for takedown? Is it the "whatsapp" in the name? What about a simple "x.whatsapp.net" connection string in the code? Is that infringement?
You're aware that you have rights under DMCA too? File a counter-notification[1] explaining why you think the takedown isn't valid and Github will likely put the repo back online. And if WhatsApp doesn't like it, they can sue you.
Assuming you're filing a counter-notice in an instance where you have a good faith belief that the original takedown notice is in error, and that you can support that belief, it's rather unlikely that the counter-notice alone will make the supposed copyright holder more disposed towards litigation. Especially if they knowingly misrepresented matters in the takedown, opening themselves up to damages and attorney's fees.
In any case, they can already sue you regardless of whether a takedown notice is issued in the first place. :)
large money crush imagination and suck all the life out of creativity, of all people zuck should've entertained huge ecosystem of various clients that suit other people's needs...
IANAL, but what the hell does a security POC (and an unofficial API derived from it) have to do copyrights? On what grounds did a repo get chosen for takedown? Is it the "whatsapp" in the name? What about a simple "x.whatsapp.net" connection string in the code? Is that infringement?
Either way, shitty move by WhatsApp.
[1] - https://news.ycombinator.com/item?id=7230041