@jack ah okay, which addresses my original objection to even considering the Bluesky-built identity layer.

Seeing that underpinning this DID effort with a distributed datastore/ledger seems pretty far off -- I suppose this is a reasonable 3rd way.

Thanks for catching me up.

(cc: @plexus )

@jack I thought the whole thing about DIDs was that anyone can set up a resolver for whatever set of methods they want? And anyone can make a method? Why does IETF need to be involved?

Or you mean "too much centralization" around designing the did:plc?

RE: biz models - since Yorba has all your classical accounts, we really wanted a non-lockin ID as a differentiator. Also to help people keep track of different login types across services. Hence the DID interest.

(cc: @plexus )

@plexus On one hand, identity is really hard. So I understand why this isn't seriously addressed in the fediverse.

On the other hand, it would be great if there was something like `finger` that just had bio information and that could be the source of identity across the fediverse.

But who would really want to host fedID? There's no strong social or business case for it. And the downsides are immense.