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.

  • WhatAmLemmy@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    edit-2
    11 hours ago

    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.

    • Swedneck@discuss.tchncs.de
      link
      fedilink
      arrow-up
      6
      ·
      5 hours ago

      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.