I thought I was joining the promised land of free software. Instead, I got a lesson in what ‘community’ really means.
When I migrated to Codeberg, I believed I was escaping the corporate overlords of GitHub. No more algorithmic feeds. No more surveillance. Just pure, unadulterated open source idealism. Then they banned LLM training on their servers, and suddenly I was the bad guy for running a bot that scraped public repos.
The backlash was instant. ‘You’re the reason we can’t have nice things,’ they said. And you know what? They were right.
The open source community is not a democracy. It’s a dictatorship with good PR.
Let me be clear: I’m not defending my scraper. I’m defending the illusion that any platform can be ‘truly open.’ Codeberg’s new terms aren’t a betrayal of free software principles. They’re a necessary act of self-preservation. Every community that wants to survive must eventually draw a line in the sand. The only question is who draws it, and what they keep out.
Most people I know are delighted by the ban. They see it as protecting their projects from being fed into a black box without consent. And they’re not wrong. The problem isn’t the ban itself. It’s the lie we tell ourselves that a platform can be both open and sustainable without excluding anyone.
Every community is a walled garden. The only question is who gets to build the wall.
Codeberg’s founders always said they hosted only free software. The AI training clause was a loophole they never anticipated. Closing it wasn’t hypocritical — it was evolution. The real lesson here is about governance, not AI. No platform, no matter how well-intentioned, can survive without the power to exclude behaviors that threaten its existence. That’s not a flaw. That’s the definition of a community.
You’ve probably felt this tension before. Maybe you’re on a forum that banned a certain type of discussion. Or a social network that kicked off a user you disagreed with. It feels like censorship. But look closer: every boundary is a declaration of identity. ‘This is what we stand for, and this is what we don’t.’
Codeberg’s move is a masterclass in platform governance. They chose sustainability over purity. They understood that openness without limits isn’t openness — it’s chaos. And chaos benefits no one, least of all the projects that rely on the platform.
So why do I still regret migrating? Because I bought into the dream. I thought I’d found a home where I could do anything, as long as it was free. But that’s not a home. That’s a wilderness. And wildernesses are dangerous.
The real lesson from Codeberg is not that they betrayed free software. It’s that free software never existed. It was always a controlled community. And if you’re not the one controlling it, someone else will.
Don’t hate the platform for drawing a line. Hate yourself for believing a line wasn’t necessary. Now go build your own wall — or find one that matches your values. But don’t pretend you can live without walls.
FAQ
Q: Wasn't Codeberg supposed to be a free-software haven? How can they ban things?
A: Codeberg always had rules — they only host free software. The AI training ban closes a loophole they didn't anticipate. It's consistent with their mission to protect projects from exploitation, not a reversal.
Q: What's the practical implication for me as a developer?
A: Never assume a platform's terms are permanent. If you rely on a community-run host, have a fallback plan. The minute your use case becomes a threat to the community's sustainability, you'll be the one getting banned.
Q: Isn't this just an anti-AI move? The real story is about AI greed, not governance.
A: AI is the trigger, but the deeper issue is governance. Any platform faces the same dilemma: how to stay open while preventing abuse. Without exclusion mechanisms, every community eventually collapses under the weight of free riders and bad actors.