🔄Bluesky Launches Jetstream v2 With Network Replay
Catch up on missed network events with ease
TL;DR
Bluesky launches Jetstream v2, introducing network replay to catch up from any point in the past. No per-consumer cursor or subscription needed; just an API token for archive requests.
Bluesky has launched Jetstream v2 with a new feature: network replay. This allows developers to catch up on missed events from any point in time without needing a persistent connection, making it easier to integrate and manage real-time data streams. If you're building applications that rely heavily on real-time updates but struggle with reconnection issues or missed events, Jetstream v2's replay capability is a game-changer. The service now includes two live instances at wss://jetstream.us-west.bsky.network and wss://jetstream.us-east.bsky.network, plus SDKs in TypeScript and Go for easier integration.
Key Points
Jetstream v2 instances are live at wss://jetstream.us-west.bsky.network and wss://jetstream.us-east.bsky.network
SDKs in TypeScript (npm) and Go (Jetstream project) provide common glue code for reconnecting, deduping, cursor management, and decoding events
Network replay is stateless on the server with no per-consumer cursor or subscription required; just an API token for archive requests
Bluesky Protocol Services website organizes documentation for developers to build on AT Protocol network
Jetstream v2 includes full request and response schemas, updated HTTP reference, and new endpoints
Why It Matters
If you're building real-time applications that need to catch up from any point in time without persistent connections, Jetstream v2's replay capability is a must-have. The stateless nature of the server means no per-consumer cursor or subscription is required, simplifying integration and reducing overhead. However, smaller projects may find the API token requirement for archive requests adds complexity.
Frequently Asked Questions
Why does this matter?
If you're building real-time applications that need to catch up from any point in time without persistent connections, Jetstream v2's replay capability is a must-have. The stateless nature of the server means no per-consumer cursor or subscription is required, simplifying integration and reducing overhead. However, smaller projects may find the API token requirement for archive requests adds complexity.
What happened?
Bluesky launches Jetstream v2, introducing network replay to catch up from any point in the past. No per-consumer cursor or subscription needed; just an API token for archive requests.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 2,975 builders reading daily.