Bluesky launches Protocol Services with Jetstream v2 network replay
Bluesky Protocol Services
Bluesky has launched Bluesky Protocol Services, a new brand and website for the public infrastructure it operates on the AT Protocol. The headline feature is Jetstream v2, which adds Network Replay: developers can now backfill historical data from a compressed archive via HTTP, then seamlessly switch to the live WebSocket stream. This stateless replay requires an API token for archive requests, while the live tail remains open. The company also released new TypeScript and Go SDKs for Jetstream, rebuilt the Bluesky TypeScript SDK on @atproto/lex, and updated the HTTP reference. All infrastructure is open source and self-hostable.
Replay is stateless on the server, with no per-consumer cursor, no subscription to register, and nothing to stage on the client.
- simonw
The original Jetstream is really cool - it's incredibly easy to start consuming the Bluesky firehose - you don't even need to use a server, you can consume it directly in the browser.
I updated my browser demo to use the new Jetstream just now - hit "connect" and scroll down the page to see the events flowing past: https://tools.simonwillison.net/bluesky-firehose
- walrus01
Sort of on a tangent to the actual content of the page, but what documentation system/CMS is this particular web page UI? It seems very fast and relatively uncluttered for the menu on the left side, content pane, top horizontal menu bar.
- josephg
I wonder if it would be a good idea to remake DNS on top of bluesky. The basic idea is that, if you own a domain name, you post DNS updates in a bluesky feed. The firehose itself is authoritative. DNS servers sit downstream of the firehose. All the updates to domain names get written into a database, and they essentially just respond to queries hitting that database. This would let anyone (with enough bandwidth) run a fast domain name server.
We could use this to fix some of DNS's long running problems. Like, we could add upstream cryptographic signatures to DNS records. And put TLS certificates in there too. We might be able to ditch TTL entries. In a DNS server, records should update via server-push from the firehose. You shouldn't have to wait for TTL to expire.
I think it'd make a nice little system.
- ChrisArchitect
I'm all for whatever atproto expansion and whatever's going on here, mainly it harks back to early Twitter days (tho also for better or worse, watching them build Bluesky in realtime isn't the best), but when they have outages like last week a good chunk of service unreachable/down for many hours with little update on https://status.bsky.app/ and then whatever history just basically disappears as if nothing ever goes wrong, it's not a good vibe.
Despite all the openness and github repos and what not it's very difficult to get straight answers or just like find a place where issues or changes to the platform are addressed easily.
- ChrisArchitect
Suppose this would be an example of what they meant by 'expands beyond the app'
Related:
Bluesky's active user base is shrinking as its focus expands beyond the app