this post was submitted on 21 Sep 2026
509 points (94.1% liked)

Open Source

49234 readers
188 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
 

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.

top 50 comments
sorted by: hot top controversial new old
[–] eremophila@lemmy.zip 1 points 6 hours ago

Definitely agree

[–] basiliscos2@lemmy.ml 3 points 6 days ago (1 children)

I think the new category - "open source and hand-made/human crafted software" should be introduced

[–] eremophila@lemmy.zip 1 points 6 hours ago

Shouldn't that just be the default though?

[–] horus_son_of_isis@lemmy.world 1 points 5 days ago

A lot of people are making well-reasoned arguments about human nature, the nature of a dangerous tool, defining responsible use, and the challenges inherent in any sort of ban.

The points that look the best to me definitely include tagging, but I haven't seen suggested any method of gatekeeping as to who has access to the means of dissemination of software. Because the damage by the tool is determined by the one who wields it, only people who have established trustworthiness should be allowed to contribute.

[–] _hovi_@lemmy.world 142 points 1 week ago (2 children)

Yeah I don't think we need slop projects being posted here. I know a lot of people are using these tools even for personal projects nowadays but tbh I'm not really interested in exploring any project heavily written by AI.

[–] WhatAmLemmy@lemmy.world 43 points 1 week ago* (last edited 1 week ago) (4 children)

I'm conflicted. I'm anti-AI due to distrust in capitalism and our pseudo-democratic plutocracies, the profit motive to replace the human workforce, the reckless criminal-incompetence of its implementation, and apparent stupidity of the average hairless primate in understanding that you can never trust a correlation engine... but it's just a tool, and I've also found it incredibly useful in my limited and controlled usage; getting it to write small functions or blocks of code, then amending and composing them myself.

How do we determine what is "heavily written by ai", and all the obvious slop factory bullshit, without banning strong projects who are just leveraging it for legitimate dev work; as a glorified autocomplete, test autofill, etc but still read and validate every line of code?

Like most people, I'm finding it increasingly difficult to find trustworthy projects amongst the see of amateur slop, but I think banning it out-right would likely result in many false positives, and ultimately be counter-productive.

As much as I don't want to depend on metrics, I think a better approach would be to define a bunch of heuristics based on historically-competent projects. Things like defining an upper limit based on LoC vs commit time and number of devs, project age, etc. Ultimately I feel the industry should do what cybersecurity should be doing; moving to some sort of cryptograhically-verified social trust model where engineers/professionals have to build trust in the real world, and take turns in "vouching" for projects and code releases.

[–] mattyroses@lemmy.today 2 points 4 days ago

Yeah, exactly.

