I don't get why people who want to use LLMs to generate code are grumpy because Codeberg doesn't want to host it.
Surely they can just use their LLMs to generate a replacement for Codeberg, which they can operate on whatever basis they choose?
Discussion
I don't get why people who want to use LLMs to generate code are grumpy because Codeberg doesn't want to host it.
Surely they can just use their LLMs to generate a replacement for Codeberg, which they can operate on whatever basis they choose?
@neil my only slight niggle with Codeberg's policy is the slightly subjective (lack of) definition of "mostly generated", which I can't help feeling opens the door to endless debates about how much is too much.
@ahnlak Were I looking for somewhere to host LLM-generated code, I'd take the decision as a sign that I was not welcome on Codeberg, and look for hosting elsewhere.
@neil absolutely, and that's a very clear signal.
LLM usage isn't binary though. The "mostly generated" clause suggests it's fine to have used an LLM to build a small function, for example - at which point, but not putting a number on it, you're into "how much is too much".
To be fair to them, it feels like they're taking a very pragmatic position of effectively saying "no LLM-code, but we're not gonna be fanatical about it".
@neil and SlopHub is right there, too.
@neil They're worried what else they might decide they don't want to host since they now ban things.
I am, of course, joking.
They can just run their own instance of forgejo, without needing to generate anything.
@neil said the same exact thing
@neil Yabbut, unlike vibe-coding that requires some actuall skill and understanding what you are doing...
@neil Forgejo is *so* easy to host, too. I run my own just because I like having somewhere to keep scripts and bits for my servers.
@advancedrubbish Same!
For some stuff, just running git is ideal, but for other stuff, I like forgejo.
What if Forgejo starts using LLMs to craft itself? What if a library Forgejo starts using LLMs to craft itself?
The genetic fallacy is real, even though I agree with Codeberg's stance.
Point 1 is not going to happen - Forgejo is itself hosted in Codeberg, and thus has a vested interest in not using LLMs itself for development. Point 2 is the more worrisome part though - I'd first need to do a dependency table to check which external dependencies does Forgejo still have, and most importantly, which ones can be replaced or forked to the last LLM-free version if push comes to shove.
@csolisr not only is Forgejo hosted on Codeberg, Forgejo has a strict no-LLM policy that goes much further than the new codeberg ToU.
@matthewcroughan @neil It's really not though???
Forgejo is hosted *on* Codeberg, and I believe they already ban AI submissions
Yes, I understand that. But it doesn't take long, if you look at the dependency graph to find something that they depend on that is being contributed to, using Claude with harness for its daily maintenance. For example, go-redis. It has a reasonable amount of contributions now, powered by Claude.
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/go.mod#L89
@matthewcroughan @HuguesRoss @neil Let's fork go-redis from before the claude contributions, then
@neil@mastodon.neilzone.co.uk or even just self-host Forgejo, which their LLM surely is able to explain to them
@sijmen Ha! I've just posted exactly the same thing :)