• 0 Posts
  • 79 Comments
Joined 7 months ago
cake
Cake day: June 5th, 2025

help-circle
  • The American politics are vibe politics. You can have no policies but as long as you say the thing people want to hear people will vote for you. I can absolutely see why some people thought a wealthy criminal who regularly screws people over would side with the working class. Because Trumps campaign did focus on working class issues. It doesn’t matter that his “solution” to those problems was blame the immigrants and he had no real intention of helping the working class. Because for the average American the politics end at “I hear you”. That’s what the average American cares about, having their problems being acknowledged. Actually solving the problems is a problem for a different time.

    That messaging in the right-wing propaganda sphere is just the continuation of the campaign, because somehow it works even when those people see the contradictions on a daily basis.















  • I have to agree that killing online only games makes sense because they can’t be forced to run the server forever, not they can be forced to release the source code. But offline / solo / bots should keep working.

    We are not in agreement. It doesn’t make sense even for online games.

    The politicians statement is not what SKG is about. SKG is not trying to preserve every version of a game. It would be cool if that was also on the table, but that’s not the purpose of the initiative. SKG is concerned with keeping the game playable AFTER the publisher/developer has decided it’s not longer worth maintaining. At that point the online video game is no longer a dynamic service because it’s no longer updated nor maintained. And that means it absolutely could be viewed as a static product. The point she is making is completely irrelevant to the initiative and shouldn’t even be a point of discussion.



  • I’ll rephrase it more clearly then. Selfhosting focuses on the hosting aspect of software. [email protected] focuses on the development aspect of software. This article talks about the architectural decision made during development. It doesn’t talk about how to host serverless. It doesn’t even talk about why you wouldn’t want to selfhost serverless. It talks about bad software patterns the come with serverless. It also talks about the cost of running those things but even that is geared more towards enterprise level devops people.

    It might be an interesting read from the software developer perspective but it’s not interesting from the selfhoster perspective, because the article has nothing to do with selfhosting.