Hell yeah. Though I do always wonder if such entities mark themselves as targets for AI scraping. For instance, Wikipedia is also committed to banning slop articles. But that just means for any AI scraper it just becomes a reliable source of quality training data. So Wikipedia volunteers have to expend a lot of time and resources determining if something is slop and getting rid of it, all so that the slop trainers can come in and create the next version of the slop engine used to spam Wikipedia…
Anyway… whatever. Good for Codeberg!
I get it, but determining and moreso verifying code is mostly generated is so intractable that this will likely not do anything practically. Well, perhaps it will discourage some disclosure.
I don’t think anyone expects to catch every vibe coded project that might end up on the site. It’s seems to be about nurturing specific direction for their community, giving admins clear rules on this issue and making their decisions easier in case they do find (or get a report about) a clearly AI “led” project.
Even if vibe coder manages to stick around, they can’t be sure their projects won’t disappear at random due to the new rules. Might be enough to prevent some of them from using the site.
giving admins clear rules on this issue and making their decisions
The wording used is “mostly”. Which is concerning, because “mostly” is anything but clear and leaves a lot of room for interpretation.
Exactly.
Boosters: There’s no way to enforce this! This rule shouldn’t exist. You can’t be 100% sure a project isn’t slop. Keep the flood gates open.
Reality: We also can’t 100% enforce that people follow the speed limit, but we have speed limit laws. When we catch someone, we can point to the law. The mere existence of the law also acts as a small deterrent.
Same with Codeberg. We can’t 100% enforce the ban, but when we catch someone we’ll be able to point to the rule and kick em out. And just seeing an “AI not welcome” sign on the wall will deter some amount of people.
Speed limits are binary and easily enforceable
Yeah that is a good way to frame it. Makes sense. It does say something about their ethos.
And: false positives? How much fun is it to go to clone your repo and find it locked because something (probably an AI algorithm) decided your project was “vibe coded”?
Don’t ask me. I have nothing to do with Codeberg and I’m not involved in the process itself, I’m just speculating. I would assume that if they’re against hosting AI projects they won’t try to hunt for them using AI screening and stick to a honour system + reporting instead but I know nothing about Codeberg’s inner workings to say for certain.
There will probably be more info on that once the official announcement drops so I guess we’ll see.
The Codeberg team seems crazy solid, or so I feel. I have all my repos there except one which isn’t open source.
That’s good to know. Hopefully they’ll be able to come up with a decent solution that’ll fit their community well.
It’ll also be a great way to take down projects you don’t like. Just accuse them of witchcraft.
Good thing we have pro-AI platforms like GitHub that would never arbitrarily remove projects… Right?? Right???
That’s just Facedeer, an infamous AI booster and concern troll.
A bad faith troll could claim any genuine rule against platform abuse could be turned into a witch hunt. Rules like “don’t upload giant files to overwhelm our servers” or, since I’m reminded of someone else who claims they’re labeled a witch, “don’t harass transgender people”…
Yeah but I also get it as a thing to put down, just in case you need to mass-ban thousands of clearly-AI-generated projects. You can then just point to this ToS.
Define clearly
As in obvious. Like they have model instructions and bots credited as authors on commits.
Congrats you made a mistake. Any contributor can make commits with ai bots credited into them, and it’s not displayed to the reviewer. Meaning that for just accepting a MR that looked good, you would get banned. Nothing is obvious
The rule is for vibe coded projects. From the article:
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
They don’t need a rule that can be run automatically because it’s a purely human operation that is trying to take a stand against the more pernicious effects of corporate LLMs.
Do you just disagree with this stance and are just trying to poke whatever hypothetical holes you can in their logic, or do you just want more rigorous definitions/rules?
From experience, content moderation works best when there is some flexibility in the rules, so people can talk it out and come to concessions together.
Carighan talked about “mass-banning”. This is what I opposed to
Nobody cares for your got’em logic, it just makes you look childish.
I think a lot of the time with these things is not really about filtering every single offending project but stablishing a legal precedent to remove a project the moment it is found to be violating the rules.
- You must not share projects that mostly consist of code written by “generative AI”-tools (including services such as Claude, OpenAI Codex). Such projects having an unclear copyright status (see requirements § 2 (1) 1 and § 2 (1) 3) and furthermore have little safeguards to ensure that they do not include harmful code (c.f. § 2 (1) 5).
That feels like a reasonable middle ground. Allow some things with some AI written code, but don’t allow stuff that is a majority of AI code.
How on earth will they determine that though?
I can’t see the future, but this all doesn’t sound like an ideological “vibe code is bad, we don’t allow it” but a “the copyright of vibe coded content is unclear across jurisdictions, we don’t allow it.” So I don’t think it’s something they’ll say “hey, this looks vibe coded, deleted.” Many projects self proclaim they’re vibe coded. Many projects list every commit that is vibe coded. It seems likely they’ll go after those projects instead.
But yes, I’m not an oracle, and Codeberg could always heel turn and turn this into a witch hunt, but I don’t think they’ve earned that reputation.
It does sound like “vibe code bad”.
Because if they were actually concerned about copyright, they would ban all LLM code, not just some LLM code.
There is no need for a repository hosting software to decide what people are allowed to upload unless it is literal Nazi or kiddy diddle content or something else illegal.
Did you not read the actual change?
- You must not share projects that mostly consist of code written by “generative AI”-tools (including services such as Claude, OpenAI Codex). Such projects having an unclear copyright status (see requirements § 2 (1) 1 and § 2 (1) 3) and furthermore have little safeguards to ensure that they do not include harmful code (c.f. § 2 (1) 5).
Let’s be real here: Most future projects will be mostly written by AI.
Sure, the good ones will have proper human QA. But Claude Code is so much faster at writing and rewriting surprisingly good code, that ignoring it is just like ignoring IDEs was a decade ago.
You can still write code without AI, syntax highlighting, code-suggestions, documentation tooltips, inspections, and fully integrated version control. But all these tools legitimately make software development easier.People still ignore IDEs. In fact, in certain circles, it is seen as a badge of honor to use Vim or Emacs instead of some modern solution.
Let’s be real here, the concerns about what the copyright is of code that’s produced by AI is still sort of in the air, especially for a site that wants to host content from across the globe. Codeberg picking its battles and not wanting to deal with that for now seems reasonable.
Let’s be real here, the ethical concerns over LLM use far outweigh any copyright concerns and are the real reason people should refrain from using them in any way, shape, or form.
Seeing how codeberg is FOSS only, I’m not suprised. Vibe-coded projects is a HUGE legal trap considering licensing. And seeing how it’s based in Germany (notorious about siding with license owner against regular individuals) it only makes sense
How can I prove that I have ownership over code I wrote myself, and that it isn’t copyrighted somewhere in the world? How can anyone prove that code is written by a human or AI (if you don’t commit obvious AI harness files and folders)?
Developers also “generate” code and are also “trained” on code they written as freelancers or employees for others which is potentially copyrighted. In that aspect just because it’s written by hand, doesn’t imply the writer has copyright on it.
based. So glad I moved there recently.
I use them as one of my mirrors for public projects, but host my own repos and CI now.
A repo host that can remove your repo at any moment because someone can accuse your code of being “vibe coded” is not a repo host I’d trust. It shouldn’t matter how good, bad, or A.I. written your code is. It’s a hosting platform.
This right here
The main argument is due to copyright issues of LLM generated code. Github will happily remove repos which violated copyright laws or IP laws. It makes sense that Codeberg doesn’t want to host code which may be violating copyright law.
And anybody could try to take down your repository by pointing to copyright law in general. Bad faith takedowns are not a new phenomenon.
Just one problem with that: Every piece of work - code or otherwise, made by a human or not - may violate copyright law. There really is no way to know without actually checking against all other works (which you can’t because you don’t have access to all of them).
What GitHub does is what a sane person would do: React to claims. They just assume that what they get uploaded isn’t violating copyright until someone claims otherwise. And as it is literally impossible to actually know, that is the only sane way to approach this problem apart from just not hosting other people’s stuff at all.
And how do they know it’s violating copyright law?
What
Then why not say it’s not allowed to upload code you don’t have copyright to? This would make sense, nobody would question it and it would generally also cover AI-generated code.
Mentioning vibe coding just upgraded it into a social and moral topic, while the sole fact that AI generated code is no issue at all, just that there is not a general concensus in the world who holds the copyright to that code.
It’s kinda like blanked banning cooking, because you can’t cook without a knife, and knife can be used as a weapon.
It’s more like banning cooking anything with mushrooms in it, because we haven’t sorted out which mushrooms are poisonous or not. You could make it more accurate by instead banning cooking with anything poisonous, but of course then lots of people will keep cooking with their mushrooms, naively thinking they are not poisonous and therefore allowed.
I mean, I agree with you, but there’s still room for abuse.
Have you seen OpenClaw’s issues page?
Vibe coders and AI agents are floating it with garbage, if they were to do that to Codeberg, it’ll probably run out of resources pretty quickly
How bad cou…
HOLY SHIT
I mean the host can always remove your repo. We’ll see how they handle it; but I would assume it won’t be without care. But yet another reason to host your own as well.
What’s an LLM-extrusion?
Something extruded from an LLM?
Ah, LLM-generated code
A bell ends’ extrusion.
No idea, it’s mainly left wing progressive slop
I wonder if they have a statement on palestine
They’re German so no
Based
Hahahahaaaa hell yeah
Like anyone who’s offended by this isn’t already slopping for Microsoft’s GitHub.
Guess I’ll pull all my stuff from Codeberg then, vibe coded or not.
That’s dangerous as hell, because there is no guarantee that your stuff is deleted for the wrong reason.
It’s their decision. But I dislike it.
There’s never a guarantee that they won’t delete your stuff for the wrong reasons. That’s not something you had before this. I’m not trying to be pedantic, I just mean if that’s a legitimate concern you have that you should be backing things up in different ways as well.
Sure. And of course I’m backing up my code somewhere else.
But this clause makes it much more likely that my repositories get deleted. And there are other services connected to it, e.g. an app via Fdroid/Obtainium. Losing Codeberg means disconnecting the apps.
Has Codeberg earned a reputation of deleting things without warning and not making good decisions though?
It doesn’t matter. The door is open. I won’t wait for anyone to got through the door, by accident or not.
All that matters is that the option is there.
That door was open the second you uploaded anything to it anyway. Same for any online service.
Guess I’ll need a new host for some of my recent repos. Oh well. Nothing that I haven’t dealt with for other reasons (with GitHub and Bitbucket).
I’m not sure if these tools will stick around, but if they do I’m not sure you’ll be able to find anyone that isn’t using them in a couple of years. I hate it but it does turn out that dropping a trillion dollars on automating writing software has yielded results.
Edit: Update: Moved my personal slopjects over to gitlab which is fully embracing the slop.
I get that some people are completely against LLM assisted coding. I’m still with you guys in spirit, but if these things stick around in their current quality (which is honestly a load bearing if) I just don’t see a way to continue working in the software industry and meeting expectations without using them.
Well, whatever… its just another reason why it’s best to self-host your git services…
Were you triggered because you shat out a vibe coded app?
Very cringe thing to do when the whole industry jumps on LLM-automation wagon. This way you filter out people who actually do stuff professionally.
Good to know though. Would avoid.
The only acceptable use in the industry is using it as a code analysis tool - vibe-coding is not.
Why though? Aside from blind hate, good written JIRA stories are almost oneshot now in many occasions. You can spend more mental energy on logic correctness rather than translation of requirements into code.
Not only it is faster, but you can deliver greater quality faster. Slopware is a result of trying to crank the dev speed to the max without following proper sdlc with proper dod.
The company I work at has fully embraced vibe coding, so from my experience: it did seem faster at first, but also the amount of regressions and new bugs being introduced has gone up dramatically, and so the overall workflow has stabilised to be roughly just as fast as before AI, but now almost all mental energy is going into QA and reviewing. From the customer perspective, they saw lots of new progress initially, but have now been frustrated by constantly finding things broken or buggy.
And all this is at a company which has entire teams dedicated to trying to improve AI-based workflows and tools to make them more reliable.
So no. From someone in the field, quality has dropped a lot, and speed is only increased if you close your eyes and ignore all the tech-debt being created.
Your devs do QA, not a dedicated team?
Unit tests, snapshot tests, UI tests?
Nice one!!















