Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Do forks go away together with the original repository when it's removed from Github?


In this case it seems so, someone just uploaded the codebase again (archived): https://github.com/emmauss/Ryujinx


5 years out of date though, it would seem.


Here's a more up to date one: https://github.com/Synthlight/Ryujinx


Codebase, but no releases...


They used to handle releases through github actions, so it should be fairly straightforward to set that up


Edit: I guess I'm wrong, see reply

If a repository is removed by Github in response to a DMCA request, yes.

(But it's not clear that that's what happened here.)


The forks aren't actually automatically taken down in most cases. The claimant must list every individual fork in the claim. Which I love, because it's kind of petty but still following the DMCA to the letter.

Here is an example[1] of the form claimants must fill out.

> Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down

[1]: https://github.com/github/dmca/blob/master/2024/05/2024-05-3...


IIRC it took them a couple months to get through all of the Yuzu forks after the initial DMCA and lawsuit. I doubt there were nearly as many forks of Ryujinx, though.


Depends on which type of removal they do, but they can be yes.




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

Search: