The AT Protocol supports it (in the “standard”), but Bluesky itself doesn’t, at least not yet. Let’s say you are the owner of the example.org domain, and would

The AT Protocol supports it (in the “standard”), but Bluesky itself doesn’t, at least not yet. Let’s say you are the owner of the example.org domain, and would like to federate your content to the Bluesky servers. The Bluesky servers are currently unable to make use of a `did:web:example.org` DID (that would induce a request to https://example.org/.well-known/did.json https://example.org/.well-known/did.json). All you can do is tell all the Bluesky AppViews that your @example.org nickname is an alias to your `did:plc` in Bluesky’s plc.directory “database”. So it’s just a local mapping between a domain and an account, that’s somehow secured by a DNS verification (but non-techies don’t know it, and someone on X could very well make use of your domain as a local nickname too). I would appreciate being proven wrong, though!