thearchivist.funBluesky opens federation to self-hosted data servers
On 22 February 2024, Bluesky announced that its network was opening to federation, initially with a release intended for self-hosters. People with the necessary technical knowledge could operate a personal data server instead of relying exclusively on the company's hosting. The announcement described this as a step toward a social web in which account data and application choices were less tightly bound to a single provider. AT Protocol separates several responsibilities that a conventional social platform often combines. Personal data servers hold account repositories, relays aggregate network data, application views support particular experiences, and feed or moderation services can add further layers. The distinction matters because decentralization is not a single switch. Different parts of a working network can have different operators, resource needs and degrees of concentration. Bluesky's explanation emphasized account portability and the ability to change hosting without necessarily abandoning the social identity built around an account. That is a design goal with practical implementation requirements, not a promise that every migration will be effortless. A host still needs maintenance, security and availability, while applications must support the protocol's identity and repository mechanisms correctly. For researchers, the event provides a useful alternative to studying social media only as a set of company-owned websites. A public conversation can be understood as records moving through a stack of services. When archiving it, identify the original record, the account identifier and the application through which it was observed. A rendered post is one view of that underlying data. The February release marked an operational opening of the network, while subsequent tooling and policy developments continued to determine how accessible that opening was to ordinary users.
Context and provenance
Read this alongside ActivityPub rather than assuming the two protocols are interchangeable. Both support communication beyond one host, but their mechanisms for identity, distribution and moderation differ. The comparison becomes useful when framed around concrete tasks: move an account, find an old post, follow a conversation or change a moderation layer. Ask which component performs each task and what remains dependent on a central service. This keeps a research note precise enough to survive changing product language. It also separates the existence of an open protocol from the experience of running or using a particular implementation.
Why it matters
Federation made independent data hosting part of the production network and exposed the distinct layers behind a social application.
Sources and evidence
Editorial review: 2026-09-23. New evidence may change this account.