I really doubt that they are that stupid. My guess is that they are hoping to hinder the development of the project for a bit to delay the switch 2 implementation in yuzu or a future switch 2 focused fork.
Also, all the ppl that were directly associated with the group are no longer legally allowed (or at least would risk a lawsuit against them) to contribute. So a lot of expertise got lost.
Okay, how would sintendo know if some of the original Yuzu devs are working on it if there is no trail leading back to them? If I were a Yuzu dev, I’d just start a new account and get right back to work on a fork that is gaining traction just to spite those subhumans working for a legal dictatorship.
Even if that were perfect, you’d have to make sure to never make a mistake. One commit with the wrong account or not using whatever you’re using to mask where you’re from and you’re toast. Also there needs to be no other identifiers. It’s almost certainly not worth the risk for them.
It would make it harder to compensate the devs for sure, though. They lost their finances and whoever picks the project back up will need to build their revenue stream from scratch although I feel that a good portion of yuzu contributors will just start funding one of the forked projects.
The only reason Switch emulation is as far along as it is is because they made a mistake with the hardware in the Switch’s 2017 model. As long as they don’t make a mistake like that again, they’ll probably be fine.
Physical access is the one thing you can’t shield a device from permanently. Eventually you have to relinquish some security to let users play on their consoles, or allow your service teams the ability to debug and repair it.
Those will always be the way in for anyone with the will and means to reverse engineer your system.
Modern systems being built on open hardware (compared to their predecessors) is a big thing too. ARM and x86 are easier to debug and emulate than Cell, for example.
all the ppl that were directly associated with the group are no longer legally allowed (or at least would risk a lawsuit against them) to contribute. So a lot of expertise got lost.
Sure, the core “Yuzu” team. That doesn’t include any of the external contributors. There’s very often a larger contributor base outside of a core team in FOSS projects.
And yes, there’s expertise that was lost. But that doesn’t mean no one else knows how to do the work. It will march onwards.
I really doubt that they are that stupid. My guess is that they are hoping to hinder the development of the project for a bit to delay the switch 2 implementation in yuzu or a future switch 2 focused fork.
Also, all the ppl that were directly associated with the group are no longer legally allowed (or at least would risk a lawsuit against them) to contribute. So a lot of expertise got lost.
Exactly this. Nintendo lawyers were after the people, not the project. Else they’d go after Ryujinx too (they may still to be fair)
Okay, how would sintendo know if some of the original Yuzu devs are working on it if there is no trail leading back to them? If I were a Yuzu dev, I’d just start a new account and get right back to work on a fork that is gaining traction just to spite those subhumans working for a legal dictatorship.
Because you’d need perfect infosec to pull this off
An anonymous git account and tor?
Even if that were perfect, you’d have to make sure to never make a mistake. One commit with the wrong account or not using whatever you’re using to mask where you’re from and you’re toast. Also there needs to be no other identifiers. It’s almost certainly not worth the risk for them.
Lol. Sure because those ppl are not publicly known. Coding style, writing style on issues etc.
Opsec can be hard especially when you have to have a public facing entity.
Just simply too much risk for having nothing to gain only to lose.
But you are not. And you are just talking and doing nothing.
It would make it harder to compensate the devs for sure, though. They lost their finances and whoever picks the project back up will need to build their revenue stream from scratch although I feel that a good portion of yuzu contributors will just start funding one of the forked projects.
This is the correct answer.
It’s like destroying a barracks full of elite soldiers and then going, “Don’t worry. We have plenty more barracks.”
The only reason Switch emulation is as far along as it is is because they made a mistake with the hardware in the Switch’s 2017 model. As long as they don’t make a mistake like that again, they’ll probably be fine.
Physical access is the one thing you can’t shield a device from permanently. Eventually you have to relinquish some security to let users play on their consoles, or allow your service teams the ability to debug and repair it.
Those will always be the way in for anyone with the will and means to reverse engineer your system.
Modern systems being built on open hardware (compared to their predecessors) is a big thing too. ARM and x86 are easier to debug and emulate than Cell, for example.
I wasn’t referring to the Yuzu core team.
Sure, the core “Yuzu” team. That doesn’t include any of the external contributors. There’s very often a larger contributor base outside of a core team in FOSS projects.
And yes, there’s expertise that was lost. But that doesn’t mean no one else knows how to do the work. It will march onwards.
They have no way of knowing who they verbally communicate with if they’re intent on passing along info at least lol