Comment on Codeberg bans vibe coded projects
povoq@slrpnk.net@slrpnk.net 1 day ago No need to asdume that. Just by using LLM to assist with code writing, the human in the loop changes their commit pattern.
povoq@slrpnk.net@slrpnk.net 1 day ago
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.
Most LLM users don’t try to hide it and the commit pattern is a result of the LLM assisted workflow, thus without losing the perseived benefits of using LLMs it can not be easily hidden. And the pattern isn’t only about when but also what. You might be oblivious to it, but the pattern is very clear and not possible to mistake with regular code writing patterns in an overall project. It is harder to spot in individual smaller PRs though, but that isn’t what Codeberg’s new policy is targeting.
And anyways, this isn’t a question of “wrong-think”, but simply of Codeberg not wanting to be associated with such low quality, likely copyright violating and resource hogging projects. The LLM using people have plenty of other code forges to use, so it is really a non-issue 🤷
Epp@lemmus.org 1 day ago
They haven’t had a reason to hide it before now. I wouldn’t be surprised if someone now “vibe coded” a suite of obfuscation tools specifically to avoid detection.
Yes, that’s why I said it’s a matter of prejudice. Assuming the projects are low quality, copyright violating and resource hogging are all conclusions reached by prejudice. You’re right there are other options available; my comment is just an observation.
It’s not prejudice if it is objectively true 🤷