This might be one of the closest things I've seen to actually being able to own your account - instead of having it not just owned by a second party in every way that matters, but also beholden to a third party via an e-mail or a phone number you can't possibly own in any meaningful way.
That's pretty important in a world where the likes of Google can and will just reject your attempt to log in with a valid password on the grounds of "we don't like you", and force you to "confirm" yourself using a phone number that's defunct since 2009.
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.
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.
atproto is currently permissionless world readable, that seems worse to most people (I asked low 100s) than being in a siloed platform with some amount of control over who can see their content
oh, maybe you mean Sam Altman's World with their eye scanning for identity, that is quite dystopian
That's pretty important in a world where the likes of Google can and will just reject your attempt to log in with a valid password on the grounds of "we don't like you", and force you to "confirm" yourself using a phone number that's defunct since 2009.
The issue is, as often is the case, adoption.
The PLC makes it easy for Bluesky to be a custodian and onboard new users
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.
We're all watching the first step of enshittification and thinking "this is fine"
I believe there is work around did web for an extension that would enable verifiable history
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.
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.
oh, maybe you mean Sam Altman's World with their eye scanning for identity, that is quite dystopian