Mechanisms for migration away from Bluesky PBC‑controlled core components

Determine viable mechanisms for migrating user accounts, data, and services away from Bluesky PBC‑controlled core components (the Firehose and the AppView), including how such a migration would work in practice and how network effects would affect users’ ability and willingness to switch to alternative providers.

Background

Despite the open, federated design of many components, Bluesky PBC currently operates key choke points—the Firehose and the AppView. These enable enforcement and policy control but create centralization risks.

The authors explicitly state that the process for potential migration away from these components is unclear and that network effects may hinder users from switching, identifying a concrete unresolved question about migration mechanisms.