That's where I feel ATproto strikes the right balance: it's basically “What if Nostr but the identity lives on a potentially-self-hostable server instead of the client?”, avoiding that risk of “oh no I lost my private key” while still providing the means to control where one's identity lives and move elsewhere if necessary (even if the current server is uncooperative or no longer exists).

▲

BinaryIgor 5 days ago | parent [-]

Isn't it centralized though, thus defeating the whole purpose?

	▲	yellowapple 3 days ago \| parent [-]
		That depends on what “centralized” means (i.e. whether we're conflating “decentralized” with “federated”, as is usually the case when talking about systems like ATproto, ActivityPub, Nostr, etc.). In any case, AFAICT it's possible to self-host every part of the ATproto stack, and people have indeed done that. Third-party PDSes, relays, and applications/clients can talk to one another and with the ones Bluesky PBC operates. That satisfies the meaning of “decentralized” as most people use it (at least as well as other federated protocols like ActivityPub and email satisfy it).