Those arguments are applicable to X as well, though.
1. Your username can be your website. On Bluesky, domain verification (by DNS) maps to a `did:plc` identifier – ˋAppView`s (bsky.app, the Bluesky smartphone app, etc.) only look up to plc.directory, a “database” owned by Bluesky. For your username to REALLY be your domain name, Bluesky would need to support the `did:web` kind of identifiers, which they don’t. In short, your username maps to an internal database, which is what X does too.
2. Bluesky’s basically Twitter before it needed to give money back to investors. I’d bet money that we will be seeing more broken features ten years from now when Bluesky will have to focus on how to give the money back to investors.
(Yes, I am slightly biased towards ActivityPub, even though Bluesky has better architecture.)
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).
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).
1. Your username can be your website. On Bluesky, domain verification (by DNS) maps to a `did:plc` identifier – ˋAppView`s (bsky.app, the Bluesky smartphone app, etc.) only look up to plc.directory, a “database” owned by Bluesky. For your username to REALLY be your domain name, Bluesky would need to support the `did:web` kind of identifiers, which they don’t. In short, your username maps to an internal database, which is what X does too.
2. Bluesky’s basically Twitter before it needed to give money back to investors. I’d bet money that we will be seeing more broken features ten years from now when Bluesky will have to focus on how to give the money back to investors.
(Yes, I am slightly biased towards ActivityPub, even though Bluesky has better architecture.)