Post by @xgranade@wandering.shop

2026-09-28 18:04 UTC

@cthos@mastodon.cthos.dev @nivex@tenforward.social If only there was a resource for figuring out which projects have gone slop. I joke, because yeah I fucked up with how I contributed to open-slopware, but I do think there needs to be *something* of that form, if only just to inventory the damage that will eventually need repaired.

Replies (3)

@skyfaller@jawns.club 2026-09-28 18:15

@xgranade@wandering.shop @cthos@mastodon.cthos.dev @nivex@tenforward.social I still believe that anything without a policy against slop has to be assumed to be slop. My personal betrayal of the week was Lagrange, the best (actively maintained) Gemini client in my experience: https://github.com/skyjake/lagrange/issues/801 https://github.com/skyjake/lagrange/blob/dev/CONTRIBUTING.md I'm not sure how much slop is currently in the repo, but it's now clear they are fine with future slop code. This has made me less interested in the Gemini protocol. Now I need a slop-free stack for Gemini, more extra work.

Open ##4886672
@ShadSterling@mastodon.social 2026-09-28 18:47

@xgranade@wandering.shop @cthos@mastodon.cthos.dev @nivex@tenforward.social I still don’t think you were as wrong about that as you said you were. I don’t remember what all the problems were, it’s not like I think it was perfect, but at the time it seemed like a reasonable first draft. And as more projects have embraced slop the need for a way to find projects that haven’t has only grown

Open ##5106986
@MrDOS@hachyderm.io 2026-09-28 19:35

@xgranade@wandering.shop @cthos@mastodon.cthos.dev @nivex@tenforward.social The list at https://codeberg.org/ethical-foss/open-slopware is becoming alarmingly long.

Open ##5106994