It’s amazing what a difference a little bit of time can make: Two years after kicking off what looked to be a long-shot campaign to push back on the practice of shutting down server-dependent videogames once they’re no longer profitable, Stop Killing Games founder Ross Scott and organizer Moritz Katzner appeared in front of the European Parliament to present their case—and it seemed to go very well.
Digital Fairness Act: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14622-Digital-Fairness-Act/F33096034_en
Games should be required to have reproducible source for all components (client and server) sent to whatever the European equivalent of the Library of Congress is, to be made available in the Public Domain whenever the publisher stops publishing them.
Not only games. Goes for all electronics as well.
Sick of supporting your ‘old phones’? You’re required by law to disclose all binary blobs as source code to let somebody else pick it up the slack.
Feeling like bricking old Kindles? Fine, but users must be able to install alternative OS on your old device.
Not providing software updates for your TV anymore after you removed features? That’s your right, but so is the right of the effing device owner to install something else on it.
And it’s not just consumer electronics. (caugh John Deere caugh).
Not to be pro-corporate/anti-repair…but I feel I have to play devils-advocate here…
That sounds like a legal and security nightmare.
If you just give binary blobs and no sources, there’s no way to maintain the code/device long term. As exploits continue to be found in upstream dependencies, the hardware continues to become increasingly insecure.
But if the source needs to be released…I imagine that there are heaps of proprietary code that is still in use on “active” devices even after another model goes EoL…so if that code is released, there’s instantly thousands of nefarious eyes on it.
On top of the regular zero-days that are found out when a popular product reaches EoL.
I think that’s potentially a lot to ask of users. Will your technically-challenged great-Aunt switch to post-support build when her phone hits EoL, or will hackers be able to remote control her banking app and take away your inheritance before the community can even patch it (assuming there’s enough community support out there for an 8-year-old Galaxy A-series…)
Then there could also be licensed code that would need to be released as well…hence the legal nightmare.
Not saying it’s impossible…in fact, I greatly agree with your stance and stated position. Just saying that there are some blockers on this epic.
Security by obscurity is a myth
No. It’s a valid tactic but needs to be part of a much broader strategy.
Absolute security is unachievable, but it is much harder to probe a black box to understand how it works than reading its entire manual.
This is the dumbest take I have heard in a long time.
That is a bold thing to say at a time when open source projects are being compromised by AI agents finding holes left and right.
But even without that, obscurity is and has always been a valid tactic, despite purists like you saying otherwise.