Self-promo links below if you would like to star a few of mine good for developers.
https://gitlab.com/architecture-decision-record
Infrastructure should be neutral. Codeberg is a social club
My wishlist: free for open source and paid for closed source, able to do simple projects that are handwritten and also complex projects including AI LLM code that needs CI/CD/auditing, and hosting in the UK or EU.
Aside, I donate money to Codeberg because I think Codeberg is a wonderful service with strong commitment to free open source, and because I host some larger projects and AI projects that are for public welfare social good.
To Tangled -- it's great that the core code is MIT licensed and anyone could stand up a competing appview (the credible-exit property of atproto).
Do Tangled Labs Oy's articles include a purpose clause instead of the default profit-only purpose[0]? Or is something similar on the roadmap?
[0] OYL 1:5 reads The purpose of a company is to generate profits for the shareholders, unless otherwise provided in the Articles of Association.
You're deliberately avoiding a network effect lock-in by being federated, you make competition trivial by giving away not only the protocol but also making your code available, and you don't even restrict commercial competition by using the MIT license rather than, say, BSL.
To me that sounds like you are deliberately starting a race-to-the-bottom competition on price with, well, everyone capable of hosting a SaaS? Heck, if you don't end up with some solid competition the whole "federated code" USP doesn't play out. To me that doesn't exactly scream "good return on my €3,8M seed round". Am I missing a brilliant plan here, or should we expect a rug pull a few years down the line?
Anyone who joins the association (small fee) can vote.
So, yes, it's technically a democracy, but it deserves extra nuance in my mind because it might not be what everyone immediately thinks a democracy should feel like.
That's a fairly good starting place. Might seem innocuous, but don't forget that "far right" has no agreed upon boundary. You might as well replace it with "wrong think" at this point.
Which, again, good for them. I could care less. I left a little over a month ago once I figured out what was going on. They are perfectly allowed their fiefdom on the internet, but I would never recommend the platform to anyone as a useful Git forge unless they happen to sit in that little thought bubble.
But that's the game, I suppose. Everyone knows what's going on and they just don't care. And so I don't care about Codeberg :)
Infrastructure can never be neutral, because infrastructure is owned and costs resources to run. All infrastructure comes with rules, be they the voting consensus of some e.V. or state-run entity, the whims of an individual on their private server, or the corporate interests of something owned by a, well, corporation.
The problem isn't "neutral infrastructure". The problem is an overreliance on centralized services even though most such services are relatively easy to host yourself.
I run my own DevOps server based entirely on OSS. Is it github? No. Does it what I need it to do? Absolutely. Do I get 99.999% uptime? No, but when it's down or slow, I can fix it. When the corporate platform is down, I can only wait.
And "network effects" are not a good argument. Open Source was wildly successful long before centraliced DevOps platforms.
And in hindsight, the added friction of getting in touch with projects before being able to send them any code, was a benefit not a disadvantage. Because it acted as a barrier of entry that disincentivized alot of subpar code from hitting these projects in the first place.
Even if whoever owns and runs the infra would like that to be the case, the law of wherever they are can put restrictions on this as well.
The value these centralized services provide is the centralization itself - that makes things easy to find. Remember the web before Altavista? Finding anything was detective work, guessing domains, following links through multiple pages, digging in newsgroups, asking around, and so on.
Open source was successful, but not nearly at the same level it is now thanks to precisely platforms such as GitHub (and Launchpad, and Bitbucket, and Gitlab, etc) that added useful functionality such as bug trackers and project management on top of a version control system.
Now, if we could do something like GitHub on top of a network such as Mastodon, then we would have something that's centralized enough to be useful and distributed enough to be indestructible.
And in recent years, how is the centralized world of websearch doing?
https://www.techspot.com/news/101560-study-confirms-search-r...
> Open source was successful, but not nearly at the same level it is now thanks to precisely platforms such as GitHub (and Launchpad, and Bitbucket, and Gitlab, etc) that added useful functionality such as bug trackers and project management on top of a version control system.
None of that depends on a centralized provider. I have all the features you listed on my self-hosted platform as well.
So, relatively, not so long ago it was pretty common to host all this stuff yourself. I don't think (or maybe don't remember) Subversion having any Web interface of its own, but, since forever Git came with GitWeb. I remember configuring it for the first time: any extra bit of configuration, especially those that resulted in some added interactive functionality seemed exciting. For a week, I'd push something to my branch and immediately refresh the browser page to see my changes reflected in the remote repository :D
The infatuation wore off very quickly: after a month I have almost forgotten the Web interface even existed.
The cycle repeated with hosted services, the addition of PR interface, the addition of "pages", the bug reports, the built-in Wiki. After discovering the new gadget and associated hype, invariably, came the realization that the predating existing functionality was... better. The PR discussion in the Web page detached from the code is a lot worse than the PR discussion in the PR itself. The built-in issue tracker doesn't come close to the stand-alone product functionality. The built-in Wiki is ridiculously underwhelming when compared to an actual Wiki.
And so was the CI. For me, it started with Gitlab. There are oh so many reasons to hate Jenkins, so, whenever anyone announced an alternative platform, I'd absolutely check it out, and so did a lot of others, I presume. I was super hyped up about the possibility of running CI from the command line, completely locally on my laptop. And then it turned out to be a bait-and-switch kind of thing. I've created monumental dozen-steps and branching pipelines connecting multiple projects only to realize that the best CI is the one that uses as little as possible of the platform tools.
In the end of the day, I came to realization, that beside the social aspect of the platform like GitHub, everything that it offers on top of the essential Git repository storage is too low quality. And so do competitors. If I was ever again tasked with setting up a company code repository storage, I'd go with a physical server attached to the local office network, unless there's no office, in which case, probably, some EC2 VM would do the job...
Places like GitHub or Gitlab lure you in with their free tier offering, where you get the storage space and some other goodies for free, but once you need to upgrade to the paid tier, you inevitably realize that it's not worth the money they charge for it.
GitLab and Codeberg can absolutely become trash, each in their own way.
The solution isn't just "migrating off of GitHub"; it's "migrating to a platform that is unownable by design, not only hope".
And there are no good enough decentralized alternatives to GitHub yet.
Tangled.org's decentralization has serious holes. Radicle made an alien universe; a niche within a niche. Also, it's already having problems with ISPs: https://radicle.dev/2026/04/23/domain-move
Issues/PRs/comments are records owned by their authors, not by the repo. So an issue can span N users' PDSes. That's a neat model for social media, but a forge wants the repo to be the durable owner/context of its issues and history because that's where the comment/issue/etc. logically belongs.
The solution? tangled.org acts as a super advanced cache/aggregator for that. What can possibly go wrong?
> As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs.