Tangled – We need a federation of forges
Tangled introduces a federated forge solution, leveraging AT Protocol, to challenge GitHub's centralized dominance amidst claims of its recent "crumbling." The project aims to decentralize code collaboration by separating Git for code transfer from the communication layer for issues and pull requests. This resonated strongly on HN, sparking discussions about GitHub's reliability, the merits of various decentralized protocols, and the practicalities of building robust, federated systems.
The Lowdown
Tangled positions itself as a critical new entry in the forge federation landscape, advocating for a decentralized approach to code collaboration in direct response to perceived instabilities and the monoculture risk associated with GitHub. The project's core philosophy centers on a distributed system that separates the Git-based code transfer from the communication and social aspects of development.
- The Centralization Problem: The article argues that while Git itself is decentralized, the reliance on single providers like GitHub creates a centralized monoculture, which is inherently fragile. It specifically highlights recent issues with GitHub as evidence of this fragility, emphasizing the risk of 90% of open-source software depending on one platform.
- Tangled's Solution: Tangled proposes to federate events across various Git servers, which it calls "knots." It utilizes the AT Protocol for the authenticated transfer of collaborative events such as issues and pull requests, along with social features like timelines, follows, and stars.
- Cross-Server Collaboration: The system is designed to allow seamless collaboration, enabling users to fork repositories and open pull requests across different Git servers, effectively modernizing the patch-over-email workflow.
- Protocol Choice: Tangled differentiates its approach by using AT Protocol for communication, contrasting it with historical methods (email), current centralized systems (GitHub's website), and other federated projects (ForgeFed's consideration of ActivityPub).
- Project Goal: The ultimate aim is to empower open-source projects to break free from monocultures while ensuring that code collaboration remains an engaging and social experience.
By leveraging the AT Protocol, Tangled offers a blueprint for a more resilient and distributed ecosystem for open-source development, seeking to mitigate the risks associated with single points of failure inherent in centralized platforms.
The Gossip
GitHub's Grumbles and Gaffes
Many commenters confirmed the article's assertion that GitHub is "crumbling," citing recent issues such as abysmal uptime (some quoting as low as 88%), security vulnerabilities like RCEs, inconsistent billing for actions, and general dissatisfaction with UX and AI spam. However, some argued that GitHub's struggles are due to exponential usage, questioning if any ideology-driven alternative could handle the same load.
Protocol Proliferation Predicament
The discussion often revolved around the classic "N+1 standards" problem, with skepticism about introducing yet another communication protocol (AT Protocol) when others like ActivityPub exist. Commenters debated the merits and limitations of AT Protocol versus ActivityPub for forge federation, with some pointing to detailed arguments from ForgeFed developers on why ActivityPub might not be suitable, while others highlighted ongoing AT Protocol developments addressing concerns like group permissions.
Federated Forge Frontiers
The concept of a federated forge sparked comparisons to existing and past decentralized solutions. Commenters inquired about BitTorrent-like approaches for Git (noting data mirroring is solved, but other forge features are not) and highlighted projects like Radicle.xyz as active, distributed forge setups. The underlying appeal of email-based collaboration for its proven longevity was also revisited as a foundational model for building federated UIs.
Capital Concerns and Centralization Creep
A significant point of contention was Tangled's venture capital funding, particularly from a crypto-focused VC (Bain Capital Crypto). Commenters expressed strong reservations, predicting an inevitable "enshittification" similar to GitHub's trajectory, and questioned whether a VC-backed project could truly deliver a decentralized, anti-monopoly solution, suggesting it would ultimately repeat the same patterns.
Naughty Nomenclature: The "Knot" Conundrum
A lighter, yet widely discussed point concerned the project's choice to name its Git servers "knots." Some commenters humorously pointed out the sexual connotation of the term within certain communities, leading to an explanation of the term's meaning in that context. The author acknowledged the unintended double entendre, opting to keep it for a bit of fun.