This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
Let's talk about software revocation: when a seller limits or disables their software after release, like an online game shuts down, particularly when customers aren't refunded.
Examples
Egregious example: Microsoft plans to remotely disable Office 2019 and 2021 for Mac. To be clear, this software was a one-time purchase and works completely offline, Microsoft even explicitly stated at one point it would continue to function. I can't even play devil's advocate.
Another example that I personally believe is stupid: when music from games is removed because the songs are licensed for a fixed duration (e.g. GTA4). Because, why include songs with these licensing requirements, when there are plenty of great songs without them? (And I don't think the removed songs from the GTA4 list are especially popular, I don't recognize any of them and only a couple artists.) Many games are simply delisted when the licenses expire; alternatively the licensed songs could be gated only for new users. At least these gamers weren't explicitly told the music would last forever (I assume), they just assumed.
Less egregious cases: when online-only games shut down. It's expensive to keep servers running; if the seller is an individual or small company they may obviously not have the funds. Providing users self-hostable servers can also be expensive: the server code should be changed for consumer hardware and documented, and the client code should be changed with UX and functionality for custom servers, or gamers will have trouble running it. Sometimes, the seller legally can't release server binaries, for IP reasons I don't really understand (the client code has third-party libraries, why is the server code different?). The most justified cases (albeit rare): the game is free-to-play with only temporary (e.g. seasonal) micro transactions, so there's nothing to refund.
The archtypal example: The Crew. A paid game released (by Ubisoft) in 2014 and permanently shut down in 2024 (without refunds). Online was a big part of the core gameplay, but the game had an offline mode which included a single-player campaign. Regardless, when Ubisoft shut down the game, they disabled the online mode and stopped players from re-downloading it. This shutdown spawned Stop Killing Games and lots of discussion about software revocation. Fortunately, the community has created a mod that re-enables the game and emulates its server (The Crew Unlimited).
Reactions
Stop Killing games campaign/NGO (mentioned above). Most known for collecting 1 million EU signatures so the EU Commission must eventually discuss their initiative, they also collected enough UK signatures for a UK parliament debate, and lobby in the US. Their voice has reached mainstream audiences (more or less: the world is so complicated there's not really one mainstream, but besides millions of signatures, they also got endorsed by celebrities including PewDiePie and Notch), but they haven't (physically) accomplished much, yet...
California's Protect our Games act. Passed the state assembly (not yet law). It requires publishers to post a notice 60 days before shutting down their game, and provide some offline functionality or refunds, although it doesn't apply to subscription games (and may have other exceptions). Backed by Stop Killing Games.
French consumer group sues Ubisoft over shutdown of online game 'The Crew': "UFC-Que Choisir alleges that Ubisoft misled consumers about the permanence of their purchase and imposed abusive contractual clauses stripping players of ownership rights". An earlier lawsuit in the US was dismissed. Backed by Stop Killing Games.
Cory Doctorow has (of course) written about this. I still support his crusade against enshittification, centralization, and unreasonable DRM (regardless of underlying goals), but I admit my general opinion of him has lowered, as this recent article has subtle xenophobia.
A road paved with good intentions
Of course consumers shouldn't lose access to things they've bought. You wouldn't remotely shutdown a car, or remotely disable its heating, or make previously-free heating a paid upgrade...(In fairness, the first two were mandated by governments, and the third was walked back.) Back on topic, surely at least egregious cases like Microsoft's are unjustified, so why shouldn't we prevent them via regulation?
It's not so simple:
Generally speaking: regulation doesn't intrinsically prevent anything, it's just a strongly-worded suggestion to the government and population. Moreover, all regulations have drawbacks: they cost money to enforce, discourage businesses, and hurt good-intentioned violators. Selective enforcement leads to the worse of both, where good-intentioned individuals and small businesses are targeted (sometimes frivolously but it still hurts them) while big businesses are ignored; an example I think is copyright, with false DMCA claims hurting individuals while big AI companies train on everything.
Consider the regulation "a software seller cannot disable any offline feature in their client without refunding buyers". Sounds reasonable, right? But what if an indie game developer pushes a balance chance that nerfs an OP character by removing their special ability? What if they remove a poorly-implemented game mode almost nobody was playing? Both of these also sound reasonable, but both can be considered disabling offline features. Even if no indie is successfully sued for such a frivolous reason, a failed lawsuit (motivated by the law) would harm them; even if there's no real lawsuit, the potential may discourage them.
My proposal
For now, media pushback and patches seem to be working for the most egregious cases. The Crew is playable via mod, more games are explicitly stating they won't remove licensed songs, I predict Microsoft will walk back revoking Office and am confident otherwise there will be a widely-available patch.
For the future, I support removing regulations on buyers circumventing end-of-life software, rather than adding regulations on sellers. At least after software becomes "end-of-life" (but preferably in general), there should be no restrictions on hacking the local version, only trying to hack the server. This won't stop determined sellers who put the entire game on the server and don't stream important gameplay logic (effectively recreating Stadia for only their game); but it's an improvement, and that streaming would make their game accessible to gamers with low-end PCs.
If a software license wants to say "you cannot hack the client, ever" then who is the law to prevent that? In general, we allow all sorts of things in software licenses.
To my knowledge, courts only enforce IP law against "hacking the client" projects whenever the companies can prove they're being financially harmed. Most of the time it means they have some version of the service up already. I suppose there might be cases where a very edgy fan fiction tarnishes the brand's IP, but presumably the company does believe there is financial damage in this case.
Well there is one other case, which maybe is the real discussion: if the fan-made project is making money, companies will go after it to get a piece of the pie. I think that's fair. If a company wants to stop service for their online game, I don't think it means the IP should become public domain. For example, the service might be unprofitable after merely 1 year. The company should still be able to expect royalties, for example. Or, be able to veto a fan-made service, even if it is profitable in the market.
I say this as someone who has played MMOs, as someone who is sad many have changed or shut down, and as someone who follows various emulator projects (And am sympathetic to the community).
You’re right about breaking the client. I don’t know why people have a hard time with this. You realize “the cloud,” is someone else’s computer, right? Whether that’s social media or online banking or an MMORPG, it doesn’t make any difference to the point. Client side apps often run in containers like Docker or Kubernetes, which adds a layer of abstraction between the user and the actual application, so you’re not directly in control of the binary to examine. If you’re messing with it you’re often doing things like looking for and intercepting API calls to look for keys, OAuth tokens, looking for misconfigured servers, fuzzing endpoints to look for IDOR and SSRF.
Whether you're messing around to cheat on their systems, playing a joke or have criminal ambitions from their standpoint, they don’t know what your intent is, not to mention your activity is actively damaging the integrity of their infrastructure and impacting them financially. If I was in their shoes, I’d be ‘somewhat’ sympathetic to that viewpoint too. It’s not like dissecting assembly on a Super Mario cartridge. If the product is EOL and being retired that’s a bit of a different issue.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link