It is not just UX, if the plc directory censors your operations, you are screwed, and then people say oh but we can detect that and start using another registery, as if this is viable in practice, as if we couldn't in theory use a separate root servers than ICANN.
did:plc is a shitcoin. Let me explain to you why.
On #Nostr, your public key is your user ID. On #Bluesky, although you have a public key, your real user ID is a did:plc.
To generate a did:plc, you must make a POST request to https://plc.directory/
Yes, https://plc.directory/ (the literal URL) is part of the protocol definition. They'll say it's not, but it is.
They'll say it's not, because theoretically you could run multiple plc.directory servers, and people could point at different ones. But there are big challenges around security and UX of that, and let's be real, Bluesky never intends to "fix" it (it's not broken).
Now, if we just put the whole thing on a blockchain that would totally solve that problem. But in fact, did:plc "does not make use of any blockchain". Because the accepted decentralized way to achieve this _would_ be to put it on a blockchain, so they had to make that qualifying statement against it.
So, they needed to use a blockchain, but they don't want to use a blockchain. So they invented their own blockchain: a regular webserver!
And they pretended their regular webserver was a blockchain. And this, is why did:plc is a shitcoin.
Discussion
No replies yet.