open-slopware – Alternatives to FOSS projects choosing to use LLMs/AI
smartmic
28 points
14 comments
October 09, 2026
Related Discussions
Found 5 related stories in 282.7ms across 8,999 title embeddings via pgvector HNSW
- Protecting our FLOSS commons from LLMs acmnrs · 11 pts · July 23, 2026 · 64% similar
- The state of open source AI rellem · 407 pts · July 17, 2026 · 58% similar
- Open weights are not open source: Why AI's favorite label is under dispute pseudolus · 13 pts · September 15, 2026 · 57% similar
- The growing divide between AI hype and software engineering reality jruohonen · 60 pts · August 29, 2026 · 56% similar
- Extensible Software in the age of LLMs coloneltcb · 137 pts · August 19, 2026 · 56% similar
Discussion Highlights (11 comments)
warkdarrior
Here comes the AI inquisition!
Tiberium
Some of these are, in my opinion, extreme. From their README: === Condones the use of AI/LLMs to ingest the project's contents. This can be for "understanding the code better", "finding bugs/security issues/optimizations". This tag is to be used independently for projects that generally reject the use of AI in their code repositories, issue trackers, and sponsorships, but still encourage or permit users to use LLMs to ingest their code base. This is independent of a project's licensing. This tag is to be used for the maintainers' statements about, or reactions to, the usage of LLMs/AIs to ingest the repo. The reason we still find this worthy of a tag is because it: - means that the LLM, often provided by a company with very little respect for copyright, will then save a copy of that open source repo for use in it's future outputs. - still encourages people to use LLMs and carves out a special situation in which they're still OK, but as this repo is against AI/LLMs for more than just "poor code quality" reasons, we still believe this is not a good course of action as it still promotes the use of inherently unethical tooling. Evidence may be, but is not limited to: - An AI or Contribution policy that carves out a space for "using LLMs to understand the code" or "finding bugs" - Core maintainer using or accepting the use of AI for finding bugs or security issues === If I understand it correctly, if someone merely opens an issue in an open-source project and says something like "Claude helped me find this issue", and the maintainers don't immediately close it, then they get on the list in the repo.
rishabhaiover
it recommends SiriDB as an alternative to PostgreSQL :)
msub2
Part of me understands the sentiment behind a list like this but disavowing this much just feels impractical. Suggesting that anyone who wants to do 3D game development at all might be able to use LÖVE as an alternative (no shade to them, I know some folks doing cool LÖVR stuff) just doesn't feel that helpful. And Servo? Seriously? The one browser engine with a very stringent do-not-send-us-AI-generated-PRs policy? I dunno man. I think we all have our own personal lines and they draw theirs pretty harshly.
ranger_danger
Love how the Linux kernel is ironically on the list, and yet they willfully ignore it and keep using Linux.
VariousPrograms
This feels like a hobby or special interest rather than a list of genuine software recommendations, unless you're running CoffeeBSD and browsing the web with Netsurf.
collinfunk
Ironically, the maintainers of this repository are equally talented as vibe coders, since they simply maintain a markdown file and nothing else.
dimava
When I read "open-slopware" I wanted to see OSSlop Adobe forks Now I'm disappointed -_-
mbStavola
The fact that this list is so long and grows longer every single day just shows how this line in the sand has become untenable to uphold in reality. I suppose it's good to be informed at least?
jkahrs595
Anybody else remember the latch batch of old farts who retired early because they refused to learn how to use a computer? I guess we’re onto a new batch of old farts.
cyberrock
The Other OS section should include TempleOS.