About enshitification, open source and AI pollution

all 27 comments

sorted by: hot top controversial new old
[–] 93 points 6 months ago* (2 children)

Anyone else suspect commercial game engine are doing this to attack their FOSS (free open source software) competitor?

Unlike other engines Godot asks nothing of its users. No money, no tie in to their sales platform. It's literally just good free software anyone is invited to try.

Sad to see it dealing with this. FOSS may be under a kind of intentional AI attack.

  • source
  • hideshow 2 child comments
  • [–] 47 points 6 months ago

    yes, exactly my thoughts. what if the AI-slop pull request onslaught is a way of the feudalists to weaken the FOSS community and on the long run make themselves irreplaceable? seems to be happening to a lot of maintainers

  • source
  • parent
  • [–] 47 points 6 months ago (4 children)

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

  • source
  • hideshow 4 child comments
  • [–] 4 points 6 months ago

    There are cheaper services that use Chinese models like Deepseek, but even then I doubt they will become mainstream when the bubble bursts and if the US decides no one will use LLMs anymore because they're not selling subscriptions for them. I guess only people savvy enough to run local LLMs or get services from elsewhere would keep using them, hopefully with more caution (yeah this is cope)

  • source
  • parent
  • [–] 16 points 6 months ago (8 children)

    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.

  • source
  • hideshow 8 child comments
  • [–] 1 point 6 months ago (3 children)

    Use ai to make code to detect and block AI. Actually though wish we could force an AI tag tat could just be blocked with UBO

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 6 months ago (2 children)

    But what polices that? And what's to stop humans pasting in the AI code, which may look like human code, just behave poorly or contain hallucinations.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -2 points 6 months ago (1 child)

    Write tests and actually do the practice of testing every single line with no regression testing. That will solve the AI problem. Since if it does work, there is no problem. If doest work just remove it. If it does work, who cares if it's AI or not?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 6 months ago* (2 children)

    Humans in the loop? Code would have to be read and understood by the human, in relation to the problem being resolved, and the rest of the code base it may or may not interact with... And that's difficult.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -2 points 6 months ago (1 child)

    If ai slip vibe code is so shitty, then it should be pretty easy for humans to detect it and shut down without wasting too much time right?

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

    No, it's shitty because it's complicated, looks correct, but actually filled with errors and hallucinations. Including libraries that may not exist, and that leaves code open to injection attacks (where people make fake libraries/dependies based on commonly hallucinated code, then package them with genuine FOSS software which is now playing cover for malware/viruses).

  • source
  • parent
  • [–] 10 points 6 months 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.

  • source
  • [–] 6 points 6 months ago (5 children)

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

  • source
  • hideshow 5 child comments
  • [–] 10 points 6 months ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 6 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 6 months 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...

  • source
  • parent
  • [–] 5 points 6 months 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

  • source
  • parent
  • [–] 1 point 6 months ago (2 children)

    Can they require that all code submissions have a natural language summary of it included?

  • source
  • hideshow 2 child comments