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?

  • geneva_convenience@lemmy.mlBanned
    link
    fedilink
    arrow-up
    10
    ·
    2 days ago

    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.

  • TrollAccount69@lemmy.ml
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    2 days 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.

  • Majestic@lemmy.ml
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

    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.

  • BJW@lemmus.org
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    2 days ago

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

  • Rogue@feddit.uk
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    2 days ago

    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.

    • RumRunningDevil@lemmy.zip
      link
      fedilink
      arrow-up
      3
      ·
      2 days 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.

  • lightrain@forum.storstad.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days 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.

  • WardPearce@lemmy.nz
    link
    fedilink
    English
    arrow-up
    111
    arrow-down
    6
    ·
    3 days ago

    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?

    • MalReynolds@slrpnk.net
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      2
      ·
      edit-2
      3 days 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.

    • JustEnoughDucks@slrpnk.net
      link
      fedilink
      arrow-up
      8
      ·
      3 days 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.

  • HaraldvonBlauzahn@feddit.org
    link
    fedilink
    arrow-up
    52
    arrow-down
    1
    ·
    3 days ago

    How about making a rule that it is at least six months old and in continued development? This would filter out most slop.

    • lasagnaisland@lemmy.zip
      link
      fedilink
      arrow-up
      24
      arrow-down
      1
      ·
      3 days ago

      agreed. i think metrics like this are much more practical and useful:

      • age of project
      • number of stars (not great, but can help show overall interest)
      • number of versions/updates
      • activiely maintained

      if an amazing, maintained tool uses AI, that’s a lot different than a one-night project that’s never been tested and will be abandoned in a week

  • ProdigalFrog@slrpnk.net
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    edit-2
    2 days ago

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

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    72
    arrow-down
    11
    ·
    3 days ago

    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.

    • Not_mikey@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      14
      arrow-down
      5
      ·
      3 days 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.

    • Artemis_Mystique@lemmy.ml
      link
      fedilink
      arrow-up
      19
      arrow-down
      14
      ·
      3 days ago

      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

      • ProdigalFrog@slrpnk.net
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        2 days 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

    • Sims@lemmy.ml
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      16
      ·
      3 days ago

      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…

      • ISOmorph@feddit.org
        link
        fedilink
        arrow-up
        10
        arrow-down
        1
        ·
        3 days ago

        You’re missing the point he’s trying to make IMO. He’s questioning if software can be categorized as open source, if it is coded by closed source LLMs, that in turn only aquired their database by stealing someone elses intellectual property. It’s a valid question. OSS is more than just “I can see and fork the code”.

        • sudoer777@lemmy.ml
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          6
          ·
          3 days ago

          But humans do basically the same thing and their brains aren’t open source either

          • ISOmorph@feddit.org
            link
            fedilink
            arrow-up
            2
            arrow-down
            1
            ·
            3 days ago

            I truly meant it as a debatable question. If LLMs didn’t have massive proven negative ecological and societal impacts, I’m not sure which way I would lean. Since they do, I have a clear personal opinion. But it’s just that. My opinion.

            • sudoer777@lemmy.ml
              link
              fedilink
              English
              arrow-up
              3
              ·
              3 days ago

              Humans also have massive negative ecological and societal impacts depending on the person/society. I don’t see how whether a human or LLM writes code changes how open source it is.

      • lagoon8622@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        2
        ·
        3 days ago

        You are just adding your oss preferences to open source here.

        OSS == Open-Source Software, what are you talking about

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        3
        ·
        3 days ago

        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?

        • notfromhere@lemmy.ml
          link
          fedilink
          arrow-up
          8
          arrow-down
          2
          ·
          3 days 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?

      • ferric_carcinization@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 days 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?

  • motruck@lemmy.zip
    link
    fedilink
    arrow-up
    23
    arrow-down
    2
    ·
    3 days 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.