Comment by adamddev1
4 days ago
Making a principled ban against LLM would seem to allow for more freedom and flexibility with usage limits. People who are creating more by hand would still be allowed to have more breathing room. With a hard limit of resources everyone would be more restricted. That's also a solution, but it's just a totally different approach. The LLM ban could help to allow for freedom without the resources getting overwhelmed.
Only if you can reasonably separate LLM from non LLM code, which is in no way a solved problem. Even if one agrees with their priorities 100%, it's just asking for non-automated enforcement. It's difficult to execute, and either lead to completely arbitrary enforcement, or a lot of resources being spent in exchange for this freedom you mention. It's just a very hard practical line to try to draw.
And let's be real, most of the costs LLMs incur on hosting providers have little to so ln who makes commits. A popular project than bans LLMs from contributing, but is used often by LLMs that are using the project as a library is indistinguishable from one that allows LLM contributors.
So from a practical perspective, it's a head scratcher
It's true that an LLM ban is really hard to enforce, but that doesn't mean it's worthless. If i make an image editor and say "It is my policy that serial killers and pedophiles cannot use my software" i can't really enforce that, but it still makes a (somewhat useless) statement.
In my opinion, not allowing LLM code at least signals that codeberg (and forgejo) itself is unlikely to be majority LLM code, which raises its stock in my book; It signals what kind of people the maintainers are.
> what kind of people the maintainers are.
Can you elaborate on this? It's new that we're judging what kind of people we're dealing with based on what tools they use.
2 replies →
If you made this statement and you catch a serial killer using your software, it affects the options. A more reasonable example may be: Microsoft may not reverse engineer this. They still can do it privately - you can't enforde it - but if you catch them, then you have more options besides saying "welp, I said they could"
> Only if you can reasonably separate LLM from non LLM code, which is in no way a solved problem.
It's trivial to detect when someone's coding with a chatbot - they tell you, repeatedly.
Nobody who doesn't code with a chatbot worries that it's hard to tell.
Apparently some people have compared it to some other unlikable groups of people (I know this because a vibecoder complained about the comparison someone else made)
If someone has to ask whether their software is mostly AI-written, then it is.
If someone has to ask exactly how racist you have to be before you can be called a nazi, they're probably a nazi.
If someone has to ask how attracted to underage girls they can be before they're a pedophile, they're a pedophile.
If someone has to ask how responsible you have to be for a death before it's a murder, they're probably a murderer.
Because people who aren't these things clearly know that they aren't.
> principled ban against LLM
So was it about high resource use, or a principle?
> People who are creating more by hand would still be allowed to have more breathing room.
What about the breathing of people creating by hand with a sprinkle of an LLM?
> but it's just a totally different approach.
Indeed, a better one where you manage directly the issue you claim to care about
My interpretation is that the resource usage should be roughly proportional to the human activity involved. That wouldn’t restrict resource usage by any individual project, which might be a popular project with many contributors and a lot of activity, but the resource consumption needs to be justified by corresponding human effort and interest, which LLM usage doesn’t exhibit.
https://blog.codeberg.org/protecting-our-floss-commons-from-...
In this corresponding blog post, one point made is that LLMs tend to LARP big-project infrastructure on small projects. They use the resources for something like GNOME but they aren't actually GNOME so they don't have any excuse for it.
Both. They noticed the high resource usage of LLMs and decided that LLMs, in general, aren't worth supporting.