Sort of.

I like to insist that the PLC Directory collects and distributes updates to highlight how it's different from a database. The latest state of the account is signed by the key that created it, or by a key that succeeded it. The directory can't inject any values, it's just a low-complexity solution for data availability: the "how do I learn about updates" part.

It could decide to hide/reject updates, but then it could just as well be forked and replaced if it did that. If downstream applications decide to get their account updates somewhere else, that's the directory now, without any loss of continuity for the accounts.

You don't get that from a simple database.

One could argue domain registrations, and so did:web, are more of a database controlled by a (large, international) organization than PLC. Plenty of tradeoffs of course.

Data flow: all the internet's creators ----> Jack Dorsey ----> all the internet's consumers

We're all watching the first step of enshittification and thinking "this is fine"

one of the other feature of PLC compared to did:web is that it presents the identity history, but this is also problematic for some people (dead naming and right to be forgotten)

I believe there is work around did web for an extension that would enable verifiable history

IMO perfect is the enemy of good here. If your personal email account you use for literally everything is firstname.lastname@mailprovider then you're already in the same situation. This isn't any worse, but it is strictly better.

You can always create a new identity, I don't think anything has changed there. If you don't want your new identity connected to your old identity, then don't.

The right to be forgotten is whole separate problem. The only hope here, really, is that entropy takes care of it for you. I don't see how a chain of trust system can fundamentally be compatible with the right to be forgotten unless you relax the rules a bit.

Nobody owns a domain name. You rent it, subject to the whims of the registry. Miss a single payment and you loose it forever. Even if you always pay up on time, despite price rises etc, they can still decide to take it away: https://neil.fraser.name/news/2026/09/03/

PLC is imperfect, like every solution to identity so far, but it's a lot better (in terms of ownership / control of your own ID) than DNS.

I think ENS basically solved this already. Turns out nobody really cares about the problem much.

The problem with ENS is only Brave and Opera support it. That's less that 5% of users. If Chrome had a way to add custom domain resolvers in extensions it would be a lot more useful because you wouldn't need to tell people they have to install a whole new browser.

I guess that is technically correct, but I'm not sure that's a weakness of the underlying protocol

Permanent human-readable names are subject to squatting. Who owns microsoft.eth? I bet it's not Microsoft.

Doesn't did:web suffer from the same flaw as e-mail on your own domain - not being able to actually own a domain?

it's a shame the way handshake and crypto went, that was an actually great use for blockchain