this post was submitted on 03 Jul 2025
66 points (100.0% liked)
Stop Killing Games
259 readers
20 users here now
[EU/UK] Stop Killing Games:
The consumer movement to stop game publishers from destroying older games with kill switches.
The goal is to reach 1 million signatures in the EU so that the european parliament will respond to the initiative that then leads to regulation that requires end-of-life plans for games to stay playable.
Progress Tracker:
UK Final Day 14/7/2025
EU Final Day: 31/7/2025.
founded 1 month ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@QuadratureSurfer @skg looking at the code of the progress tracker, the tracker website makes direct requests to ECI every 3 seconds without even waiting for the previous requests to finish{0}.
The large number of people keeping this tracker open could very well be the cause of the overload:
https://github.com/Alex1337F/StopKillingGamesTracker/issues/25
Closing the progress tracker and maybe reducing its exposure a wee bit until it's fixed sounds like a good idea :blobcateyes:
Maybe the team behind ECI should have expected this kind of load, sure, but it's what we have today and it'd be a shame to lose the initiative to this :blobcatfacepalm:
edit: oops, looks like Lemmy misinterpreted my notation for "footnote links" out of square brackets and rendered this post in a broken way, let's see if curlies help
edit²: there is a PR that intends to stop new update requests from firing when an earlier request is unfinished: https://github.com/Alex1337F/StopKillingGamesTracker/pull/26 — which should help *somewhat*
{0}: https://github.com/Alex1337F/StopKillingGamesTracker/blob/master/main.js#L972-L973
Is it making those requests per user, or making them once and then sharing the results with all users?
@QuadratureSurfer best I can tell, per every instance of the page open. So roughly per user.
The requests are made straight from viewers' browsers to ECI.
Yikes, that doesn't scale well!