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 -
I think that generally, it’s harder for game companies to successfully even threaten a frivolous lawsuit, than to defend a legitimate one.
The game company’s lawyers can defend the government’s lawsuit, or the hobbyist sued for bypassing EOL-not-EOL software can get enough people and attention on their side to recover any financial damage and Streisand the game company.
The problem with adding regulations is that they may be applied to smaller devs. Removing regulations, so that some smaller devs’ software may be deemed EOL too early, is less of an issue; because smaller devs already have weaker DRM and lawyers, and thus rely on good faith to defend against piracy (which seems to work well enough).
We have examples now that show this isn't how it will work in practice. I think the recent case around Bambu Labs' software is illustrative.
I won't go into all the details but what I find notable about that case is that, when served with a legal threat, the developer who made a workaround to now-removed functionality immediately took it down without any attempt to fight a legal case. This happened despite a significant number of people interested in his success and despite the developer appearing to believe the threat was legally unsupported.
It shows very clearly that legality is not sufficient to protect game preservation efforts. Under the current legal system threats of legal action often work even if the target believes the case is meritless.
I'm not convinced the requirements from Stop Killing Games will be much of a concern for small developers. They're far less likely to use DRM and turning off Steam's DRM would put basically all of them in the clear of even your more stringent requirements. They're also far more likely to stop supporting a game because their company has gone bankrupt, at which point fines for non-compliance are irrelevant.
I'm far more concerned that SKG and similar laws will be added to the pile of laws that are effectively unenforced than I am about seeing them enforced strictly on small publishers.
Of course he did, because others already forked it. And if Bambu still tries to sue him, Louis Rossman has pledged to pay his legal fees.
The FULU repository went up May 12. The developer took his repository down on April 23rd.
Apparently he received the threats from Bambu in late April. Unless some very fast-paced discussions happened behind the scenes, he could have had no idea a replacement would go up when he took his repository down.
Furthermore, is FULU maintaining the code or just re-hosting the original? Now the developer is out of the way all Bambu needs to do is make a small change to obsolete the backed-up version.
He pledged $10,000. This is good of him but probably insufficient for even a simple legal case, and doesn't cover the personal cost of dealing with this either. Fundraising might cover the rest if the developer actually gets sued. I wouldn't want to take that bet. Would you?
Others went up earlier: https://github.com/dafik/OrcaSlicer-bambulab
Nowadays, when a popular repository goes down, one can be confident someone will upload a backup, even with a weak legal threat
(Although it's not the only possibility and maybe they're wrong) that Bambu didn't make this small change is evidence they expect someone would fix the repository.
Not personally, but the multiple people re-uploading the repository are.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link