As someone who has been working on a large open source project for literally years, while trying to support a family, the hardest thing is time to devote to this project (which, absent capitalism, is what I'd spend my life doing).

AI can allow me to instead increase the speed at which I'm delivering the project I'd already architected, designed, and laid out with my other devs. I don't have the money to pay myself to work on it, much less other devs - and my bank doesn't take repo stars as mortgage payments unfortunately.

I hate the AI industry - but that's a problem with the economics, not the tool.

I'm happy to label that my project uses AI assistance, but bans just make me realize that wherever is banning it isn't more concerned with shipping a solution instead of a crusade against LLMs.

[–] horus_son_of_isis@lemmy.world 0 points 5 days ago

"distrust in capitalism and our pseudo-democratic plutocracies, the profit motive to replace the human workforce, the reckless criminal-incompetence of its implementation, and apparent stupidity of the average hairless primate"

I have hair, thank you very much, but seriously get out of my head. The hubris these days is unbelievable.

[–] Swedneck@discuss.tchncs.de 19 points 1 week ago (2 children)

the problem with "just a tool" is that using it will inherently change how you act.
Best concise way i can put it is that it's like how better hardware has largely just resulted in software not really caring about efficiency any longer.

[–] mattyroses@lemmy.today 1 points 4 days ago

Sure, but should we then ban any open source that doesn't run in 10MB or less of memory?

[–] horus_son_of_isis@lemmy.world -1 points 5 days ago

It is just a tool, but human nature makes it a net negative. There are a lot of tools like that, and history shows that once the cat is out of the bag, humanity just has to live with the damage that tool causes. There's literally nothing that can be done to stop it on a large scale, but small communities can always dictate what they will tolerate.

load more comments (1 replies)
[–] p03locke@lemmy.dbzer0.com 23 points 1 week ago (13 children)

I'm fine with AI. I'm not fine with slop. Ban slop, not LLMs.

We are not the same!

[–] horus_son_of_isis@lemmy.world 1 points 5 days ago

A perfect example of a tool used responsibly vs a tool in the hands of an idiot. There's nothing that can be done to make idiots stop idioting.

load more comments (12 replies)
[–] otter@lemmy.ca 93 points 1 week ago (2 children)

This was a problem in !selfhosted@lemmy.world and they've done a good job of dealing with it. You could take a look at that past discussion to see what worked / what didn't.

IMO there is an organized effort behind some of these new accounts pushing AI projects, and you need to deal with it in some form to stop them from coming

[–] urushitan@kakera.kintsugi.moe 52 points 1 week ago (1 children)

Agreed. TLDR, you must tag posts there with the following:

Post Tagging

There are three types of tags for project promotional / AI posts.

  • [CBH] - Code By Human - A project promotional post with a project that did not use AI in any capacity. No disclosure necessary.
  • [AIP] - AI Project - A project promotional post with a project that used AI in development in any capacity. Disclosure is required for how it was used.
  • [AIT] - AI Topic - A discussion topic that includes AI. This may be for a discussion on hardware to self-host on, llama.cpp vs ollama, your experience using vulkan, etc.
[–] CrypticCoffee@lemmy.ml 24 points 1 week ago (3 children)

Thanks for sharing this. Maybe correct tagging could be useful. Makes it easier to ignore but not overly heavy and possibly toxic.

load more comments (3 replies)
load more comments (1 replies)
[–] warmaster@lemmy.world 72 points 1 week ago (2 children)

Both the Linux Foundation and the EFF have permissive policies towards AI generated code, even Linus Torvalds accepts it as a tool.

Some FOSS projects that have AI generated code in it:

  • The Linux kernel
  • Fedora
  • Mesa 3D
  • Jellyfin
  • Firefox
  • Chromium
  • Homebrew
  • OpenSSL
  • FFmpeg
  • Curl

Should we ban them all? If so, this community would be either dead soon OR it would be hypocritical.

Or because they started pre-AI it's ok now? Shouldn't we care more about disclosure, policies, licensing, code quality and maintainability?

Users should downvote crappy software and crappy devs, regardless of the tool it was written with.

[–] eremophila@lemmy.zip 1 points 6 hours ago

even Linus Torvalds

He made his choice, that doesn't make him right, regardless of who he is, or who he thinks he is.

ai as it is now, owned by the people who own it, pushed by the people who push it, is the exact opposite of the linux philosophy for me. If I wanted microslop, I would still be using it.

[–] wiccan2@thelemmy.club 55 points 1 week ago (2 children)

Experienced developers using AI as a tool and properly understanding their code base are not slop.

AI slop is when someone with no software development experience prompts a piece of software into existence without any understanding of how that piece of software actually works. The project's are usually heavily pushed by their creators in the initial couple of weeks of creation but are then quickly abandoned when the creator finally realizes neither they nor their AI can maintain the project. Essentially these kinds of projects flood the internet with low quality abandonware.

A newly created open source project coded using AI would be fine if the creators could prove that they understand how to maintain the project and keep it going beyond the initially promoted code and that kind of proof can only come with time.

The big problem is the sheer volume of low quality projects that get abandoned will cause the projects that actually have potential to become needles in haystacks.

load more comments (2 replies)
[–] 87Six@lemmy.zip 52 points 1 week ago

Never in my life have I wanted to read about or use an AI slop project.

[–] MissingGhost@lemmy.ml 48 points 1 week ago

I am convinced that, with the right tools, it's possible to damage 40 years of work within a few weeks.

[–] halm@leminal.space 46 points 1 week ago (5 children)

I for one would really appreciate just one single FLOSS community that flat out banned any and all "AI" contributed code instead of following the approach of others. Somebody have the spine to stand out, plz.

I'm not a developer, but I wanna be able to keep up with open source news without having to navigate a slippery slop(e) into clanker dominated territory.

[–] eremophila@lemmy.zip 1 points 6 hours ago

Agreed, I really want to see this for linux distros and desktop environments, the list is far too small, and far too niche at present.

[–] wewbull@feddit.uk 20 points 1 week ago (1 children)

The Zig language has a no AI contributions policy. That's for the language itself, but a lot of it's community have similar views.

Codeberg has a no AI policy for projects hosted on its servers, so anything hosted there should meet your requirements.

load more comments (1 replies)
load more comments (3 replies)
[–] Enjoyer_of_Games@lemmy.ml 38 points 1 week ago* (last edited 1 week ago) (3 children)

I would support such a ban so long as there is some process to prevent it becoming a witch hunt.

I have personally already received one false accusation of using AI in this community and I wouldn't want to continue posting projects here if it becomes an atmosphere of suspicion.

load more comments (3 replies)
[–] Rudee@lemmy.ml 31 points 1 week ago (3 children)

I think one of the appealing traits of open source is that you can identify what piece of software and hardware does what (and how, if you're interested). You can post your exact method, and another person can follow along and replicate the result.

But if AI tells you how to build everything, you don't get the opportunity to learn, and your stack depends on what that particular model thought was best on that particular day. Maintenance also becomes harder if you just did a sudo apt install whatever Claude told me to without knowing what everything does and how it interacts

load more comments (3 replies)
[–] kazerniel@piefed.world 31 points 1 week ago (1 children)

Yes please. It's dispiriting to regularly go through the cycle of seeing an interesting project pop up here, oh wait it's vibe-coded crap, nevermind...

[–] verily@lemmy.dbzer0.com 18 points 1 week ago (2 children)

At a bare minimum, it would be nice for users to tag their projects accordingly. You could, with a glance, realize there wouldn't be a point in investing your time/energy into a project that the creator had less investment in, themselves.

load more comments (2 replies)
[–] AustralianSimon@lemmy.world 25 points 1 week ago* (last edited 1 week ago)

We allow it on our large subreddits on reddit. What we do is use a bot to filter repos that are less than 3 months old.

People who vibe code slop just want to share their thing and then abandon it. A limit like that or even 6 months will kill majority of this sort of low effort crap. Most of these people just let Claude or whatever sign the repo as well, another easy way to catch slop.

Developers that develop and only use AI as a tool build great products still as they review all their code.

A blanket ban is just going to make people be more sneaky.

[–] DieserTypMatthias@lemmy.ml 24 points 1 week ago

Vibe coded code whose "author" understands the language and actively challenges the agent for his decisions in the interest of long term window is OK. Vibe coded coded that are one-off without any future prospects should be 100% banned.

[–] HerbGrower@slrpnk.net 24 points 1 week ago (1 children)

Just ban low effort content, AI or human made slop both count and have no value.

load more comments (1 replies)
[–] Jolteon@lemmy.zip 22 points 1 week ago

I'm in favor just requiring AI-generated code to be tagged in some obvious place in the post. If there's a full restriction on it, I think quite a few people would just try to hide the fact that it was vibe-coded and post anyway,

[–] asudox@lemmy.asudox.dev 21 points 1 week ago

Yes. They are useless. Get rid of them.

[–] NuanceDemon@lemmy.dbzer0.com 20 points 1 week ago (1 children)

Most important step is to decide exactly where you want to draw the line.

load more comments (1 replies)
[–] beyond@linkage.ds8.zone 17 points 1 week ago

For me the most important thing is that something is free software. I've seen people advertise proprietary stuff in this community and have reported it, and nothing has been done. I don't know if that means my reports don't federate properly or if it's tacitly approved by the moderators. I know in the degoogle community there are "trusted' proprietary apps that are often recommended but this should not be the case in a free software or open source community. In any case, any rule that bans "AI slop" while allowing proprietary products is in my mind backwards.

Regarding "AI slop" I am generally in agreement with Codeberg's policy which states,

You must not share projects that mostly consist of code written by "generative AI"-tools (including services such as Claude, OpenAI Codex).

I suppose "mostly" is up to interpretation but for me this specifically targets vibecoded apps where there is no or very minimal human involvement. This may be heterodoxy but I actually don't think "an otherwise human-written codebase with a single line of LLM code" is the same thing as an entirely LLM generated codebase. I think there's room for nuance especially if the usage is disclosed (I don't think punishing transparency should be encouraged).

[–] iForgotSpells@sopuli.xyz 17 points 1 week ago (1 children)

Yes, please ban them. If not, soon this space will get overrun with those losers. This is what happened to r/fossdroid and r/opensource. 90% of posts there are from sloppers. It got really bad to the point regulars stopped participating, and now these subreddits are mostly just sloppers congratulating each others. Every post reads the exact fucking same, every project looks fucking similar, even comments. These people barely put effort anywhere.

This is a community for people to share and communicate, else we can all just talk to LLMs. Please don't let that happen to this community.

At the very least, make posters require to have an AI tag on their posts and a separate day for them to showcase their "projects".

Please don't reply saying but Linux uses LLMs, or other whataboutisms. There is a significant difference between code quality from people submitting to Linux and a slopper who vibecoded a project thinking they're helping.

load more comments (1 replies)
[–] carotte@lemmy.blahaj.zone 17 points 1 week ago

yes to a ban, these projects are worthless to most but their authors. and good for them, but they can keep their trash for themselves.

like 95% of new foss projects i see pop up are heavily ai-generated, and often in very unsubtle ways (line half the commits being "co-authored by" claude, that sort of thing)

it would be nice to have a community where we can share and discuss projects made by humans, so they don’t drown in the llm bile

[–] Fleur_@aussie.zone 16 points 1 week ago (3 children)

I think a blanket ban would make people try and hide the fact that something is ai. Like it or not ai isn't going away. I feel disclosure in either the title or body is the better choice. By all means ban those blatantly not adhering to the disclosure rule though.

Tags in Lemmy would be really helpful here as users could chose yo filter out all ai related posts from their feed, though a similar effect can come through requiring a keyword like "[AI]" to be in the title and a user end keyword filter.

load more comments (3 replies)
[–] njm1314@lemmy.world 15 points 1 week ago (1 children)

Maybe start out with strict labeling guidelines. If it's AI then it should be labeled as such. If a user posts something that's Ai and doesn't label it then ban that user. Maybe a warning first up to you.

But if the choice is between blanket everything allowed or blanket ban I lean more toward blanket ban.

[–] feral_sh@lemmy.today -3 points 2 days ago* (last edited 2 days ago)

I think disclosure is the most important piece. I don’t create anything without AI nowadays, but I’m:

  • planning architecture
  • addressing common exploits
  • running penetration tests
  • having automated code review pipes from different models
  • directly specifying details of how the code should work

I’m not so sure everyone is doing that. And if anyone has advice on how to improve, let me know!

load more comments
view more: next ›