• yhvr
    link
    fedilink
    English
    arrow-up
    142
    arrow-down
    1
    ·
    edit-2
    3 months ago

    I hate to be that guy, but it doesn’t seem like there’s anything to this fork. At least a few links in the README don’t work, and the domain for the “email” is actively for sale. The owner of the repository doesn’t seem to have any real previous projects on their GitHub account.

    I can understand that it’s a new fork, but in my mind you’d want to at least make sure the Readme is… passable before you spread the word and make a Patreon for the project.

    EDIT: The Patreon link has been removed since I made this comment. I’m still incredibly skeptical of the project though

    • WarmSoda
      link
      fedilink
      English
      arrow-up
      75
      ·
      edit-2
      3 months ago

      I would say don’t make a freaking patreon for it. You know what companies hate even more than people using thier IPs? Getting money while doing it.

      • IllNess@infosec.pub
        link
        fedilink
        English
        arrow-up
        48
        ·
        3 months ago

        This looks like a straight cash grab. I bet the whoever owns this github won’t work on it at all.

      • cm0002@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        19
        ·
        3 months ago

        Nah fuck that, let’s all make a patreon for every. single. fork.

        Let’s see if Nintendo’s unlimited legal budget is unlimited or ISP “unlimited”

        • viking@infosec.pub
          link
          fedilink
          English
          arrow-up
          26
          ·
          3 months ago

          They have a bunch of lawyers inhouse who do this as part of their day job. Sending a cease & desist to github and patreon costs them nothing extra, and neither of those will fight Nintendo in court to protect IP infringements.

          • ClaraBecker@threads.net@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            3 months ago

            Conservatively, if several thousand forks appear, they may hire an additional person and cost themselves a couple hundred thousand. Given your point, there must be a more effective way to be an attrition-based nuisance.

        • berg
          link
          fedilink
          English
          arrow-up
          4
          ·
          3 months ago

          Go ahead, be the change you want to see.

    • pivot_root@lemmy.world
      link
      fedilink
      English
      arrow-up
      24
      arrow-down
      1
      ·
      edit-2
      3 months ago

      Yeah… I looked at the project’s subreddit, and I don’t expect it to last long. The creator’s idea of avoiding Nintendo’s legal team boils down to “assert emulation is legal and condemn piracy within our dev team and community.”

      I don’t mean to be a dick, but I don’t think the guy knows what he’s doing. The only way an actively-maintained fork is going to avoid the same fate is if they either give up before Nintendo cares, or:

      • Stripped out the code that gave Nintendo’s argument validity in the first place;
      • Did not make money off the project; and
      • Stayed far the hell away from retail game emulation, focusing on perfect compatibility for homebrew entirely.

       

      Even then, there’s a good chance they’re screwed either way. The original Yuzu devs agreed to Nintendo’s terms of explicitly naming Yuzu as a circumvention tool. Settlements don’t serve as precedent, but I suspect it’s going to be extremely hard to argue that a minimal derivative of a circumvention tool is not still a circumvention tool when the original creators stated they designed it as such.

      • yhvr
        link
        fedilink
        English
        arrow-up
        8
        ·
        3 months ago

        I’m sure a lot of forks will pop up right around this time. I’ll be less skeptical of them once I see actual commits made to the codebase instead of things like just changing the readme