51–60 of 69 posts
> unauthorized use of WhatsApp APIs Does that actually have anything to do with copyright or trademark, or are they just very takedown-happy lawyers?
Earlier quoted context omitted.
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. [1] http://www.chillingeffects.org/dmca/counter512.pdf
With $19B in pocket they can totally ruin his life with a lawsuit.
Earlier quoted context omitted.
And surely taking action against parties who exploit that fact is their solution.
How does an security PoC and API library fall under the DMCA? See this comment: https://news.ycombinator.com/item?id=7273662 From what I recall, the DMCA is about copyright and trademark infringement.
That said, this takedown looks pretty bogus to my (untrained) eye.
Earlier quoted context omitted.
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. [1] http://www.chillingeffects.org/dmca/counter512.pdf
With $19B in pocket they can totally ruin his life with a lawsuit.
With the poor, let's say terrible, security posture WhatsApp always had, this is really not the way to communicate the message that they care and want their software to be scrutinized. Open implementations are a great help to any reverse engineer trying to figure out the mess that is their protocol. This is exactly what triggers full disclosure.
You know what was pathetic? With all its security and authentication loopholes people still used it. I gave it up for time but friends still won't listen and then I had to come back. Now, Facebook is sth I can't tolerate. At least earlier I didn't run the visible risk of my very intimate messages falling into advertisers' hands.
Earlier quoted context omitted.
> Interesting. Trademark law is probably pretty strong against repositories named "WhatsApp" or something very similar. Using the logo without permission as well. They probably fall under nominative use, which is an affirmative fair use defense. Describing an API or implementation of XYZ as a "Webclient for XYZ" should be fine.
Agreed. It's not as if there aren't a zillion other Github repositories using trademarks in their names. Consumers of open source will generally understand the distinction between official libraries and third-party-developed libraries, and if trademark law is reasonable (IANAL), it should accept even "whatsapp" repos as fair use since no "reasonable person" would be confused. But it requires someone willing to fight…
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.wha…
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. [1] http://www.chillingeffects.org/dmca/counter512.pdf
Earlier quoted context omitted.
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. [1] http://www.chillingeffects.org/dmca/counter512.pdf
There's still a mandatory 10(?) day delay before the content can be reinstated.
https://github.com/davidgfnet/wireshark-whatsapp
My apologies for the bile, but I can't help but call out my reactions to this news...
1. facebook (you: I expected this from, you we're already #1 on this s#17list) 2. whatsapp (sell-out!) 3. github (highly disappointed watching you just lay down and immediately comply shutting down these repositories)
I'm considering moving all my code off of github over this...