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.

  • Otter ( otter@lemmy.ca ) 
    72·
    2 months ago

    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 漆たん ( urushitan@kakera.kintsugi.moe ) 
      44·
      2 months ago

      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.
        • wiki_me ( wiki_me@lemmy.ml ) English
          3·
          2 months ago

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

          If i am just posting these projects i found which i think are interesting (which i did a lot of). i am now suppose to spend more of my spare time researching if they include AI? I am pretty sure i won’t be able to know most of the time .

          There are not a a lot of projects i think people will be interested enough to do a “high effort evaluation”. if anyone is that interested he can just ask, or check out the code which should be fairly rare.

          AI has been here for a while. If it would have caused FOSS communities to be flooded by AI it probably would have happened by now. We should try and avoid the bias of risk aversion.

          Looking at AI . it reminds me of how for wayland there was constant criticism even if it was just plain wrong and just made people overly scared . the plain wrong stuff was highly upvoted and i didn’t always have time to correct it, plus people being disrespectful discouraged me from discussing it because i didn’t feel it will be productive . now wayland is pretty much accepted as “good” by most of the FOSS social media communities in my experience. when a new technology appears. it takes time and effort to study it deeply and it’s advantages and disadvantages . And i suspect people in social media are often not the first to do that honestly.

          • curbstickle ( curbstickle@anarchist.nexus ) English
            3·
            2 months ago

            On /c/selfhosted, you share someone else’s project without the disclosure. Age of account requirement is still there, though, has to be at least 30 days old.

            If youre aware of some level of ai involvement when posting, its encouraged to mention. If they have an ai disclosure in their repo and you link it, even better.

            But since its impossible for a 3rd party to know development details, disclosure doesn’t apply. Assuming something similar is done here, that wouldn’t be a concern.

    • curbstickle ( curbstickle@anarchist.nexus ) English
      8·
      2 months ago

      @CrypticCoffee@lemmy.ml if you have any questions on those rules, please let me know.

      The disclosure was needed because there is a wide variety of LLM use, which you can see in the explanation post as well. There is a rather wide difference between “I used an LLM to summarize my changes in the readme” and “I generated everything here from a single prompt”.

      The disclosure addresses that part, while the tags allow people to choose what to interact with or what to filter.

  • Handles ( halm@leminal.space ) English
    38·
    2 months ago

    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.

  • Enjoyer_of_Games ( Enjoyer_of_Games@lemmy.ml ) 
    32·
    2 months ago

    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.

    • verily ( verily@lemmy.dbzer0.com ) 
      13·
      2 months ago

      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.

      • kazerniel ( kazerniel@piefed.world ) English
        3·
        2 months ago

        yeah, I’ve since seen the suggestion for enforced tagging in the top comment, and I agree that it could be a good solution for allowing users to decide for themselves if they want to engage

  • Rudee ( Rudee@lemmy.ml ) 
    21·
    2 months ago

    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

    • Eq0 ( Eq0@literature.cafe ) 
      16·
      2 months ago

      U also like that for small private projects you can literally contact the developer for questions/suggestions/comments. There is no point if all they did was ask Claude

  • iForgotSpells ( iForgotSpells@sopuli.xyz ) 
    21·
    2 months ago

    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.

    • wiki_me ( wiki_me@lemmy.ml ) English
      3·
      2 months ago

      This is what happened to r/fossdroid and r/opensource

      I have to admit i don’t think there is a significant drop in quality in r/opensource . and honestly reddit is declining in quality as it gets more popular IMO so i am not sure correlation implies causation even if it exists.

      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.

      Problem is “AI slop” basically means “bad AI code” which is subjective. i am sure the guy from xlibre thinks xorg is terrible .

  • Matt ( DieserTypMatthias@lemmy.ml ) 
    16·
    2 months 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.

  • Chloé 🥕 ( carotte@lemmy.blahaj.zone ) 
    16·
    2 months 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

  • Jolteon ( Jolteon@lemmy.zip ) 
    16·
    2 months 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,

    • Eq0 ( Eq0@literature.cafe ) 
      11·
      2 months ago

      Agreed ! I think a complete AI ban on every element of the project is too strict. But I also have no interest in a massive AI repository with no supervision (and who can supervise a huge AI commit ?)