Comment by Aachen
5 days ago
I'm a member of Codeberg and was allowed to vote on these amendments. There was the annual assembly meeting before the ballots were sent by email. Each proposal had a short presentation and a few minutes of Q&A.
It wasn't a discussion (the text was final at this point), it was just to ask for clarifications. In the meeting I asked about the server load that they mentioned in their presentation, but misphrased it and got some answer about (AI?)bots scraping Codeberg and not if auto-generated code being shared on Codeberg is actually an issue.
It seemed pretty useless compared to commenting on the ticket where one could have a structured discussion. I also don't know how many of the >1000 members were in the meeting in the first place and how many just got the email "Wanna ban AI? Vote now!"
Once the results were announced, the rest of the users came into the ticket and started asking questions https://codeberg.org/Codeberg/org/pulls/1253#issuecomment-19... This was then shut down and if you have questions you should join the chat room on Matrix
There was also a discussion on the codeberg forum. Anyway, I hope this new rule will be overturned in the future. I think it invites arbitrariness and besides, whether or not a project was vibecoded (and how much) doesn't really decide how useful or even how well-written it is.
it would be better to encourage people not to have agents create repositories. i think that is the actual issue they want to tackle, while people manually making projects and then having AI write code should obviously be allowed at this point. it will only evolve more, and people can trivially hide it by instructing the LLM and doing manual commits :/
[flagged]
So I voted against, partly because I feel that the text doesn't to justice to such a multifaceted topic.
If all projects on Codeberg were human-written, that would be a big seal of quality! There are a lot of projects coming out now where someone feels like they've made a cool thing but it breaks on the first edge case and is entirely unmaintainable. Many are built on wrong principles because the prompt authors aren't savvy and don't know better. Some authors (I've encountered this in the OpenStreetMap community) even have the gall to pretend that their code is a gift that we now have to host and maintain. Aside from these quality and community issues, build and test pipelines also take a lot of compute resources, and with large growth in projects, that will increase as well. That the author of the proposal wants to avoid this makes a ton of sense to me.
But it also drives a lot of projects away because maybe you later want to use LLM assistance (imagine LLMs got twice as good as they are today), or maybe the auto-generated tests might become >50% of the code. You'd have to migrate your repository and community away from Codeberg. Why take that risk? It's just not a worry I feel that developers need. They're looking to get away from Microsoft (GitHub) for their open source project and that's the point where Codeberg should be a no-brainer
We're an open source community and so the mass stealing of all our work to feed LLM training which heats the world and causes (at least temporarily) giant price hikes in consumer hardware... there's a lot to say for more ethical training and use of LLMs, but does it matter at all if Codeberg bans LLM output? Won't we just make ourselves obsolete? Idk. It's multifaceted and this proposal seems too vague and blunt for me. That's not an option that's set in stone btw, just my current understanding of the different aspects
You'd have to migrate your repository and community away from Codeberg. Why take that risk? It's just not a worry I feel that developers need.
I feel like we are already there. I am not vibecoding a lot, but I certainly use LLM-assisted coding now for most of my work. Once you go beyond vibe coding, an LLM feels a lot like a compiler from your well-specified ideas to code. So, to some extend, these restrictions feel like disallowing a higher-level programming language in a time when everyone was still writing machine code.
I understand where this decision is coming from (especially because they have been under attack by LLM bots) and it is well within their right, but the vague language adds a lot of uncertainty:
You must not share projects that mostly consist of code written by "generative AI"-tools
It's clear that this excludes vibe coding. But what about LLM-assisted coding, where the developer writes very clear instructions of what to do and carefully reviews every line? In such cases a project 'mostly consist of code written by "generative AI"-tools', but the quality is probably not worse than fully hand-written code, especially because an LLM is often more able to 'think' of all kinds of corner cases.
I have some projects on Codeberg and donate monthly, but I have to reconsider both, since with this change Codeberg does not really align with how I work anymore. The projects that I have on Codeberg are largely human-written, but certainly use LLM-assistance for new code.
At any rate, I guess I'm back to GitHub until I have found a better alternative.
> It's clear that this excludes vibe coding. But what about LLM-assisted coding, where the developer writes very clear instructions of what to do and carefully reviews every line?
My impression is that they don‘t care, it’s still ”slop” for them and for most of coderbergers for that matter.
But I do exactly this. It‘s a code base that I have written prior manually, before LLMs, so now this helps a lot with boilerplate and add features. LLM-assisted is not vibe-coding, but FWIW I don‘t care what others think.
1 reply →
A big seal of quality because it is human written? Maybe in narrow spaces but in general, I’d put money on the average developer being significantly worse at writing code with bugs than an AI. It’s codebergs infra so their choice, but it seems like an overly simplistic solution to a complicated advancing technology, in that it is a threadbare line between “vibe-coded” and “complex agent harness with human oversight and review”.
Also, I’m actually quite happy with some of the vibe-coded apps I use. Handy is an example, which started as a vibecoded app, and is fantastic for STT/dictation. It seems like a literal baby with the bath water approach.
> I’d put money on the average developer being significantly worse at writing code with bugs than an AI.
I'd put money on the average AI-coded project being of a worse quality, simply because the number of vibe-coders with no experience now outnumbers actual coders using AI-assist around 10 to 1.
I'm literally seeing companies being pitched with B2B products written by people who had never written a program before, even as a hobby!
AI on average might write better code, but there's no way AI prompted by a shoe salesman is going to be better than code written by a person with even 2x years of experience.
9 replies →
I’d put money on the average developer being significantly worse at writing code with bugs than an AI.
I'd take that bet if it was measured in "bugs per day" instead of "bugs per LOC". LLMs generate far fewer bugs in absolute terms, but they also generate far more code, so it probably balances out if everything is equal. I think LLMs will actually lead to more bugs just because they're usually working with poorly defined requirements (prompts) and they guess to fill in the gaps based on the averages of their training data. A lot of those guesses are wrong.
Where LLMs win though is the severity. An LLM will write buggy code in the sense that it doesn't do what you wanted it, but not so much in the sense of security or data loss bugs. They get that right more than humans because they're trained to care about that stuff. There's far more "how to write good code" content in the training data than "how to not care about security and go fast" content (because writing that would be weird!)
1 reply →
I'd rather read bad poetry written by a person than anything generated by a machine.
Even if an LLM generates "good" poetry, it did not, it mashed up elements of good poetry previously written by people, but stripped of all attribution, and stripped of all intents and insights of those original authors.
Since software has a function besides pure art, it's tempting to think of it as actually nothing but function, and so it doesn't matter how a functional thing comes about, merely that it functions. But I say there is more to software than that, and I'd rather not spend my own time and attention on things that no one else spent any of their own time and attention on.
Maybe codeberg is reacting too crudely, so maybe I don't defend them or this action fully in it's current form, but there is nothing ridiculous about the concept of a human-only filter being a seal of quality. The quality isn't the code all works the best, the quality is it's all human.
1 reply →
I'm not saying you can't be happy with autogenerated software, especially for something like a dictation app where the main functionality amounts to a language selector (or calling into a detector) and calling TTSlibary.render(String text).play(). You could also just use an existing TTS app, but whatever works for you
For more complex software, so far it has been my experience that you get more predictable behavior (fewer edge-cases), performance, and relevant (but, to be fair, less comprehensive) documentation when someone thought about and built it
4 replies →
[dead]
[dead]
>> There are a lot of projects coming out now where someone feels like they've made a cool thing but it breaks on the first edge case and is entirely unmaintainable. Many are built on wrong principles because the prompt authors aren't savvy and don't know better.
It would be nice to have concrete examples of that kind of project.
> imagine LLMs got twice as good as they are today)
I have no idea how you'd quantify that, but they're pretty good already. At least in the hands of someone who knows what they're doing.
I share everybody's concern about many aspects of LLMs; copyright, data collection, energy use, component prices, not to mention what it does to us: outsourcing our thinking, dependency, slop. And I don't entirely disagree wanting to limit that.
And yet, I have just written a library that I was planning to put on Codeberg, but I've used a lot of LLM assistance for it, because it's simply too big otherwise. I put a lot of effort on code quality and architecture, and I don't think this counts as slop, but I do think it violates Codeberg's new rule, so I guess I'll have to look for another place.
No idea where yet; I don't want to go to Github, and I believe there were similar concerns about Gitlab, so I don't know where to go yet.
> No idea where yet; I don't want to go to Github, and I believe there were similar concerns about Gitlab, so I don't know where to go yet.
Perhaps https://radicle.dev or https://tangled.org would be fine for you?
2 replies →
If you could have built it yourself but it was just too much work for the available time, then I trust that indeed the architecture will be sound and it sounds to me like it should be fine to build this way and host on Codeberg... until this amendment :/. I feel sorry that I'm part of this organisation that just shut the door on you
How's your appetite for self hosting? I've only ever hosted the predecessor of Forgejo, Gitea, and that was a breeze. Sadly I'm not aware of other open source hosting platforms, like, if you search "forgejo is confirmed" (with quotes) you find a lot of instances, but the point of Codeberg was the (presumed) longevity
1 reply →
> No idea where yet; I don't want to go to Github, and I believe there were similar concerns about Gitlab, so I don't know where to go yet.
FWIW I just gave up and went back to GitHub. Not because I like it. I hate the organization.
But having been burned with the year long diversion through Codeberg, and actually caring about getting eyes and contributions on my project, I have no appetite for playing more games here and ending up back in the same situation in another year.
I could self-host, and I'm willing to front that cost. But it would be frankly at the cost of getting eyeballs and contributions. And come with hassle to boot.
I already had a read only mirror to GH from codeberg anyways.
you say human code is better but in reality it is not. a lot of human code is garbage. i am sure if youd look at mine you would be horrified. moritified. a lot of people just have fun with it.
what you imply is only wanting 'professional' projects on there written by professional programmers. This seems like some exclusive membership would be more adequate. no need for fees, just invite the people whos code you like to see -_-
I had a project on there. The vote result was clearly already a foregone conclusion the moment it was announced. Any voices that even asked for clarification were shouted down on multiple forums. I had never joined as a formal community member to get involved in voting on there, but saw no point in doing so prior to the vote. The tone on external forums (Mastodon, etc.) was just brutal, and the discussion on the PR confined and curtailed.
I've already been downvoted to oblivion and insulted galore on yesterday's thread for commenting on this so I don't have much energy for it today but I'll say this:
Nobody can reasonably fault a community if they want to define their own limits and terms to engagement with their resources. They can legitimately be angry and frustrated if you do so retroactively and without clarity. I put a lot of work into moving onto Codeberg in the first place -- because I (thought I) shared their values. There was not a single note or concern about agentic tool use then, nor in the 10 months I was on there.
Further the actual blog post that finally described the terms and how they will do enforcement came after the vote on the rather narrow clause in the PR. So, again, no, this is not a healthy democratic process.
And then I had to put a lot of work into moving off.
That's my time and energy and the energy of my contributors wasted and it's just strikes me as poor behaviour driven by a crowd with pitchforks that wants to wave them and had a priori defined an in and out group.
... But at least I had an LLM minion to help me with the moving off part.
The problem with politically radical communities is that sooner or later you'll find yourself on the other side. "I didn't speak out because I wasn't X" and all that. I never liked codeberg because I saw the writing on the wall. GitHub is flawed, but it is at least more tolerant of dissenting values. You can both host anti AI and pro AI content side by side; imagine that!
Troubling, though I see it's a typical internet half-off-topic discussion. What kind of conversation has been present in the chat room?
> What kind of conversation has been present in the chat room?
The original reply that closes the issue is this:
> This is not a place to continue or start a new discussion about AI or not AI and its copyright status in the world, it will not change the results or how its going to be interpreted. I'm closing this issue, you're more than welcome to continue this at https://matrix.to/#/#codeberg-offtopic:matrix.org
Make of the room topic what you will.
Needs to be a member of parent #codeberg, which is invite only. I wonder if they gated the room after public backlash?
1 reply →
I didn't join the chat so I don't know that. It's final now anyway, nobody can change the text (next year you can propose another vote). No idea what the point would be of ephemeral conversations about it
Sounds very disingenuous and manipulative in nature. Thanks for letting us know.
[flagged]
Nobody is LARPing an Eingetragener Verein, they're just being one, and the law requires them to have a board and presidium.
As they got hundreds of votes on the issue, that means tens of thousands of euros in membership contributions. It doesn't seem unreasonable to want to create a legal entity for that, and an e.V. is easier to set up in the beginning (although it can lead to a lot of drama later).
[flagged]
6 replies →
Sort of yeah! I got used to it by now. At the local hackerspace we have a voorzitter, penningmeester, and secretaris -> president, treasurer, and secretary I think would be the English terms. All sounding fancy and together they're the board. But they don't dress up or anything, it's just terms that are commonplace for small organisations here, in Germany (like with Codeberg) as in the Netherlands (like our hackerspace). In practice people just do as they see fit, the titles are often just a formality and not taken seriously unless you can use it to teasingly redirect work onto another person :)
That's normal for any "vereniging", "Verein", union or association. My VVE (HOA) has that too. So did both of the student unions I've been a member of. There are organisations for playing games that have the same structure. As soon as you've got any kind of money or responsibility involved, you need some governance structure, or you're just giving your money to some guy.
1 reply →
I think German non profit organizations are required by law to have a certain level of governance structure.
Ah, interesting! I didn't realize they were German, and didn't realize it's a non-profit as well. I thought it was just an open source project and that was that. That would explain the bureaucracy.
2 replies →
Guess the Germans woke up and had a board meeting about this comment lmao
> I also don't know how many members were in the meeting in the first place and how many just got the email "Wanna ban AI? Vote now!"
Was that actually the subject of the email? If so that's nuts.
Sorry, I didn't mean to give the impression that was literal. I just assume that's how most people read the proposal. Looking it up, the email was:
> Subject: New poll on polls.codeberg.org
> A new poll has been created on polls.codeberg.org:
> Poll Question:
> Disallow vibe-coded projects (Terms of Use amendment) Do you agree to the changes from the Pull Request https://codeberg.org/Codeberg/org/pulls/1253/files being accepted?
> Plese vote with token [my_vote_token] here: https://...
> This vote is completely anonymous, voting slips are not stored, only a counter is incremented, your token is not associated with you or your IP address in any way and neither this mail nor your token when voting will be written to any log file.
> [some more info about how to use your token]
The voting URL is disabled now (or at least it currently shows me a blank page) but I remember it quoting the proposed amendment text and you could click agree, disagree, or abstain
Ah okay, and no problem!