Notice that the user who received the temp ban went on to complain about it, and even after other users explained why the memes were racist (including the zuckerberg post that you also agree is racist), the user dismisses the racism entirely and just says “not arguing everyone has to like the memes.” They are showing zero ability for self-reflection and refuse to acknowledge the memes were racist.

I still would’ve given a permaban based on the evidence at hand, were it my community. You can disagree with that and give them more and more chances, but posting one blatant racist meme which is indisputably racist (even you agree), shows that we’re not working with some innocent lamb who just isn’t keeping up with modern dog-whistles.

If someone had only posted the LOTR meme without that previous history, then I would give benefit of the doubt, and just remove it and explain why.

Their previous history of racist posting was pretty clearly taken into account, it wasn’t some random LOTR fan who happened to get misconstrued.

You may want to look up racist dogwhistles, and how they are used. Equating migrants to an invasion horde is a common racist dog whistle and fearmongering tactic.

It truly is, and learning that virtually every DE is also using it was a wake-up call for me of how deeply this has infiltrated FLOSS projects (I would’ve assumed they would be less apt to jump on the band-wagon, especially after the environmental and ethical concerns became apparent, but… Most don’t seem to care too much, if at all about that).

Especially disheartening that the kernel is turning such a blind eye to all this and ignoring you. They seem to be setting an example for other FLOSS projects to follow. I feel like it’ll continue until some of them get slapped with serious infringement cases, then maybe that’ll cause at least some to take action against LLMs.

Strange, how is it that you can see the posts that were deleted?

I assume I can still access them due to being an instance admin, that’s how I know what they were.

What’s racist about that?

I explained how that imagery is used by racists, and the previous racist meme is a good indicator it was posted with racist intent.

Notice that there’s 2 posts that were removed for racism. The other one was posted 15 days prior, and was an image of a black mark zuckerburg with a comment below it implying that that was the version who steals data, which is clearly a racist post. The moderator who removed it added the comment “Next racist post gets a perma-ban”.

The post with the Cueta post that got them banned had the post title of ‘Cueta right now’, but was an image of an invasion from Lord of The Rings, equating the Cueta migrants as essentially a ‘barbarian horde’, which has traditionally been used by right-wing media as a racist scare tactic to make their viewers see non-white migrants as evil hordes who are ‘invading’ their country.

Both memes were clearly very racist, but despite that, they only received a temporary 1-week ban (I would’ve given a permanent ban for such blatant racism, myself).

An update on the different DE’s stance on AI:

• LXQt won’t ban AI, and will allow code contributions.
• MATE’s Contributing.md on github explicitly allows AI contributions that are marked as AI.
• Budgie has Claude submissions right in their github.
• KDE’s team is divided somewhat, but ultimately accept AI code.
• Gnome allows AI code on most of their projects.

That leaves Cinnamon and Cosmic, both of which are currently unknown on their stance. If they turn out to both be pro-AI, that would mean most major DE’s are pro-AI, leaving us with the Window Managers to investigate like i3, Qtile, etc.

Edit: I see Qtile has claude contributions already so… Egh…

Also update regarding the MATE desktop, I found in their Contributing text that they are following the Linux Kernel’s lead on accepting LLM code, with only a requirement to tag it as being AI-assisted.

AI-assisted code receives no special treatment compared to human code. If disclosing AI assistance, use the Assisted-by format adopted by the Linux kernel guidelines. Do not use Co-Authored-By with AI tool accounts or vendor emails, as it pollutes the commit history.

So they’re off the table as well :\

The Labwc wayland compositor (which MATE uses for wayland support), has similar guidelines in its Contributing file.

That’s exactly the type of thing I had in mind! Thanks for the heads up :D

Dome Keeper is a really fun up-to 4-player co-op game about digging for minerals beneath a dome and defending it from creatures on the surface who try to break in every so often.

https://store.steampowered.com/app/1637320/Dome_Keeper/

It’s mostly a chill game, but the defense of the dome can be exciting, though only one player needs to actually man the defenses, the rest can continue to mine below ground.

I saw a couple standout titles like A Short Hike (polished cozy game) and Neon Struct (thief-like). I’ll see if there’s anything else that jumps out at me.

Edit: Eldritch is a rather good rogue-like Cthulhu survival horror.

Dungeon Bodega Simulator looks fun.

Deep Space Exploitation looks good.

Hyper Gunsport looks like a fun multiplayer game.

The Wratch’s Den looks neat.

I believe FreeBSD currently doesn’t allow LLM’s either, at least for now due to licensing concerns (I get the vibe they’d be open to it if it was deemed ‘safe’ from a licensing standpoint, so if the court ever made a decisions that makes them feel safe, they’d probably open it up to it).

Realistically though, both BSD and Haiku would be a pretty drastic downgrade in overall usability from reduced software and hardware support compared to Linux, and at least at this point, that’s a bit too big of a sacrifice to make :(

I plan to start probing other DE’s who have yet to make a public stance on LLMs in hope of finding at least a few that can be considered a safe haven.

KDE unfortunately is also accepting AI/LLM code contributions, as is LXQt and Gnome.

This news has made me realize it’s not going to be trivial to avoid AI slop FLOSS projects, we’re likely going to need to collectively collate a list of known anti-AI projects, and probe projects that haven’t taken a public stance to find out what’s safe and what’s not.

An unfortunate update; a user from the other thread on this went and asked LXQt developers their stance on LLMs, and they responded they accept AI contributions, and will not ban the practice. :(

Ah man, that absolutely sucks. I went and read all of their responses. You did a fantastic job presenting a compelling case to them, thanks for taking the time to engage with them to find all that out.

I’m starting to see that avoiding slop even in the FLOSS world isn’t going to be trivial, and more are jumping on board than I anticipated… I’m thinking it may be necessary and worthwhile to probe as many widely used FLOSS projects as possible on their stance to then compile the results into a list on codeberg (so others can contribute their findings as well), to make it easier for people to find software that refuses to use AI.

Maybe calling it the Slopless Software Project?

Gloomwood is the only close spiritual successor, but its been in early access for a long time (though it does still get substantial updates).

My crumpet

Agree 100%.

Honestly, as a silver lining, this is likely to finally make studios pull back from graphics being the end all be all, and instead focus a bit more on art styles that run well on weaker hardware.

The endless pursuit of graphics has had drastically diminishing returns since the PS3, it’s about time the industry focused on optimization and doing more with less for once.

It’ll let our hardware stay relevant, and it’s better for the environment if we make it last as long as possible anyway :)

Down with consumption, and bring on the age of Permacomputing, I say!

This comment in a different thread from someone who used to work for them gives some great background as to why.

The other day I tried installing Star Wars Dark Forces 2 from disk, complete with a ‘windows 95/98 compatible’ blurb on it. Heroic launcher got the installer running without issue and within a few minutes it was playing.

I ended up using the Openjkdf2 engine instead for some nice quality of life improvements, but it was still quite something to see Linux run a piece of software from 1997 so effortlessly.