1426
Stop Killing Games delivers 'absolutely incredible' hearing in European Parliament: 'There was no [parliament member] that wasn't responding positively' (www.pcgamer.com)
submitted 5 months ago by to c/technology@lemmy.world
231 comments fedilink hide all child comments
 

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.

Official Stream: https://multimedia.europarl.europa.eu/en/webstreaming/committee-on-internal-market-and-consumer-protection-ordinary-meeting-committee-on-legal-affairs-com_20260416-1100-COMMITTEE-IMCO-JURI-PETI

Digital Fairness Act: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14622-Digital-Fairness-Act/F33096034_en

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 5 months ago (4 children)

I firmly disagree that this would be a good use case. Allowing this kind of container shenanigans would introduce more incompatibilities than it solves.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 5 months ago (3 children)

    I firmly disagree that this would be a good use case.

    Why ? Any technical reason beside your dislike for containers, in this specific scenario ?
    Remember that we are talking about software that probably is built with older version of the OS as target, using older version of tools and libraries. The source code could not be compilable anymore without a porting, which can be not that easy.

    Allowing this kind of container shenanigans would introduce more incompatibilities than it solves.

    It depends on your objective.
    If the goal is to be able to continue to play a game which require a server, having the publisher to release a container solve your problem, you just run it and you can continue to play the game, which if I am not wrong is the ultimate goal of all the Stop Killing Games initiative.

    If the publisher only give you the server binary (and all the dependencies) there is way to be sure that the next OS update does not break something, assuming you are able to run it in the first place.

    The source code you say ? Fine, when the copyright end, after 70 years, they will release it in the public domain, until then... good luck, laws are on their side.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 5 months ago (2 children)

    Why ? Any technical reason beside your dislike for containers, in this specific scenario ?

    Because jailing a container is even harder than jailing an application. "But a container is already jailed" you'll say - I don't trust any jail that I can't choose & configure myself.

    If the publisher only give you the server binary (and all the dependencies) there is way to be sure that the next OS update does not break something, assuming you are able to run it in the first place.

    The source code you say ? Fine, when the copyright end, after 70 years, they will release it in the public domain, until then… good luck, laws are on their side.

    How about: document the requirements for the execution environment (in industry this is called an interface definition document), based on which the gaming community can then generate their own container configs if they like, but no one has to run stuff in a container.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 5 months ago (1 child)

    Because jailing a container is even harder than jailing an application. “But a container is already jailed” you’ll say - I don’t trust any jail that I can’t choose & configure myself.

    Fair enough.

    How about: document the requirements for the execution environment (in industry this is called an interface definition document), based on which the gaming community can then generate their own container configs if they like, but no one has to run stuff in a container.

    Also a good solution but you will end up in a container anyway once the requirements will become too old to be satisfied on a current OS.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 5 months ago

    Also a good solution but you will end up in a container anyway once the requirements will become too old to be satisfied on a current OS.

    That might be - but depending on the platform, that container is trivial or not necessary at all (e.g. wine on Linux still runs 16 bit executables with just a config file). Also, until then, I can continue to run the game without worry. E.g. Unreal Tournament 99 still worked out of the box (last I tested) on Debian 12 - haven't tried it yet on Debian 13.

  • permalink
  • fedilink
  • source
  • parent