222

Open-source game engine Godot is drowning in 'AI slop' code contributions: 'I don't know how long we can keep it up' (www.pcgamer.com)

submitted 3 months ago by pylapp@programming.dev to c/opensource@lemmy.ml

15 comments fedilink hide all child comments

About enshitification, open source and AI pollution

top 15 comments

sorted by: hot top controversial new old

[-] pr06lefs@lemmy.ml 44 points 3 months ago

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

[-] circuitfarmer@lemmy.sdf.org 33 points 3 months 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 2 points 3 months 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.

[-] webp@mander.xyz 3 points 3 months ago

But will there still be big tech saboteurs?

[-] Shimitar@downonthestreet.eu 13 points 3 months 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.

[-] SlimePirate@lemmy.dbzer0.com 5 points 3 months ago

There is the new vouch system too

[-] ttyybb@lemmy.world 1 points 3 months ago

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

[-] nullroot@lemmy.world 9 points 3 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.

[-] Vex_Detrause@lemmy.ca 6 points 3 months 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 10 points 3 months 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 11 points 3 months 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 3 points 3 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...

[-] chrash0@lemmy.world 4 points 3 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