Comment on Codeberg bans vibe coded projects
Epp@lemmus.org 1 day agoYes, I am. I have a global pre-processor directive for all of my prompts, so it always includes “match existing code style, formatting and conventions.” The result is indistinguishable from hand written code. Thinking you can magically discern what was written by AI is delusional.
Sorry but you are clearly delusional. There is no magic involved, just being able to look at the structure of the code and the pattern of the commits. It’s fairly easy in fact.
Epp@lemmus.org 1 day ago
Oh, I see. You assume agentic AI that can perform it’s own commits. That would make it easy to tell, but you’d have to be really stupid to give AI such unfettered access to your repository.
TrickDacy@lemmy.world 1 day ago
So 1) we absolutely know people are much stupider than that. and 2) does exactly that has widely been observed.
Epp@lemmus.org 1 day ago
Oh, without a doubt. They’ll get some low-hanging fruit, I’m sure.
JustEnoughDucks@slrpnk.net 1 day ago
And many, if not most, of the people vibe coding projects on git repos are that stupid. People who have never coded and never used anything other than
git clone. That is just a fact of many of the people who do it. They are the people who think they are tech geniuses because they once made an LED blink on arduino or made the millionth timer app.It is just a fact of who is flooding the most slop projects. There are plenty of people who use AI in subtler or more useful ways, but that is not what is the target of anti-vibecoding rules. It is the 1000 slop projects generated bloated repositories fully in 1 day that are killing bandwidth and storage limits for everyone else.
Epp@lemmus.org 1 day ago
That makes sense.
No need to asdume that. Just by using LLM to assist with code writing, the human in the loop changes their commit pattern.
Epp@lemmus.org 1 day ago
“Suspicious commit pattern” sounds like a pretty flimsy basis for banning a human from the platform. If nothing else, this futile crusade will be entertaining for almost everyone; except for their support staff who will need to investigate and either defend or repeal the been each time there’s a false-positive, and a person is accused of wrong-think because yesterday they commit twice in an hour whereas they usually only commit once per hour.
Zink@programming.dev 1 day ago
All you need is another one of those global pre-processor directives! Then you’ll have commits that exactly match human output just like with the code itself!
Epp@lemmus.org 1 day ago
Technically, yes.
“Make commits sporadically, using inexact terms, occasional typos and every once in a while, forget to include a file that then necessitates a follow-up commit of a single line that simply says ‘whoops’”