solution is to use AI to review the AI slop 
Timeline
Post
Remote status
Context
4
:gondola_head: 🌿 
@kaia
>idk how we can keep it up
It's simple.
Do a "community slop" fork and tell all AI contributors that this is the place to put your slop code.
Call the main godot source stable and the slop on unstable.
>idk how we can keep it up
It's simple.
Do a "community slop" fork and tell all AI contributors that this is the place to put your slop code.
Call the main godot source stable and the slop on unstable.
🔻🪂
@mangeurdenuage @kaia Serious Open Source projects should start prompt injecting anyone that's using an AI editor.
If you add enough cursor rules (and other slop editor pre-prompts), you can hide anything there.
If you add enough cursor rules (and other slop editor pre-prompts), you can hide anything there.
@MechaSilvio @mangeurdenuage @kaia It's fun finding new projects on git* and seeing all the comments where AI has mentioned what the functionality is supposed to do given the environment of the prompter
@graf @mangeurdenuage @kaia How many years until experienced devs that think they can "just review" AI code start forgetting important things
https://m.youtube.com/watch?v=d2nmG01jsqA
https://m.youtube.com/watch?v=d2nmG01jsqA
Replies
3
@MechaSilvio @graf @mangeurdenuage @kaia less than a year based on something I read from a guy that was saying he is losing the ability to read code
@MechaSilvio @graf @mangeurdenuage @kaia but the obvious answer is make all code requests include 'nigger' in the comment
Relevant post I read earlier today. AI got ass blasted he didnt like its code so it published a smear article on him.
https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/
https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/