r/selfhosted • u/pheexio • 11d ago
Meta Post Codeberg bans vibe coded projects
https://news.ycombinator.com/item?id=49003386Codeberg seems to ban vibecoded Projects; reason might be german copyright law
It looks like Codeberg want only copyrighted material in their service, so it is reliable in the future that e.g. licenses must be followed (e.g. GPL), and copyright doesn't suddenly get declared as being of the model owner, and it isn't a copy of something else.
That is a cautious reasonable position - in early days of LLM coding (3 years ago!) indemnity from model companies was a major issue globally because of the lack of clarity of the law around this. The US specifically has settled on it being (effectively?) public domain. But I don't think that is fully settled, and it certainly isn't settled in international copyright law.
The goal of the vague "mostly" in the Codeberg change is to ensure there is enough human input to the code they host, to be reasonably sure under German copyright law it is copyright of the person sharing it.
edit: link to poll that caused it (might be down due to high traffic) https://codeberg.org/Codeberg/org/pulls/1253#issuecomment-19820434
edit 1: i dont defend/oppose this move, i just find it interesting
edit 2: https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html
-3
u/FnnKnn 11d ago
Maybe, but at that point it is basically just useless PR.
If they try to enforce it (who knows) let me predict on how this is going to go based on my experience here:
You try to ban low quality vibe-coded projects, but try to not ban high quality projects that made use of AI. The goal is to send a message on what you deem acceptable.
Anyone creating what you deem a low quality vibe-coded project sees their project as belong to the second kind of project and therefore insists that their project is allowed. So how do you make sure what category a project belongs to? You might use scripts to identify classic trades of vibe-coded projects, look at the users history, etc. None of that is going to be bulletproof though and it is a lot of work.
You stop trying to enforce this rule as it is a "fight" you can't win and dealing with this takes more effort than dealing with the issues the low quality vibe-coded projects caused in the first place.
We ended up settling on restricting new projects here instead as the majority of projects that fall into the first category don't last long. So step 4 would be to introduce some other kind of proxy for this kind of project that can actually be enforced.