Bluesky

I've been contemplating how to make your Farcaster ID a native Bluesky ID. Perhaps this channel could be ground zero for people interested in exploring these types of integrations?

I've looked into it and it's a bit complicated, because BSky supports Secp256k1 and p256 while FC uses ed25119

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

I'm envisioning something bigger and bolder. Currently, the identity layer for Bluesky relies on W3C-based DIDs, specifically did:plc or did:web. What I’m proposing is the creation of a third option: did:fid.

This approach would allow every Faraaster ID to double as a Bluesky ID.

Why pursue this? For one, it would simplify cross-posting and ensure seamless authenticity of posts across both platforms. Additionally, it addresses a key criticism of Bluesky: the lack of censorship resistance in controlling identity keys.

Success would be achieved when the Bluesky team adopts this third DID type as part of their identity layer.

Wouldn't did:ens be the more obvious choice here?