mastodon - Link to source

Slop-free FOSS ๐Ÿ–‘๏ธ


FOSS apps, projects, and services with accounts on the Fediverse that do NOT use AI, LLMs, Claude, vibe coding, etc.

fedidevs.com/s/MTA2OA/

#NeverSlop

Slop-free FOSS ๐Ÿ–‘๏ธ - Mastodon Starter Pack

FOSS apps, projects, and services with accounts on the Fediverse that do NOT use AI, LLMs, Claude, vibe coding, etc. #NeverSlop
fedidevs.com

Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)

2026-09-27 03:54:20

mastodon - Link to source

I should make a list of FOSS apps, projects, and services that have Fediverse accounts and don't code with AI, then strike them from the list with a big ELIMINATED notice if they do start drinking the slop kool-aid.

EDIT: Made one fedidevs.com/s/MTA2OA/

Honorary mentions
infosec.exchange/@catsalad/117341552145650963


#neverslop

reshared this

in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
friendica (DFRN) - Link to source

Carlos Solรญs

Don't forget to always have one finger on the block button, and one eye on the retractions list. Fortunately that list above added the latter for this kind of cases, I'd recommend adding a notification whenever the page changes so you're on the safe side.
in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
mastodon - Link to source

Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)

Bevy only has one co-authored by Claude commit, however their AI Policy does indeed allow for LLMs, so....

โš ๏ธ ELIMINATED


@bevy :aneobot_explode:

We are wary of the use of AI in the development of Bevy, and are particularly troubled by its impact on artists, but tolerate careful human-driven AI use in some code-related areas consistent with the above values.

Skip swap-chain texture acquisition for windows with no camera targetโ€ฆ ยท bevyengine/bevy@62379cf

โ€ฆ (#23276) # Objective Fix a file descriptor leak on Adreno 740 (Quest 3) caused by unnecessary render passes on windows that no camera is targeting. `prepare_windows` calls `get_current_texture...
GitHub
@Bevy
in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
sharkey - Link to source

Raeve

github.com/bevyengine/bevy/issues/23418#issuecomment-4088119141
Their response to this being discovered was effectively 'Ew, fuck, our bad...' and they'll purge it eventually.

Losing your shit at such a large project letting one commit slip through, a project lead-maintained by a visibly trans dev for that matter, is a bit dickish, tbh.

Update LLM policy? ยท Issue #23418 ยท bevyengine/bevy

How can Bevy's documentation be improved? I would like to preface this by saying I am neither a lawyer nor an expert on Bevy's policies, and I think a lot of incredible work has been done in this p...
ethanuppal (GitHub)
in reply to Raeve
mastodon - Link to source

Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)

@raeve Oh the one Claude commit is not why I removed them from the list, it is that they "tolerate careful human-driven AI use in some code-related areas" (as per their AI contribution policy)

AI Policy

Bevy, as a project and a community, values: Quality: Creating a reliable, high-quality foundation for others to build on Growth: Developing understanโ€ฆ
bevy.org
@Raeve
in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
sharkey - Link to source

Raeve

You're doing the impossible dichotomy thing where a glorified autocomplete must be argued entirely out of every usage in a way that fully exhausts their maintenance efforts until they give up, because somehow that shitty autocomplete is so pervasive and obvious that it will overtake regular human effort in the repo with lazy hallucinatory garbage.

Or maybe they'll just do what you don't seem to have continued reading about, this crazy thing called having standards that shitty autocomplete will either fail to meet or be indistinguishable from human-written code and otherwise evasive of enforcement without disclosure.

in reply to Raeve
sharkey - Link to source

Raeve

Yeah, in fact, I fully fucking agree with their assertion: Zero-tolerance doesn't work. Slopcoders will just try to hide it better. When they make it clear that they will grill a submitter on their rationale and understanding and that they won't accept discussion or documentation written by LLMs (the hard part, mind), I feel like this presents a better trap than trying to argue every little code completion.

This isn't a permissive policy, it's a "Go on, try it, we'll rip your balls off during review" policy.

in reply to orfanik
mastodon - Link to source

Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)

@orfanik @kde TBD...

circumstances.run/@davidgerard/117311106218081864

David Gerard

2026-09-21 21:17:04

mastodon - Link to source

lol, the attempt to ram through a pro-slop KDE policy just got closed yet again because people found out about it

invent.kde.org/plasma/plasma-workspace/-/work_items/187#note_1648917


Proposed KDE LLM guidelines (#187) ยท Issues ยท Plasma / Plasma Workspace ยท GitLab

This is a continuation of this mailing list thread about "fully LLM-generated merge requests, preserved at https://mail.kde.org/pipermail/kde-devel/2026-September/004496.html There, I proposed...
GitLab

@KDE @orfanik
in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
mastodon - Link to source

KDE

@orfanik

floss.social/@kde/117325537492794402

KDE

2026-09-24 10:27:08

mastodon - Link to source

We apologise if any of our messaging over the past days has created confusion. For the sake of clarity:

1. KDE is open, diverse and accepting and we have the track record to prove it. Please come join us and see for yourself.
2. KDE does not harbor "fascists" and we have the track record to prove it.
3. We are not writing a set of "pro-LLM" policies. Quite the contrary. The current draft actually restricts its use much more than currently codified.

[Continued >]


@orfanik
in reply to Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)
hometown - Link to source

voxel

not sure how strict your requirements are for inclusion here but Inkscape has a few (openly) claude AI 'assisted' commits, i.e gitlab.com/inkscape/inkscape/-/commit/eb8e143091e1

Don't access GtkRecentManager when running headless (eb8e1430) ยท Commits ยท Inkscape / inkscape ยท GitLab

When Inkscape is run without a display (e.g. `inkscape input.svg --export-type=png` with no X11 DISPLAY), gtk_init_check() fails and a plain Gio::Application is created instead of a Gtk::Application. The gtkmm wrappers...
GitLab
in reply to voxel
mastodon - Link to source

Cat ๐Ÿˆ๐Ÿฅ— (D.Burch)

@voxel The full LLM policy is being actively developed but appears to lean towards banning generative AI

gitlab.com/inkscape/inkscape-board/-/work_items/5#note_3140424828

Oh, and there's also this:
social.treehouse.systems/@dysfun/116182391411729473

gaytabase (@dysfun@treehouse.systems)

inkscape is hiring 2 c++ developers. they have a big red warning box saying absolutely fuck off with your genai
gaytabase (Treehouse Mastodon)
@voxel