this post was submitted on 04 Mar 2024
141 points (98.0% liked)

Emulation

3531 readers
23 users here now

Community to talk about emulation & roms.

RULES:

1.) No bigotry

LINKS:

founded 4 years ago
MODERATORS
lnxprcy@lemmy.ml
141
Help preserve Yuzu's code base (discuss.tchncs.de)
submitted 8 months ago by Rikj000@discuss.tchncs.de to c/emulation@lemmy.ml
4 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.world/post/12733354

As you all know or may not know,
Nintendo has taken down Yuzu,
see following post for more info on that:
https://lemmy.world/post/12728163

Now it's important to preserve the code base of Yuzu,
so hopefully someday, once things cooled down a little,
an active fork can stick it's head up.

After looking at the Azure DevOps Pipelines
of yuzu-emu/yuzu,
I noticed the latest pipeline ran 8 hours ago
as of writing this post:

Which tells us that the latest commit,
was a merge of PR #13198 from
zhaobot/tx-update-20240301020652

This fork,
is the most up-to-date one / contains the latest commit
done to Yuzu before the take down:
https://github.com/zhaobot/yuzu/tree/tx-update-20240301020652

I encourage you all to pull, star and fork this fork,
not only the master branch, but all branches!
The more copies floating out there,
the better the project will be preserved.

You can pull the code base to your local machine, with:

git clone https://github.com/zhaobot/yuzu.git

(Requires https://git-scm.com/)

And you can pull in all the branches,
as described in this Github Gist:
https://gist.github.com/grimzy/a1d3aae40412634df29cf86bb74a6f72

you are viewing a single comment's thread
view the rest of the comments
[–] NuXCOM_90Percent@lemmy.zip 22 points 8 months ago* (last edited 8 months ago)
  1. Probably don't rely on github (or gitlab) for this. This is the kind of thing that (the mechanisms that enable) DMCA requests are built for. And if this is problematic enough, MS just has to make a filter and it will auto-delete any repo (which is pretty trivial with git)
  2. Please, everyone, be wary of building and running any code you get from one of these sources. There is absolutely nothing stopping people from adding in malicious code. I am not sure who I would even trust at this point but, bare minimum, document the git logs and a dozen or so hashes (or all of them) so that you can at least have good odds on detecting if someone tampered with the code.
  3. If your career/goals in life are at all coding related, maybe be a bit wary of forking this into your namespace. Because this doesn't look the best when someone is going through your github/portfolio and realizing you are potentially going to be a headache.