GitHub - GreemDev/Ryujinx: Experimental Switch emulator written in C#
github.com
Experimental Switch emulator written in C#. Contribute to GreemDev/Ryujinx development by creating an account on GitHub.

Looks like owner of Ryujinx changed and now is developed by someone else? The top contributor for this is gdkchan, the previous owner and main developer. So this is not simply a fork, but changing ownership of the original repository. Is that right? It makes sense, because what happened previously is that gdkchan got a message (or visit) from Nintendo to stop working on the emulator. That’s all. There was no cease and desist to the entire project, or anything like that (unlike with Yuzu).

Edit: Another hint that this is the original repository is, that a message is displayed that I have blocked a certain user who contributed to this repository. This message does not popup on any of the forks.

Edit 2.0: I may have been wrong: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.

And looking in the list of forks, the oldest one seem to be 1 month old or so.

  •  mox   ( @mox@lemmy.sdf.org ) 
    19•19 hours ago

    It’s a bit of a leap to say the “owner” changed. Ryujinx is MIT licensed, allowing anyone to clone the original code locally, build upon it, and publish it to a public host. Looks to me like that’s what happened here: a fork, but without using github’s built-in “fork” feature, perhaps to avoid being included in a mass take-down. There are others on non-github sites, although I don’t know if they have been getting new commits.

    I don’t see any reason to think the original repo was renamed or moved to another user’s account. The top contributor is gdkchan presumably because gdkchan’s commit history was preserved.

    For the record, gdkchan’s last commit to the original repo was on 2024-10-01.

    Edit: The README confirms what I thought:

    This fork is intended to be a QoL uplift for existing Ryujinx users. This is not a Ryujinx revival project.