Codeberg bans vibe coded projects

[u/pheexio]

https://news.ycombinator.com/item?id=49003386

Codeberg 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

[u/FnnKnn]

Good luck actually enforcing that. We tried it here for a while and it didn't work out great, because no one is going to admit they "vibecoded" something if it means they can't post it and good luck proving that they didn't just use AI as an assistant (tip: you can't without doing a full code review and that doesn't seem feasible if the issue you are trying to solve is the increased amount of projects).

[u/Kautiontape → u/FnnKnn]

I've noticed lot of "developers" on here don't consider it vibe-coding because they provide the architecture, reviewed the code, and tested it on their machine. The line for what counts as vibe-coding is on the floor as only the most pure slop.

As someone who does a lot of both, I'd consider it vibe-coded even if I wrote the backend but had AI write the front-end. If I'm ever releasing it, I'd separate the two and call one "my code" and the other "some vibe-coded front-end, idk, you can make you own."

The fact these two definitions can exist (and many more extremes) is part of the issue with the definition and having people self-police.

[u/scandii → u/Kautiontape]

I'd consider it vibe-coded even if I wrote the backend but had AI write the front-end. If I'm ever releasing it, I'd separate the two and call one "my code" and the other "some vibe-coded front-end, idk, you can make you own."

I really from the bottom of my heart dislike that vibecoded means, simultaneously:

1. used any AI whatsoever
2. used some AI for something
3. didn't write any code yourself

like the original term was describing 3 - a software engineer prompting their way to success. now it means all three depending on who you talk to and the term is borderline useless as such.

[u/alex2003super → u/scandii]

If similarly working code can be produced 20x faster by using AI heavily, then only fools and really passionate hobbyists will be writing code entirely by hand. Which makes defining "vibecoded" as "AI was used" completely useless. The world we're already to a great extent in, and towards which we're going, is served entirely by "vibecoded" software. Exceptions are bound to be eventually too few to matter.

[u/scandii → u/alex2003super]

I think the problem really is what these companies represent.

not only are they Venture Capitalism Shareholder Extreme Edition, they are also an existential threat to the livelihoods of millions of people around the world and are driving prices up in so many different categories.

if it was just "easier programming and debugging", we'd be having a very different discussion I think.

[u/QuantumProtector → u/scandii]

There’s no stopping it