yeah!! arg another thing i need to write up since repo `rev` increases monotonically, you can subscribe to multiple firehoses (even jetstream+relay in neat ways!) and aggregate the event streams into one. drop repo events with old revs and it pretty much just works :)
Apr 16, 2026 at 8:26 PM
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.
Firehose Viewer — ATProto Events
Real-time ATProto event stream from the Bluesky firehose via Jetstream
firehose.stream — ATProto jetstreams
A lightweight, filterable JSON firehose of real-time ATProto events.
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.).
Event Bridge for ActivityPub Plugin — WordPress.com
Make your events more discoverable, expand your reach effortlessly while being independent of other (commercial) platforms, and be a part of the growing decentralized web (the Fediverse). With the Event Bridge for ActivityPub Plugin for WordPress, your events can be automatically followed, aggregated and displayed across decentralized platforms like Mastodon or Gancio, without any extra work. Forget the hassle of managing multiple social media accounts just to keep your audience informed.
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
Event Bridge for ActivityPub
Integrating popular event plugins with the ActivityPub plugin.
Event Bridge for ActivityPub
Integrating popular event plugins with the ActivityPub plugin.
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.
ATproto Command Center — Live Bluesky Firehose Dashboard
Real-time event velocity, hot collections, active accounts, and content signals — streamed from Jetstream and computed entirely in your browser.
Event Aggregator
Hi there 👋 There’s no good one-stop shop to find all the various events happening in a given city, so I’m trying to build one! I’ve got a fairly basic implementation up here. At the moment, it just runs a daily cron that scrapes events from a small set of local Vancouver publications/venue websites then pushes them to a bluesky collection, which the site then fetches and uses to populate the calendar. It supports basic commenting and RSVP functionality via bluesky auth. It’s very...
i feel like having rich event embeds/blocks and more cross-compatibility could go a long way. maybe a @semble.so collection that automatically compiles all standard.site publications that link to an event??
TLDR in English Just did an automation using @airglow.run that will save me so much work from now on Every tangled repo I give a star will now be saved into my @semble.so collection for atproto-related repos, using the permanent URL
Victoria
Mal conheço o Airglow e já considero PACAS Acabei de fazer uma automação que vai me poupar um trabalhão Todo repositório do Tangled que eu dar uma estrela, vai ser automaticamente salvo numa coleção do Semble, E USANDO URL PERMANENTE (que usa DID e não handle)!!!!! airglow.run/u/vicwalker.dev.br/3ml5ixicbo…
made atproto.md awhile ago, just added some relay features. discover repos by collection and constellation backlinks. connect your agent to the /mcp to fetch records, resolve actors, discover repos and more. try it out, suggest stuff, contribute.
atproto.md — AT Protocol data as Markdown
atproto.md
