And, if those alternatives don't exist, well, you now understand why Codeberg is taking the position they are.
What if he just throws wood randomly at the table saw and tries to sell whatever pieces come out?
(Never do this with a table saw, btw. They can, and will if you don't use proper procedures, throw wood sideways at speeds that can punch through walls and impale people)
Is a musician less of a musician if they use a pre-recorded back-beat and sing on top? Are you not a musician if you use the chord mode on a keyboard?
Is code not hand-written if my editor automatically closes all of my html? What if my editor flags all of the errors and I manually correct them? And what if it auto-corrects at the press of a button?
There is a line and I'm asking about it earnestly, but the table saw analogy doesn't reach it IMO.
I feel like it may be closer to attention? That's the thing we actually value, that someone took the time and put in the effort to do something. And the quality depends on how much we value that attention. Like high effort low quality is praised when it's the work product of your child for instance.
That's not your problem.
But I guess you're right, as far as you go: none of this is my problem. I'm just a curious observer.
I did you wrong, and in general we shouldn't guess the motivations of others, but I'll still say that lot of the comments asking what is the exact meaning of that rule is, how it will get enforced precisely, strike me as seeking to undermine the validity of their decision rather than wanting to make sure they don't run afoul of it. Or even coming up with ideas to help them enforce that rule better. One even said maybe we should test if they actually can tell. I responded to you as if responding to that, and that was uncalled for.
Take the HN guidelines, for example. It's impossible to make them completely "clean cut" rules. But people know that if they genuinely think there's been a misunderstanding they want to clear up, they can contact HN. And with Codeberg it's probably like that, too. Not like Google, where the rules ideally should be 100% clear and mathematically accurate, because you just get nuked by algorithms with no recourse.
You might even say if people post on HN, they already understand what fuzzy rules are, by definition. They know language is fuzzy and that the letter of the law points at the spirit of the law. If someone doesn't want to understand that spirit, no amount of legalese detail will make them understand it. But of course that shouldn't be an argument to shut down discussion about it, either, and I didn't mean it like that.
Codeberg is different. It's a non-profit, so my criticism is mostly around all the heat and light that will be generated when they start banning projects (politically), and the amount of human effort that it will take to assess whether a project is "majority" written by AI. I just think the way the rule is written is fraught with issues that will cause a lot of wasted effort in the coming months and years.
Their stance is obvious: if you just want dumb git hosting with a freemium model, use something else.
So block huge resource use? What if people use LLMs with worry disproportionately tiny resource use?
So now your solution entails lowering the quota for everybody because allowing in LLyou must assume eve
Terms of use should be read as a statement of intent, not a series of if-then statements.
Are you sure? It's pretty easy to find telltale signs of LLM usage, like the CLAUDE.md file, the '.cursor' directory, the 'vim'-sized codebase done in a week.
They are not. You can probably draft some query to get candidates based on those criteria. And so very quickly.
> Quotas are automated, evicting projects is highly manual.
The human world is very chaotic. Automation is not a panacea, which is highlighted by Big Tech abysmal support. Sometimes, you want humans to judge, because the optimal result is based on heuristics and not rules written in stone.
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
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.
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
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.
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.
Open source software that exists for its own sake is exceedingly rare, and understanding the goals of a community before becoming dependent on it is a good idea
I readily concede that there is a huge volume of inexperienced programmers generating crap, though.
It's basically Eternal September for programming.
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.
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.
Then instead of addressing the excessive resource usage problem indirectly via banning AI-assisted apps, they could've addressed it directly by imposing limits/quotas.
It's abundantly clear (and not that they are hiding it either) that their issue is with AI itself so anything else is just a secondary concern if not even a smokescreen.
---
> I'm a solo dev, and I couldn't find the judgement against solo developers or any slight against people who don't have a team.
Quoting their blogpost [0]:
> ## The development team of none
> Using LLMs to work with your code gives you a kick of adrenaline. You can develop at a rapid pace, build things as if you had a large team. Only that you have none. In fact, you are (often) alone, working with a statistical machine that turns energy into code.
I couldn't care less about what they think about solo developers, but it's just one bad excuse after another and that's what people are criticising. Open Source is one person. [1]
---
[0] https://blog.codeberg.org/protecting-our-floss-commons-from-...
The problem (or the virtue?) of this comment is that it's impossible to decipher with which side it disagrees, and for what reason too. Cause both sides expressed their right to do or not to do.
> Play ball or get out.
People can say things on their way out, and this is what's happening.
At least in the US tax-exempt status carries obligations.
If you don't want to be banned, you're welcome to email [email protected] and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html.
Citing the op themselves: “ an alarming number of self-described AI experts whose expertise appeared to consist entirely of having a ChatGPT or Claude subscription and the willingness to write about it in seventeen-paragraph posts.”
Just saying "no spam" means you don't have to waste a single byte on spam and everyone else can have a higher quota.
For one, they've already done this to an extent. For two, they're also doing this by deciding what projects are and are not welcome on their service in the first place.
If 9 people eat an apple or two a day but a tenth person wants to eat 100 apples a day, we don't have to set some apple limit. We can tell the tenth person to pound sand and keep giving everyone else the apples they want.
Hell, I'd argue that Vibecode without the prompt that generated it isn't even real open source.
The learning doesn't come from copying and pasting code from stack overflow. It comes from
A) searching which code to copy and paste
and
B) Fixing the broken code that you just copied and pasted.
I suspect most programmers outgrow the "copying and pasting from stackoverflow" period of their development pretty quickly when they get frustrated by the fact that most of the stuff they were copying and pasting is broken or sub optimal in some way. If they prompt claude "write me a function", and then when it's broken they prompt "fix the broken function", they're learning (and doing!) a lot less.
DO NOT try to spin that into taking some form of moral high ground. DO NOT make yourself the arbiter of what is and is not considered a worthwhile project. That is not neutral. That is not free.
It's not fair for everyone to have to eat the costs of AI (like communities getting bulldozed for data centers) and just accept that it has to be used.
For example, in the case of being overloaded by AI contributions, a neutral solution would be to implement the same rate-limiting for every project. Set a sensible limit, and enforce it universally. Do not discriminate specific projects.
It is like saying Gmail shouldn't delete spam, but instead, should apply a limit of 1 message per day per destination per source address to all messages.
Most vibe projects aren't even projects in the way that spam isn't even mail. The message says it's from my bank but it isn't. Why should I have the same limits on messages that say they're from my bank and messages that are actually from my bank?
Yes, human rights should apply to anybody, including war criminals. That is what makes them HUMAN rights.
Universal freedoms and neutrality should apply universally, including to waste-of-time-and-resources AI slop. That is what makes them UNIVERSAL and NEUTRAL.
> It is like saying Gmail shouldn't delete spam, but instead, should apply a limit of 1 message per day per destination per source address to all messages.
I said a REASONABLE limit should be applied. 1 message is not reasonable and you know yourself that this is a bad faith argument if you are honest.
1k messages on the other hand would be a reasonable limit. There is pretty much no legitimate use case for sending more than that to any specific address from any specific destination in a single day.
It is also bad faith because Gmail never claimed to be free or neutral.
My point is: Codeberg is not a neutral and free git forge. I wish that it was.
What they are doing is completely within their legal and moral rights. I just disagree with it.
He also has a lot of posts since: https://mastodon.social/@[email protected]
I don't think this is a fair summary. I don't see this conflation in Codeberg's blog post. The words in quotation marks don't actually exist in Codeberg's blog post.
It seems that what they are saying is: In a free hosting platform where we share all the resources, it's not fair that some people using LLMs are using up disproportionately huge hosting resources to handle the unnaturally large amounts of resources they can churn out with these tools.
I'm a solo dev, and I couldn't find the judgement against solo developers or any slight against people who don't have a team. The concern is that some people don't gobble up an unfair amount of resources.
I personally have been moving to self-hosted Foregejo for ultimate freedom. But I also think it's fair for some providers have the freedom to take a bit more of a harsh (or based - depending on your perspective) stance against LLM generated code. I mean, a lot of people have been bemoaning the fact that the human-generated material has been increasingly hard to find in a sea of AI-generated material. It could be nice to have a corner of curated, human-made code still available on the web.