We’ve been getting a lot of AI coded submissions recently, as well as lots of reports asking to remove them.
Should we remove these posts, or not?
I think requiring AI disclosure like how !selfhosted@lemmy.world does is a good approach. Not all projects rely as heavily on LLMs as others.
I think they should be allowed if they have actual effort and maintaining put into them, but that’s usually the problem. Most LLM projects get abandoned very fast.
This is a major difference with a project like Linux. Even if they start using slop code there, you know that they’re not going to suddenly abandon it.
Maybe we need to think out of the box, and instead of an LLM tag, we need a tag like how long the repo has existed which can be automatically checked by a bot.
Remove, and suggest they go start an AI software community. We can’t be monsters to people who might not know better.
Definitely need to remove them.
Rule 1 says Posts must be relevant to the open source ideology
I don’t think any ai projects can claim to be that when their copyright status is debatable and the tooling is worse with how closed their training is.
People against LLM parrot the same arguments again and again that it has simply lost its original meaning.
copyright status is debatable
debatable by who? who is going to settle this debate?, the courts who serve corporate greed?, Legislation made by politicians lobbied by SaaS companies? Anthropic? OpenAi? Microsoft?
The “Copyright is debatable/ its just a plagiarism machine” stance is not the Leftist/ pro FOSS gotcha argument you think it is. The point of the FOSS movement was to have total freedom over software, and that freedom includes the ability to study, learn and use it in ways it was not intended for. To stand as the antitheses of that is make Steve Balmer happy
-
All currently existing LLMs are unethically trained on copyrighted code that is incompatible with GPL licensed projects. LLMs have a 3 to 10% chance to unknowingly reproduce the copyrighted code perfectly, introducing legal plagiarism into an open-source project, which could easily open up the developers to being sued in the future if companies scanned open source repos for copyright violations.
-
Many courts are ruling that LLM generated code cannot be copyrighted at all, meaning that it also cannot be legally made GPL, losing the protections from corporate exploration the GPL normally grants. https://fsfe.org/news/2026/news-20260825-01.html
-
Since when has development tooling mattered for something to be FOSS? If it relies on propietary software to build or run it then there’s an argument it’s not truly free.
But if we’re saying that anything developed using closed source tools is not allowed then we’ll have to throw out anything that was developed on a mac or Windows PC.
You are just adding your oss preferences to open source here. I too have preferences, like no corp oss, no ads, no logins, no telemetry and so on, but i have to accept oss as oss more broadly.
I would recommend that you set your agent to filter out posts you don’t want, but you would likely rather censor this sub than automate it with an agent…
You are just adding your oss preferences to open source here.
OSS == Open-Source Software, what are you talking about
I would recommend that you set your agent to filter out posts you don’t want
Just to be clear, do you mean that the user’s user agent (lemmy client) should be capable of filtering out posts about vibecoded slop, perhaps by having lemmy communities require such posts to be tagged? Or do you mean that a LLM should curate what users see here?
Posts must be relevant to the open source ideology
Did you not read the full rule?
How can something that is inherently closed sourced be in line with that rule?
I’ll tug on that thread… so can we not use Windows or macOS to develop OSS code on? It has to be on a Linux machine? What if the BIOS is closed source or it’s using binary blobs for the video drivers?
Require an AI tag for anything written in part or in whole by AI.
I advocate for a disclosure, blanket removal feels like censorship; even vibe coded slop is a project that might generate interest if it was made to solve some problem or showcase a new frontier, nature of OSS will push the slop out of the project eventually.
When I say “slop”, I refer to a huge codebase that does what it advertise but has no documentation on what it does internally and the primary poster cannot adequately explain what it does(code mudball esentially). but if its well documented and looks like it was put together with care, with rhyme and reason than I will defend against calling it slop
Minimum age requirement and activity requirement. If it was built all in one go it’s more likely to be abandoned and full of problems and just pollute the landscape. If it’s been under development with multiple commits over a time-span of months or a year or more it’s more likely to be higher quality, have human in the loop somewhere, continue development, patches, etc. Linux itself for example would be exempted because it has a significant age, significant recurring activity in development, multiple human developers, etc.
I do think exceptions on a case by case basis for clever simple programs that address a not previously addressed need might be fine as well. I really think there needs to be a little discretion for mod action.
What a lot of people hate and I do as well are these “look daddy I can ‘code’ too” baby’s first/second/etc vibecoded programs that people proudly toss out there without any real thought beyond pride they told an LLM to make something and it did it. Those rarely add much value, often are redundant with one another (why reinvent the wheel again and again?), and would tend to be lower quality and end up just being so much spam that makes it harder to understand what’s worthwhile.
I completely agree. It can be reworded as developer or software reputation
I think a disclosure at least in the title of the post should be required. But only if the software is known to be not slop at all. The problem with this approach is, that everyone has their own threshold and definition of what slop means, or are misinformed about the project. Overall I do not think it’s a good idea to ban any Ai contributed or assisted project.
As an example, do you consider Linux to be Ai slop project?
I’m referring to these new projects coded by AI from scratch, not existing projects which have an occasional LLM contribution.
People are submitting a lot of these AI projects recently.
What about project that were developed normally, but later changed to a complete vibe coded slop model? Because if this is allowed, then this would be a loophole basically. Just start a project without Ai, then do all the stuff with it.
If it’s not open source, remove them.
If they’re open source then the people posting them are in the right place.
A policy like what’s being suggested in the op will only be walked back in a few months.
E: also disclosure is a stupid requirement. All it does is give people something to fight over and there’s no industry accepted process for evaluating ai code as opposed to human written code, so disclosure doesnt even serve a useful purpose. It’s literally just giving people something to argue about when the hypothetical post is ostensibly about the software or what it accomplishes.
Disclosure. If LLMs are used in service of open-source projects, then they are relevant, but clearly many in the community feel that to be negative, and therefore there should be a disclosure. Someone can make open source software using closed-source tooling already, so disallowing one form of tooling entirely is letting a moral reaction interfere with how we understand open source.
Linux would have to be removed from discussion, for example, if all LLM-contributed projects were to be disallowed. I don’t see why rules should be made with explicit exceptions in mind.
I’m mostly referring to these new projects that are AI coded from scratch, not existing projects that might have some LLM contributions.
In my view, starting code from scratch or augmenting existing code with LLMs are equivalent in terms of whether or not they should be eligible for discussion. Both should have a disclosure, and both are worthy of discussing where relevant. If someone uses a bot to advertise a million LLM-started projects or something and overwhelm the community, then this is bad and should be stopped, I suppose.
Remove them!
Not calling it slop might help get less biased answers.
Remove!
I’d like to keep them, but properly identified as such. As much as I don’t prefer it, without it there would be projects that wouldn’t be attempted.
They are also used by proper developers that know what they do and they just need specific parts done, which they’ll review anyway.
So… Keep them. Identified, but keep them.







