523
Ban AI Slop? (lemmy.ml)

I had a report for AI slop today. 1m LOC in 3 months. How do you even modify and distribute that? I do not think we had a rule against it.

IMHO if we allow, the community gets drowned out by AI vomit and it is harder to see handcrafted loved projects that are easy to modify and distribute.

My mind is to ban it to preserve open source.

Are folk in agreememt with this line? Would love to hear your thoughts.

you are viewing a single comment's thread
view the rest of the comments
[-] Spite_By_Design_LLC@lemmy.dbzer0.com 2 points 3 days ago* (last edited 3 days ago)

The current 32.71 snapshot includes both source code and APKs compiled there from. I take your point that I should make that correspondence clearer, along with which future interim releases might have no public source.

At present, under the definitions you've provided, the current release meets all four FOSS criteria.

As for "sanitising", I mean removing private configuration, credentials and development files, not stripping out functional source code. That's literally all I meant.

As I've said, development happens in my private Forgejo repository, so preparing a public snapshot involves a little housekeeping. I prefer to keep the public release clean, and .gitignore only does part of that job.

I appreciate you being civil. The other points I raised are worth serious community consideration (especially what constitutes "slop", AI disclosure, and the unintended consequences of penalising transparency rather than judging projects on their merits), but I have said my piece.

this post was submitted on 21 Sep 2026
523 points (93.7% liked)

Open Source

50147 readers
453 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 7 years ago
MODERATORS