We have a number of protocol and infrastructure changes rolling out in the next three months, and want to keep everybody in the loop.
This update was also emailed to the developer mailing list, which you can subscribe to here.
- As of this week, the Bluesky AppView instance now consumes from a Bluesky BGS, instead of directly from the PDS. Devs can access the current streaming API at
https://bsky.network/xrpc/com.atproto.sync.subscribeReposor for WebSocket directly, wss://bsky.network/xrpc/com.atproto.sync.subscribeRepos
Your existing cursor for bsky.social will not be in sync with bsky.network, so check the live stream first to grab a recent seq before connecting!
- We are updating the DID document public key syntax to “Multikey” format next week on the main network PLC directory (
plc.directory). This change is already live on the sandbox PLC directory.
How will this affect me?
- For today, if you're consuming the firehose, grab a new cursor from
bsky.networkand restart your firehose consumer pointed at
The Bluesky services themselves are moving to a federated deployment, with multiple Bluesky (the company) PDS instances aggregated by a BGS, and the AppView downstream of that. As of yesterday, the Bluesky Appview instance (
api.bsky.app) consumes from a Bluesky PBC BGS (
bsky.network), which consumes from the Bluesky PDS (
bsky.social). Until now, the AppView consumed directly from the PDS.
How close are we to federation?
Technically, the main network BGS could start consuming from independent PDS instances today, the same as the sandbox BGS does. We have configured it not to do so until we finish implementing some more details, and do our own round of security hardening. If you want to bang on the BGS implementation (written in Go, code in the indigo github repository), please do so in the sandbox environment, not the main network.
This change impacts devs in two ways:
- In the next couple weeks, new Bluesky (company) PDS instances will appear in the main network. Our plan is to optionally abstract this away for most client developers, so they can continue to connect to
bsky.socialas a virtual PDS. But the actual PDS hostnames will be distinct and will show up in DID documents.
- Firehose consumers (feed generators, mirrors, metrics dashboards, etc) will need to switch over and consume from the BGS instead of the PDS directly. If they do not, they will miss content from the new (Bluesky) PDS instances.
The firehose subscription endpoint, which works as of today, is
wss:// for WebSocket directly). Note that this endpoint has different sequence numbers. When switching over, we recommend folks consume from both the BGS and PDS for a period to ensure no events are lost, or to scroll back the BGS cursor to ensure there is reasonable overlap in streams.
We encourage developers and operators to switch to the BGS firehose sooner than later.
DID Document Formatting Changes
We also want to remind folks that we are planning to update the DID document public key syntax to “Multikey” format next week on the main network PLC directory (
plc.directory). These changes are described here, with example documents for testing, and are live now on the sandbox PLC directory.