We recently released Tap, a tool designed to handle the hard parts of repo synchronization, so you can focus on building your application.
Taproot - AT Protocol Explorer
Explore the AT Protocol network. Browse repositories, records, collections, PDSes, and relays. The most complete AT Protocol data explorer.
proposal: ingest repo records #282
`sh.tangled.repo` records are one of the last few records that need atprotation (2-way sync between appview/pds). this one is tricky because we want consistency between knot state, appview state and PDS state. the path forward is described below: - migration to did/rkey syntax universally: in several places, we utilize `did/repo-name` as a globally unique identifier for a repository, we should migrate this to `did/rkey`: * for the tangled appview: this means reworking our ACLs, routers and DB to use `did/rkey` or ATURI as a globally unique identifier for a repo * for knots: this means changing paths on disk to be `did/rkey`, allowing git ops to `host:did/rkey` , updating ACLs, and XRPC endpoints * for spindles: this means updating ACLs and XRPC endpoints - once this is done, we can define ingestion logic for all services in the network to pull sh.tangled.repo records * for the tangled appview, this should create/delete/update a repo pointer record * for knots: this should create-or-ignore/delete-or-ignore/update-or-ignore a repo on disk. migration of repos needs to be thought out here. * for spindles: as above - define edge-case behaviors: * when referring to repos by rkey, it is possible for clever users to create duplicate records with the same repo-name, appview routers must handle this ambiguity with a new interstitial page that offers a redirect, knots must return an error upon push/pull on ambiguous git URLs * the `knot` cli can introduce a command `backfill` or `sync` to bring knot state up to sync with the rest of the world (repos, collaborators, pubkeys, ACLs etc.).
ATOM: AT Protocol Over MoQ Transport
This document specifies how the Authenticated Transfer (AT) Protocol can leverage Media over QUIC Transport (MOQT) for efficient data synchronization across decentralized social networks. The AT Protocol's firehose event stream and repository synchronization mechanisms map naturally to MOQT's publish/subscribe model, enabling scalable relay infrastructure, priority-based delivery, and improved resilience for large-scale social data distribution. This specification addresses the challenges of the current WebSocket- based transport and demonstrates how MOQT's relay architecture, group-based caching, and multiplexed streams provide significant benefits for AT Protocol deployments at scale.
Building More Resilient Local-First Software with atproto | jakelazaroff.com
atproto has the potential to become a rock-solid replacement for the most fragile part of any local-first app: the sync server.
Compose | Taproot
Create a new AT Protocol record on your PDS. Prefill via at.new links, save drafts on your device, and publish with one click.
Compose | Taproot
Create a new AT Protocol record on your PDS. Prefill via at.new links, save drafts on your device, and publish with one click.
ATProto for distributed systems engineers - AT Protocol
AT Protocol is the tech developed at Bluesky for open social networking. In this article we're going to explore AT Proto from the perspective of distributed backend engineering.
at://alternatives | AT protocol alternatives for popular products
Discover AT Protocol alternatives for popular products and services. Browse decentralized apps that give you control over your data, identity, and social connections.
Relay Directory | Taproot
Browse AT Protocol relay servers. View relay details, subscriber counts, and event volumes across the network.
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
ATProto Garden
A curated directory of apps, tools, and libraries built on the AT Protocol
AT Protocol
Tap into the event stream for all public activity. Build feeds, bots, search engines, and applications using live activity. No API key required.
A Markdown Editor on AT Protocol — Diffdown
Diffdown — collaborative markdown editing on AT Protocol.
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.
ATProto Architecture
Visual summary of the AT Protocol architecture: PDS, AppView, identity, records, lexicons.
