Except it ain’t so easy to switch to a different BlueSky server. Here’s what ChatGPT says about it:

Migrating your Bluesky account to a different server involves several technical steps:

Account Creation on the New Server: Establish an account on the target Personal Data Server (PDS). This requires proving control over your Decentralized Identifier (DID) by generating a JSON Web Token (JWT) signed with your existing signing key.

GITHUB

Data Migration: Transfer your existing data, including posts and media, to the new server. This process entails exporting your repository as a Content Addressable aRchive (CAR) file and importing it into the new PDS. Additionally, you'll need to upload associated media blobs and migrate private settings like preferences.

GITHUB

Identity Update: Modify your DID document to reflect the new server's details, such as the endpoint and signing key. For DID

users, this involves submitting a signed operation to the PLC directory, which may require email verification and handling of cryptographic keys.

GITHUB

Finalization: Activate your account on the new server and verify the integrity of the migration. It's advisable to deactivate or delete your account on the previous server to prevent conflicts.

GITHUB

Due to the technical nature of these steps and the potential risks—such as data loss or account inaccessibility—it's recommended to proceed with caution and ensure a thorough understanding of the process before initiating a migration.