Not saying this is the future, but something like it is. All of the core decisions here are solid (pub key identities, signed events, dumb relays). There are still features that many apps will need such as tying multiple devices to an identity, abuse prevention for relay operators, etc.
“All of the core decisions here are solid (pub key identities…” I agree, except for the bit about public keys as identities. I think public key identities are a step in the right direction, but there’s still a gap between that and what the ultimate solution is going to wind up being. We need to have some layer of indirection between user identities and public keys so that users can do things like rotate keys, have mu…
Both seem to use a “signed rotation” approach. Algorand keeps your public key stable while adding metadata that your spend key has changed and links the two. Atproto similarly uses the recovery key to sign a rotation op which can regenerate your signing key, additionally readjusting the tree to preattack state (by setting prev of the rotation to the last precompromise state).
This seems like an improvement of some kind, but still leaves gaps for lost keys. Keybase style approach, or multisig social recovery may also help.