Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I still don't see the problem with Codeberg's decision. Of course they will kick projects that they don't want, just like github will kick projects they don't want. The issue isn't what is and isn't allowed, it's who allows it, as it always has been.
Of course selfhosting is one way to control it, but in Codeberg there is a process to be part of that governance, which the author didn't partake in. At which point there is nothing more to discuss, get in the governance first and then you can write a blog post about how the governance is bad, isn't aligned with you or whatever.
It's 2026. Who still expects things to be perfect with a third-party without participating ? Be part of the governance, selfhosted or not, always
The problem for me was the decision process and the piss poor way it was communicated, plain and simple. I'm absolutely fine with the decision in itself, it's their platform and they can do that if they feel like it.
But instead of voting on an single agenda point about a small TOS change in a closed members meeting and dealing with the consequences later, I would have appreciated open communication and discussion on that topic not only among the members but also the user base before making such blanket decisions. As far as I heard there wasn't even a real discussion among the members, it was just a vote on a TOS change, which was introduced and advertised by a member shortly before the meeting took place. I could be wrong on the last point, but these kinds of salami tactics or "Vereinsmeierei" in an association would make Codeberg an unreliable platform for hosting a project.
Like someone else in here has said, this time it was banning Crypto and LLMs, next time it could be Ruby on Rails (because of their ties to the racist entrepreneur DHH) or whatever TOS change makes it through their members-only voting process. Again, that's fine for Codeberg but it's not a good place for any non-member to host a project.