Reference implementation of the AT Protocol, a decentralized social networking protocol, including the Bluesky microblogging backend.
AT Protocol is a decentralized social media protocol developed by Bluesky Social PBC, providing a framework for building open, federated social networking applications. It includes the reference implementation in TypeScript and the backend for the Bluesky microblogging service, enabling data portability and interoperability across platforms.
Developers and organizations interested in building decentralized social applications, self-hosting social networking services, or contributing to the AT Protocol ecosystem.
It offers a fully open-source, self-hostable alternative to centralized social platforms, with a modular architecture, clear specifications, and tools for seamless third-party integration without vendor lock-in.
Social networking technology created by Bluesky
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The implementation is split into focused npm packages like @atproto/api for client libraries and @atproto/xrpc-server for server-side APIs, allowing developers to selectively integrate components.
Includes Personal Data Server (PDS) and AppView services with self-hosting instructions, enabling full data ownership and federation control, as highlighted in the README's service descriptions.
Uses the Lexicon schema language for API definitions, similar to OpenAPI, with canonical lexicons for interoperability, ensuring consistent protocol adherence across implementations.
Serves as the canonical TypeScript implementation for AT Protocol, providing a reliable base for developers and including interoperability tests to verify cross-language compatibility.
Requires Node.js 18, pnpm, Docker, and jq for the local environment, per the Quickstart, creating a steep barrier to entry for rapid prototyping or teams with limited infrastructure.
Contribution guidelines state that issues may not receive responses and build support is not provided, indicating potential gaps in assistance for developers facing implementation hurdles.
Involves advanced concepts like decentralized identifiers (DIDs), self-authenticating data structures, and federation, demanding significant prior knowledge beyond typical web development.