Ok, bye bye
Ok, bye bye
Posted Jul 23, 2026 17:00 UTC (Thu) by rrolls (subscriber, #151126)In reply to: Ok, bye bye by mb
Parent article: Codeberg: Protecting our FLOSS commons from LLMs
There are clearly a lot of people who disagree with you there, starting with the 358 people who voted for it!
From what I've read over the last ~year, there are a _lot_ of people who strongly believe that code should not be generated by LLMs (and it appears a fair subset of those believe that AI should not be used at all, for anything, ever). This decision will make Codeberg very attractive to these people, so I very much doubt it will "kill" it; rather, I think it will only make Codeberg even stronger within that market.
Just yesterday at $DAYJOB, the subject of the zig bun fiasco came up, during which I pointed out that the Zig project strictly disallows AI generated code contributions. A colleague immediately responded with something to the effect of "well, that's going to make sure no one uses Zig, then". To which I rebutted that no, it won't kill Zig, it will simply create a strong correlation between "those who use Zig" and "those who are against using AI for code generation". They didn't back down, so I left it at that; they seemed to have used exactly the same questionable logic as saying "being against AI will kill Codeberg".
And I say the above as someone who is (strangely?) more-or-less neutral in this whole AI "debate".
In practice I think this is a good decision. It will let them focus their limited resources on hosting projects that do more with less, rather than hosting generated content that objectively requires orders of magnitude more resources to do the same thing. As someone who has on numerous occasions struggled to access Codeberg with it being slow or completely unavailable for periods of time, I am very much on board with this movement.
It is worth taking note, by the way, of the following section of the Codeberg blog post, which confirms that you're not just going to be taken down for having "a tiny bit of LLM poison" in your repo:
> Some early, but informal guidelines
>
> If your work fits into these cases, it is unlikely that you are affected at all:
>
> - Projects who have an active community that cares about and maintains the software
> - Projects with a significant pre-LLM history
> - Maintainers who unknowingly or willingly accepted LLM-generated contributions from other contributors, if your project otherwise does not involve the heavy use of LLMs
