Amid growing unease about GitHub's recent instability, a new project called Tangled aims to restore decentralization to code collaboration. It pairs Git's immutable repository model with the AT protocol, creating a network of “knots” that can exchange issues, pull‑requests and social signals without a single controlling service.

Historically, developers have relied on two layers: Git for moving code and a separate channel—first email, then GitHub's web UI—for discussion. Projects like ForgeFed explored ActivityPub for the latter, but Tangled adopts the AT protocol to federate events directly between Git servers. This lets users fork across servers, push locally, and open pull‑requests on remote knots as easily as sending an email patch.

Authentication and identity flow through AT, which also carries invites, SSH keys, stars and follows. The underlying Git data remains untouched, meaning existing tooling and workflows continue to work. By distributing the social layer, Tangled reduces reliance on any one provider while preserving the collaborative experience developers expect.

If the open‑source ecosystem wants to avoid another monolithic outage, adopting a federated forge like Tangled offers a practical path forward. It blends proven Git mechanics with a modern, extensible communication protocol, delivering a truly distributed workflow.