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?

top 82 comments

sorted by: hot top controversial new old
[–] 37 points 3 weeks ago

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.

  • source
  • [–] 20 points 3 weeks ago* (last edited 3 weeks ago)

    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

  • source
  • [–] 99 points 3 weeks ago (3 children)

    AI slop & AI code is very different. If its just pure vibe coded slop with no oversight or effort, then sure its just junk, remove it.

    But a lot of experienced developers now use AI tooling to increase productivity, just because AI was used in the process should be consider it slop?

  • source
  • hideshow 3 child comments
  • [–] 29 points 3 weeks ago* (last edited 3 weeks ago)

    Agreed. Needs to be disclosed in the title of the post as having AI involvement, and show signs of active maintenance. Anyone can now oneshot some slop that's nothing but a waste of our time, but it takes good developers to maintain, secure and expand.

    5 days old, nope, hasn't been touched in months, nope. Dozens of active human participants, and/or a reasonable history of active development and to a lesser degree stars or equivalent, sure.

    It's a bit more work for a poster, but I think it can keep quality high for project posts. Should be voted on by the community and made a rule.

  • source
  • parent
  • [–] 9 points 3 weeks ago

    The self-hosted community has a very good take in my opinion. Especially facing the fact that new slop vaporware often comes with new accounts that just advertise the "product".

    Disclosure about AI use, account minimums, and mods having discretion to ban obvious junk spam.

  • source
  • parent
  • [–] 13 points 3 weeks ago (2 children)

    Depends on the definition. If we go by the definition a lot of users here seem to have, Linux itself would no longer be considered a FOSS project, which imo is completely ridiculous.

    If we're talking about literally vibe coded from the ground up projects where the devs don't even know what the code inside looks like, yes maybe it should be removed or given a post tag once we have the feature.

    Personally I prefer to keep a discussion going even with heavy AI coded projects, we're living in interesting times and I am convinced to keep an open mind about what engineering will look like going forward and what doors it might open for the FOSS community despite its flaws and negatives.

  • source
  • hideshow 2 child comments
  • [–] 5 points 3 weeks ago

    As others have said in other posts, the cat's out of the bag. No matter if/when/how bad the AI crash is, if computing is still viable after then there will be AI.

    I think eventually it will emerge that the highest quality AI code will be produced by already experienced developers, who can identify when it's produced slop and fix it, and that will be the case no matter how good the models get.

    I of think of it somewhat like managing a team of interns. You give them instructions and they give you code. You still have to know enough to identify if that code meets the requirements and is of good quality.

  • source
  • parent
  • [–] 2 points 2 weeks ago*

    There is no definition of "AI". It's all bullshit. It doesn't exist.

    The supposed difference between these two unstated definitions is a difference of scale not of kind. There is no objective dividing line for moderation.

  • source
  • parent
  • [–] 12 points 3 weeks ago (1 child)

    I'm gonna agree with others that there need to be standards not a blanket ban. I'd leave it up to the admins/mods what those are. Because getting too granular with it wold be hard to enforce. You guys pick something you feel is reasonable and will cut down on 0 effort slop but also allows you to enforce things without digging through the minutia of every post.

  • source
  • hideshow 1 child comment
  • [–] 23 points 3 weeks ago
    [–] 22 points 3 weeks ago
    [–] 22 points 3 weeks ago (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 13 points 3 weeks ago (2 children)

    As an example, do you consider Linux to be Ai slop project?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 15 points 3 weeks ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 3 weeks ago

    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.

  • source
  • parent
  • [–] 11 points 3 weeks ago

    I vote to remove myself but I'd be fine with just having to state AI involvement

  • source
  • [–] 21 points 3 weeks ago

    Remove them

  • source
  • [–] 10 points 2 weeks ago (1 child)

    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.

  • source
  • hideshow 1 child comment
  • [–] 18 points 3 weeks ago

    Remove them

  • source
  • Require an AI tag for anything written in part or in whole by AI.

  • source
  • [–] 8 points 3 weeks ago

    Very hard question. I think, idk. For me Open Source isn't AI so i think remove it because it makes /c/opensource less attractive and worse but some things like about Craft i think it can be but i'am not moderator so i think ban it completely or most of it.

  • source
  • [–] 59 points 3 weeks ago (8 children)

    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.

  • source
  • hideshow 8 child comments
  • [–] 7 points 3 weeks ago

    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.

  • source
  • parent
  • [–] 4 points 3 weeks ago (1 child)

    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

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 2 weeks ago* (last edited 2 weeks ago)
    1. 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.

    2. Some European courts have ruled 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

  • source
  • parent
  • [–] -2 points 3 weeks ago (4 children)

    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..

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 3 weeks ago

    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?

  • source
  • parent
  • [–] 6 points 3 weeks ago (1 child)

    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?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 3 weeks ago*

    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?

  • source
  • parent
  • [–] 15 points 3 weeks ago

    Just make people disclose it in the title

  • source
  • [–] 14 points 3 weeks ago

    I'm assuming the majority of posts are slop now, there are a couple of dedicated opensourceai subreddits, I would prefer such a thing existed here as well, with a blanket ban in this one.

  • source
  • [–] 38 points 3 weeks ago

    Definitely need to remove them.

  • source
  • [–] 16 points 3 weeks ago

    Require a tag but if someone wants to share something that solved a problem for them as an open source project they should be able to.

  • source
  • [–] 22 points 3 weeks ago

    Remove, and suggest they go start an AI software community. We can't be monsters to people who might not know better.

  • source
  • [–] 10 points 3 weeks ago (1 child)

    I would say to just require them to be tagged, but the volume of them seems quite high. Might be better to just ban them and they can create a separate community.

  • source
  • hideshow 1 child comment
  • I vote remove

  • source
  • [–] 13 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

    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, yet excluding Linux cuts out a huge portion of open source discussion.

  • source
  • hideshow 2 child comments
  • [–] [S] 7 points 3 weeks ago (1 child)

    I'm mostly referring to these new projects that are AI coded from scratch, not existing projects that might have some LLM contributions.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 3 weeks ago

    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.

  • source
  • parent
  • [–] 9 points 3 weeks ago

    We had Slop before AI. we just called "shit".

    If a coder wants to shit out a project that never works and never patches it? I want them to notice the culture and know better.

    If someone is learning, using the tools they have available, and shows a commitment to maintain their project? I want to see their work. I wanna see them get help from the community to be more literate in their own project, and in the full toolset they're using.

    Most of these vibecoded submissions are the former. Thank you for removing the fecalware. If the community decides it needs to remove AI at all to keep this up? Eh, there's dbzer0.

  • source
  • [–] 9 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    +1 to remove them. 99% of those AI projects will go unmaintained and abandoned after a year, and their use of AI more often than not impedes socialist efforts due to directly or indirectly supporting fascists tech companies.

    1. Simply using an AI that's run on a corporate data centers encourages the construction of yet more data centers, with all of the environmental/climate negatives they bring, as well as local harms they induce on the people living near them, such as increased electricity rates.

    2. Using corporate AI directly helps the financial situations of those giant corporations (by boosting usage/user numbers, they are able to attract more investment capital), most of which are ran by right-wing CEOs who are more than willing to collaborate with and fund fascist governments to ensure that they are not regulated in search of both maximum profits. Some of these companies, such as Nvidia, Palantir and Oracle, genuinely appear to be seeking to use these tools for what would previously be considered crackpot conspiracy theory levels of public control and surveillance.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 weeks ago (1 child)

    AI is a direct result of mass-surveillance. I'll repost what I wrote to a previous user:

    Something you're not acknowledging is that this technology stems from surveillance-capitalism and the surveillance-state. Google et al were financed to solve the needs of the state. Google search for consumers was a by-product from the state's need and desire to make sense of their mass-surveillance programs.

    Surveillance-capitalism operates under complete deception. Pokemon Go players didn't know they were collecting data for autonomous-murder-drones.

    Solving Google's Captchas was unpaid labour: you were creating data for Google's OCR program and now you're creating data for autonomous cars or whatever their investors want you to toil on next.

    The original iteration of reCAPTCHA was criticized for using unpaid work to assist in transcribing efforts.[40]

    A 13-month study published in 2023, "Dazed & Confused: A Large-Scale Real-World User Study of reCAPTCHAv2," found that reCAPTCHA provides little security against bots and is primarily a tool to track user data, and has cost society an estimated 819 million hours of unpaid human labor.

    Out of all this theft, unpaid labour and intrusive surveillance what does the working class get? Housing costs are increasing. Food costs are increasing. Poverty is increasing. What is AI going to do for us? It's not building houses. It's not harvesting crops. It's not giving the working class any material benefit, but is further degrading living conditions. Enjoy the endless drone of a data-center! Enjoy breathing the fumes of gas-turbines! Enjoy talking to chatbots and never a human!

    AI is deployed as a barrier between the working class and businesses. AI is deployed to decrease labour costs. AI is deployed to kill. The fact you can create text, images, videos and audios that mimic reality only means more surveillance on the working class because digital-signals can be faked absolutely and are now suspect by default.

    You can't eat what AI creates--it is completely immaterial, but it is being used to commit genocide. I'm sure that warms the cockles of the hearts in all of us.

    I do not think AI use should be condoned.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 weeks ago*

    That seems to me to be just more justification for why we should use it. We contributed to creating it, indirectly, so we should benefit from it's creation. Admittedly simple usage isn't sufficient, and all companies that offer LLM services should be heavily taxed, with that revenue redistributed to the populace, but that's a different argument.

  • source
  • parent
  • [–] 4 points 3 weeks ago

    Maybe a slopscore bot comment on any post that links to a repo?

  • source
  • [–] 7 points 3 weeks ago

    I am going to go the other way and say the more, the merrier. I like to see new and interesting things that someone did to scratch an itch or solve a problem. I may not use it or agree with how they developed it or the license they chose, etc., but I still like seeing the posts about it.

  • source
  • [–] 7 points 2 weeks ago (1 child)

    There needs to be an actual framework for what you're excluding and why. The majority of developers use LLMs to some degree, an outright ban is unrealistic and motivated by emotion not logic.

    I'd suggest limiting submissions of brand new projects with no history and nothing to indicate they're going to be maintained going forward. There also needs to be some proof the maintainer actually understands how their own project works but that's far more difficult to prove.

    If you've been working on a project for 6 months and plan to continue doing so then I'm happy to learn about it regardless of whether AI was used in the process or not.

  • source
  • hideshow 1 child comment
  • [–] 3 points 2 weeks ago

    I guess it depends on what we mean by "using an LLM". I'm definitely more conservative than most but for me I draw the line at permitting an LLM to author code; while not ideal I can accept using it has a fuzzer and static analysis tool.

    The community will have to agree to what its pain tolerance is and enforce that position.

  • source
  • parent
  • [–] 10 points 3 weeks ago

    Remove them. If you can't ensure you own all the code written you can't make it open source. It's not yours to license.

    I hope it's not allowed here

  • source
  • [–] 6 points 2 weeks ago

    All these "remove" votes will only accomplish developers not disclosing their use of AI 🙄 It's very silly.

  • source
  • [–] 3 points 2 weeks ago

    No, I think that there should not be a anti-AI rule. People can downvote those post if they are anti AI.

  • source
  • [–] 7 points 2 weeks ago*

    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.

  • source
  • [–] 10 points 3 weeks ago

    Remove them!

  • source
  • [–] 7 points 3 weeks ago

    Remove. Perhaps there's another community interested in AI hobby projects, but most of these seem like listening to someone's dreams, and are not very interesting.

  • source
  • [–] 10 points 3 weeks ago

    Remove them. There could be another community for slop.

  • source
  • [–] 8 points 3 weeks ago (1 child)

    Not calling it slop might help get less biased answers.

  • source
  • hideshow 1 child comment
  • [–] 2 points 3 weeks ago

    Depends on how much effort is put into them and how useful they are

  • source
  • [–] 2 points 2 weeks ago*

    Idk if zero tolerance is the way to go, but conceptually at least allowing things with "significant" AI usage is kind of horrifying to me. The entire rest of the fucking world is completely uncritically embracing it so i see no reason why places like these have to allow it as well, i think it should be obvious that we want some communities that reject AI usage so we have control groups and safe havens for the future..

  • source
  • [–] 4 points 2 weeks ago
    [–] 4 points 3 weeks ago

    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.

  • source
  • [–] 6 points 3 weeks ago

    Remove them, let them create their own "AISoftware" community.

  • source
  • [–] 3 points 3 weeks ago

    From my perspective "slopcode/vibecode" means entirely (or mostly) generated, which is different than a human-maintained project that includes bits of generated code. As a rule I'm very skeptical of the former and give the benefit of the doubt to the latter especially if it's an established project.

    I'd be fine with removal or mandatory disclosure, but the latter would probably be easier to implement if there was a way to filter them out.

  • source
  • [–] 2 points 2 weeks ago

    It’s really telling how AI-assisted software development is simply divided into black and white, as if there were no in-between. Apparently, although there is.

  • source
  • [–] 1 point 2 weeks ago* (last edited 2 weeks ago)
    • I think AI disclosure has to be a hard rule. Not done properly? Remove.
    • I think there has to be a threshold of when to allow, otherwise we'll get (and are already) overwhelmed. For example, be X months old is an easy check that would filter out low-effort posting.

    Besides these basic rules that I think are absolutely mandatory, I'm not sure how far to go. I'd want to say that the project needs to explain Free Software affinity or explain why it's posted on lemmy or something like that... But it's so easy to fake it with, the irony of it, AI texts.

    In conclusion,

    • Decision-wise, I wouldn't mind if the resolution is the full removal on AI-driven projects.
    • Decision-wise, I would absolutely request a hard-ban if the lemmy text is AI-written.
    • Decision-wise, I could accept if the rule is to accept some small sliver of AI posts that would come our way otherwise. Maybe some projects where AI assists in writing code, but does not replace the programmer. Maybe that is OK, if the project otherwise is "relevant to the open source ideology" (Rule 1 of this community).

    EDIT: Also, something to think about is... community, not just code. For community health, it might be better to remove AI-driven projects entirely. Because we aren't just about code. We're also about continuing to exist long-term.

    EDIT 2: I think codeberg actually did it better than my improvised thinking. I'd go with codeberg's rules: https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html

  • source
  • [–] 0 points 3 weeks ago (4 children)

    Removed. AI is fundamentally anti open-source.

  • source
  • hideshow 4 child comments
  • [–] 3 points 3 weeks ago (3 children)

    Tell that to all the proprietary software that got OpenSourced

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 3 weeks ago* (2 children)

    Oh you mean the broken "replacement" for Photoshop?

    The one that wasn't needed since we have GIMP and Krita?

    Yeah that was fucking worth annihilating whatever teeth the GPL and associated copy-left licenses had left.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 weeks ago

    I don't think restricting what people can post is a good idea if you are looking to grow a community

  • source
  • [–] 1 point 3 weeks ago

    I think it should allow AI coded projects.

    AI code is a QA problem.

    I've seen an opensource project (amule) being revived with AI, but there's extensive testing before the PRs are merged and the project seems to be working pretty fine.

    Btw, I use AI a lot to configure my emacs init.el file :-D

  • source
  • [–] 1 point 3 weeks ago (1 child)

    Keep them but perhaps ask for #ai tags in titel, so those not wanting them can scroll past them.

    All these new apps/software announcements will just get better and better, and if they are open source, they clearly fall in under this sub. At some point most users will have their own agents that can add or improve these new projects as they see fit, so let si oss be shown here as normal.

    There are already super cool vibe coded open source software, and let's be honest, not all hooman software is great, so why not ban shitty hooman software/coders while we are at it? Oc not - oss is oss no matter how its made, even if the description sounds like an ai, or it's not always maintained.

    In the near future, pure hooman coded open source will become more and more rare, so those interested in non-ai open source should start new sub's for their special wants instead of posing restrictions on what is becoming the new normal.

  • source
  • hideshow 1 child comment
  • [–] 1 point 3 weeks ago*

    The question is how opensource is AI model which has been used for these creations? Are datasets available somewhere?

  • source
  • [–] 1 point 3 weeks ago

    I've recently been pondering the future impact of AI on coding, while trying to filter out the current noise surrounding the issue (since all it does is muddy the waters). There's a lot of amateurish supposition to follow, but since you appear to be getting fewer thought out responses than "AI-bad-kill", take it with a pinch of salt.

    There was a recent article on the open source software that props up the internet - (paraphrasing here) one of these repositories had (pre-AI) a user called Jin Yue or Jin Yin who made hundreds of useful pull requests, gained the trust of the repo maintainer and was eventually given admin privileges, only to surrepticiously merge malicious code when no one was looking (eventually discovered ~a month after the fact). I imagine that (likely) state-sponsored attempts like these will make more use of AI in the future for quicker turnaround, and that maintainers will also eventually use AI to quickly audit submitted code for security flaws.

    As far as open source software channels are concerned, I imagine there will be a decent amount of low effort malicious software that makes heavy use of AI, submitted to these channels. In such an environment, whether or not users are permitted to candidly disclose AI usage without reprisal will likely make a huge difference, since honest disclosure would invite security-minded people to audit fault-prone AI-assisted code - something that malware distributers will try to avoid at all costs (thereby allowing a distinction that can be leveraged to form between the two).

    Just my two cents.

  • source
  • [–] -2 points 3 weeks ago

    I would say if the post itself is entirely AI generated I'm not interested. If it's a human post talking about a project created with AI I don't mind so much.

  • source
  • [–] -4 points 2 weeks ago* (last edited 2 weeks ago)

    There's no such thing as "AI". Nothing to disclose.

    Even if there were something to disclose, people don't know how much of their dependencies were computer generated. It's a purity test.

    But all apps should be vetted for malware, etc.

  • source