About enshitification, open source and AI pollution

  • pr06lefs@lemmy.ml
    link
    fedilink
    arrow-up
    43
    ·
    5 days ago

    if the bubble ever collapses maybe AI use will cost too much to harass FOSS projects with it.

    • circuitfarmer@lemmy.sdf.org
      link
      fedilink
      arrow-up
      32
      ·
      5 days ago

      This. AI is not and will not be profitable. It’s afloat because of an investor circlejerk. Once they get off then it’s over. A waiting game.

    • Cethin@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 days ago

      It won’t sadly. I can run many on my computer. They’ll still be available, even if every server-based one goes down.

  • nullroot@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    4 days ago

    I’m thinking we are going to have to come up with a way to vet contributors before allowing them to contribute code. This will likely reduce the overall contributions of people given we’re creating a barrier to entry, but so many of these FOSS projects are just straight getting overwhelmed with this shit. Something needs to change.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    13
    ·
    5 days ago

    Really awful website with more ads and shit than content.

    Nevertheless worrysome and indeed food for tough. Ai is here to stay, so we all need to find ways to deal with it, that we like it or not.

    Maybe specialized humans in detect ai slop? Because using ai to detect ai seems kind of hironic.

  • Vex_Detrause@lemmy.ca
    link
    fedilink
    arrow-up
    6
    ·
    4 days ago

    Can anyone describe the process of code contribution with open-source. It’s it like anyone hands in a code.

    • jeinzi@discuss.tchncs.de
      link
      fedilink
      arrow-up
      10
      ·
      4 days ago

      You make a copy of the code (“fork”) for yourself, make edits, then request that your changes be accepted into the original project (“pull/merge request”). Someone from the project has to check the edits, make that decision and hit accept or decline.

      • OwOarchist@pawb.social
        link
        fedilink
        English
        arrow-up
        11
        ·
        4 days ago

        Ideally, you’d also first talk to the developers in charge of the project to see if your changes would be wanted in the first place.

        (Or you’d start by reviewing existing bug reports and feature requests and addressing one of those.)

        What I mean is, it’s generally better to not just throw code at them and hope they’ll like it. If you check first to see if they want it, you can save yourself from wasting effort on writing code that they’ll decline.

        • Venat0r@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          4 days ago

          I assume when people do that it’s because they’re going to be making the fork regardless, and they think they’re being helpful by submitting a pull request with thier AI slop… But really they should just keep it on thier own fork if they don’t understand the changes but want to use it regardless…

    • chrash0@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      4 days ago

      generally yeah. the problem is that the barrier to entry used to be higher so fewer people knew how to write code to integrate with the project before coding agents. now anyone who can install Claude Code has a seat at that table