Comment by embedding-shape
2 days ago
Yeah, waiting for this too, feels like the final piece of the puzzle. Tracking issue from Codeberg + more general information about the effort around the the ecosystem:
- https://codeberg.org/forgejo/forgejo/issues/59 ("[FEAT] implement federation")
Final piece of what puzzle?
We can do big federated/distributed development with git at the project level. See the linux kernel.
If the goal is fancy UI then there are alternatives.
If the goal is to do a big multi-git with cross repo issue tracker, then that implies either:
- you're a public site for random repos like codeberg
- you're a special purpose forge and identity management is a big issue you want full control over.
IMO - For this to work, they should go with the latter and not try to offload identity into some federated scheme.
Given how slowly it progresses in Forgejo, there are better alternatives - Radicle[1] (full decentralization, not a federation) and Tangled[2] (federation).
[1] https://radicle.dev/
[2] https://tangled.org/
Man I was so excited about Tangled, until they announced they sought and got VC investments, which makes it not even worth looking into for long-term projects. I still wish them luck and hope they'll be the lonely 0.1% that can resist enshittification even during pressure from investors, but realistically my hope is fairly close to the bottom.
Radicle seems better in that regards, but instead is on top of their own cryptocurrency, which comes with its own issues.
Personally my best hope is still "real" federation across centralized services, ala ForgeFed, but ideally we can make all these approaches interoperate in the future, that would be really awesome.
Radicle is not based on crypto. The governance organization uses a DAO, but that’s not tied in with the project, only with the main dev team; it’s irrelevant to users. They had some early ideas to incentivize participation through crypto, but they abandoned it in alpha. I don’t know why this notion persists.
2 replies →