this post was submitted on 22 Apr 2026
1203 points (99.6% liked)
Technology
84019 readers
3935 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Releasing source code isn't without extra work. My point is, unless you make sure to specifically target the companies abusing gamers, you're going to mainly hurt the part of the industry that is not the problem.
There's no need to release any source code if your game doesn't require an internet connection to your server to run in the first place.
Do you think only big studios make games that need an internet connection? Or why is this comment relevant?
The important part is "to your server".
Mostly big studios/publishers put "always online" requirements in single player games for a start. And even if it's not only big studios, those requirements can be omitted without effort (if anything it reduces effort to not put them in).
Multiplayer games are a different beast, but I'd argue that yes, small studios rarely make games that exclusively rely on the developer's own servers for multiplayer. That is because they are smaller studios and server architecture for a multiplayer game is a big investment for them. Even if I'm wrong there, future games can be designed with the legislation in mind (this would not affect existing games retroactively) and don't have to keep using centralized server architecture for everything.
Again, I never disagreed with the issue: (90%) solo games requiring an internet connection disappearing suddenly is a major issue in the gaming industry
I disagree with the solutions people want for it, which I find shortsighted.
And yes, such a legislation would force to rethink some designs, and force using one over the other not because it fits the final product better, but because it does not have the additional pressure of compliance. And that, I think, makes it a poor solution.
What I'd like to see is something similar to minimal warranty in the EU. So, a game has to provide X years of playability, clearly shown on the product page/box. They can guarantee longer if they wish. They then have a legal obligation to keep it online. Add to it a mandatory warning X years before shutdown.
Then the consumer is no longer deceived, and the studio has less pressure to comply with EoL requirements.
And why not make releasing the source code a viable way to comply with these requirements, and have a special label for "forever playable" games, either fully singleplayer or through code release.
Just don't force every studio to release their codebase.
It's not "extra" if it's a legal requirement.
More to the point, I'm not saying it has to be licensed as Free Software or that it has to be made immediately public. I'm saying that a copy needs to be sent to a government archive, regardless of how messy it is, so that the government can make it public later when the company doesn't care anymore.
This shows me you don't work anywhere near software. It is not as easy as you think it is.