|
Here's the thing: I'm not sure we can, in the long run, have it both ways. Not naturally anyway. The current tendency seems to go towards generalised lock down. It started with game consoles. Then iOS. And now even on the desktop, we see scary warnings from Windows and bypassing signature verification in MacOS is actually difficult if you don't know the procedure already. And soon, maybe those warnings will turn into hard errors? For me to chose an open device, that open device has to exist in the first place. Where is the open equivalent of the PS5? I don't see any. And even if it did: I bet many competitive game would exclusively found in the locked down version. Or, more insidiously, there would be two arena: the locked down one with fewer (or no?) cheaters, and the open one with (presumably) all the cheaters. There would be a strong incentive to get the locked down version for this reason alone, and one isn't going to waste money & resources on a redundant piece of electronics just so they can play without cheats and access the homebrew market. Now that I think of it, there might be a way: how about optional signatures? You'd take the same hardware, and run it in two modes: the open mode, and the signed mode. The signed mode would be thoroughly locked down by the hardware vendor, and run only signed code. This could affect networking too: just sign the encryption keys with the secure chip, and pass that along with a certificate from Nintendo or whoever. That way one would know the communication was initiated in "signed mode", thus guaranteeing the integrity of the game's binary, just like we would in an actually locked down console. Heck, we could go even a step further: have the hardware security module be swappable. That way we can separate the hardware vendor from the certificate authority. Of course, they'd be one and the same by default, but we could still switch for another if we need to. (You could have a tournament specific CA, or the hardware vendor could revoke it's own HSM and send a new one to people.) DRM for the people. Never thought I'd say that. |
Raspberry Pi w/ RetroPi or Batocera. Perhaps sometime in the future it'll be Batocera on a RISCV.
You won't get better because without huge corporate dollars, as is the case with the Linux kernel, Gnome and KDE, you won't be able to fund the QA and devs necessary to do the bullshit boring work that is essential to making certain that consoles are a polished experience; from the operating system through to every game you purchase.
TCRs and TRCs are a thing, after all. You cannot ship without meeting a certain level of minimal tolerable quality.
> And even if it did: I bet many competitive game would exclusively found in the locked down version.
Yes. Of course.
What's in it for the developers when consumers demand anti-cheat measures, which are hideously expensive to maintain, and active and pervasive moderation which is, likewise, hideously expensive to maintain? To say nothing of the _total absence_ of any strong example of a FOSS video game performing well enough to fund a AAA-quality title.
> You'd take the same hardware, and run it in two modes: the open mode, and the signed mode.
Sony has done this twice. There was the PSOne's Net Yaroze, and there was the PS3's ability to run Linux (only for the first few iterations). Consumers didn't care enough for Sony to bother with it again.
IIRC, Xbox One indie developer licenses are still basically almost free.
Your idea is still locked down, though; you cannot run arbitrary code because you cannot cross the signed/unsigned boundaries.
> DRM for the people.
Browsers have this in the form of media extensions.