GitHub - Nikilites/nuzu: Yuzu based repository. If you are a developer and able to continue this project, contact me on Reddit
github.com
Yuzu based repository. If you are a developer and able to continue this project, contact me on Reddit - Nikilites/nuzu
  • sparky@lemmy.federate.cc@lemmy.federate.cc
    851·
    9 months ago

    Forking a repo is not the same as developing it. Any idiot can rehost the existing source code, but all the developers with knowledge of the code base and project just got axed by Nintendo.

    • pivot_root@lemmy.world
      38·
      9 months ago

      This fork doesn’t even have the code for the dynarmic submodule under the externals/dynarmic directory. MerryMage/MerryHime took that down with Yuzu, and it’s a core part of the JIT recompiler.

      Not to mention, the commit history was wiped clean while a new Patreon was created before even touching a line of C++ code (and subsequently realizing it’s missing most of the dependencies).

      • noyou@lemmy.world
        32·
        9 months ago

        Lol it’s literally just a copy with nothing added and he’s already made a Patreon. Yeah no

  • Atemu
    19·
    9 months ago

    Why throw away the commit history?

    • Hawk@lemmy.dbzer0.comEnglish
      40·
      9 months ago

      Also made communities, setup a patron and donation mails.

      This just seems like a dude wanting to scam money out of it and/or taking credit for continued development, disregarding any effort made before the fork.

    • rutrum@lm.paradisus.dayEnglish
      84·
      9 months ago

      One of the problems with Yuzu (to nintendo) was that it contained the encryption keys pulled off nintendo switches. By removing commit history you actually can permanently remove this part of the code. There might be a more clever way to do this. Thats my best guess.

      • NekuSoul@lemmy.nekusoul.de
        15·
        9 months ago

        Although a good guess, this looks more like the work of someone who’s in way over their head and barely knows how to use git. Probably just downloaded the repo as a zip instead of cloning it through git. At least that’s the vibe I get from their commit history and other repos.

        So basically, this person did the right thing on accident.

        • PM_Your_Nudes_Please@lemmy.world
          1·
          8 months ago

          Probably just downloaded the repo as a zip instead of cloning it through git.

          FWIW, this can actually be a valid strategy, purely because a DMCA takedown will affect forks but not reuploads. Basically, if a DMCA takedown nukes a project, it also nukes any forked projects. But if you downloaded the .zip and reuploaded it, you won’t be affected by the DMCA takedown because it’s not considered a fork of the original project.

          It’s a dumb workaround, but it oddly may have helped save a lot of the code simply because offline backups can’t get touched by DMCA or a nuked project.

      • SplashJackson@lemmy.ca
        6·
        9 months ago

        I downloaded and set up Yuza the day before all this went down, and it did not include encryption keys. And trust me, I looked.

      • lad@programming.dev
        2·
        9 months ago

        Except, if someone had the repo cloned before the purge, they would retain all of the information, wouldn’t they?

      • PM_Your_Nudes_Please@lemmy.world
        2·
        8 months ago

        Nope, Yuzu was never distributed with keys. It could use keys that were provided by a user, but you had to add those yourself. Yuzu’s setup page even had (outdated) instructions on how to dump keys from your own Switch.

        Just like how PlayStation emulators aren’t ever distributed with the BIOS, because sharing the BIOS is considered piracy.

      • toastal
        1·
        9 months ago

        Even if there were keys, you could scrub the history instead of deleting it outright

  • stoy@lemmy.zip
    10·
    9 months ago

    What is different about this project? How will they reign in Nintendo’s legal team?