• 3 Posts
  • 83 Comments
Joined 8 months ago
cake
Cake day: January 7th, 2026

help-circle





  • There are levels to this. For sure, if we could automatically block instances with open signups and no manual verification, the worst of the worst would be eliminated and we could start with that. In fact I believe the author has a project of creating a larger-scale network of instances more or less like that, called Pangea.

    The nice thing is that however strict you want to be, there’s a chance the same tools will be needed anyway, up to you to configure, and this is what Pelago does. No matter what you do with it, it becomes more useful to everyone and I like that. Doing what you’re proposing helps those with stricter rules and vice versa !





  • 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









  • In a roundabout way the author says that the structure of the platform informs the structure of the discourse, the opinions, the information that is surfaced and the one that is invizibilized. It’s important to remember that a decentralized network doesn’t mean neutrality, there will be something put in front. It’s not the same as what a capitalist wants, and that’s good