Package backfill provides a concurrent engine for downloading and processing all repositories from an ATProto relay or PDS.
GitHub - FiloSottile/bsky-backup-template: Template repository for setting up a new ATProto repository backup using GitHub Actions.
Template repository for setting up a new ATProto repository backup using GitHub Actions. - FiloSottile/bsky-backup-template
Atproto for distributed systems engineers - AT Protocol
In this article we're going to explore atproto from the perspective of distributed backend engineering.
Introducing Tap: Repository Synchronization Made Simple | Bluesky
Just about every app built on AT needs data from a repository at some point. For many use cases – feed generators, labelers, bots – streaming live data through a Relay or Jetstream works well. But some applications need to go beyond what Jetstream was designed for, like tracking specific subsets of a repo, automatically backfilling a database when adding new repos to monitor, or even mirroring the entire Atmosphere.
com.atproto.repo.listRecords | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
Drips | Fund Open Source In Your Ecosystem
Drips is the easiest way to fund Open Source in your ecosystem. Fund your dependencies with built-in dependency splitting, run RetroPGF rounds, and achieve any
Atmosphere MCP · aturi.to
A keyless, read-only MCP server for atproto, in beta: 38 tools that let an AI agent resolve any Atmosphere link, read any repository, trace backlinks across every app, and sample Jetstream, the live event stream.
random atproto sync notes - for whole-network backfill, you have to spread your `getRepo` requests across PDS hosts to get reasonable throughput, so it's a scheduling problem. it's also a spec-SHOULD to make these requests directly to your upstream (not PDSes directly) and follow its redirects.
_very_ alpha, but I've been messing with an atproto backfill/sync solution built on @cloudflare.social — currently has a couple caveats, and needs some work and docs, but the bones are there
GitHub - estrattonbailey/slipstream: Slipstream is a syncing and ingestion pipeline for atproto, built on Cloudflare.
github.com_very_ alpha, but I've been messing with an atproto backfill/sync solution built on @cloudflare.social — currently has a couple caveats, and needs some work and docs, but the bones are there
GitHub - estrattonbailey/slipstream: Slipstream is a syncing and ingestion pipeline for atproto, built on Cloudflare.
github.com
