Hacker News new | past | comments | ask | show | jobs | submit login

I believe the entire network is suspended.



A downstream dmca suspends the upstream? That astonishes me. Anyone down to shut down react?


According to https://docs.github.com/en/site-policy/content-removal-polic..., even an upstream dmca doesn’t suspend downstream by default (unless the copyright owner claims they believe all forks violate copyright) — so I would be surprised if downstream dmca suspended upstream.

NB: according to https://www.gtlaw.com/-/media/files/webinars/ian-ballon-may-..., page 4-470, it’s possible that failing to process a DMCA notice may only lead to losing safe harbor for the material identified in the notice, not for the entire service.

So GitHub might just choose to ignore the notice for React, get sued, and win, all without losing the safe harbor.

For less popular repos, I would not be surprised if you could take down any repo literally by submitting a completely bogus notice.

But honestly I still don’t know how much leeway - legally - service providers have in applying their own technical/legal expertise when evaluating DMCA notices. I’d appreciate any sources (court decisions, textbooks, whitepapers, descriptions of actual industry practices, etc) on the topic.


> So GitHub might just choose to ignore the notice for React, get sued, and win, all without losing the safe harbor.

It wouldn't be React getting the notice. It would be say, someone forking React, then adding a pull request with some clearly DMCA-violating material.

Then, if downstream B DMCA shutdown doesn't affect upstream A's availability, there's still the question of A normally still having access to B's non-merged commits even in the case of B's deletion. So, A should still be access the DMCA-violating material.

And, if A's access to B's non-merged, DMCA-violating commit is truly revoked without affecting A otherwise... why can't we have a "Strong Delete" button on GitHub? Would seem they'd have to have "Strong Delete" functionality to comply with downstream B hitting DMCA.

Basically, I'm feeling either a violation of principle of least astonishment, or a violation of "strong-DMCA".

Unless this is to support a feature in Git/GitHub that I am too noob to understand. :shrug:




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: