Continuing the discussion from Requesting expanded reasoning for Domains :
Maybe it’s considered a subset/superset of Domains (2) and (3) in the Summer of Protocols 2024, but I’m very surprised to not find a clearer call to action for identity in this initiative.
Self-sovereign identity has yet to properly materialize, yet it is at the root of so many of our digital communication woes.
Federated(++) protocols like ATproto, ActivityPub and Matrix all depend on a form of decentralized identity in order to adequately support account portability and server agnosticism as prerequisites for credible exit .
So far only ATproto/Bluesky has a working implementation, though they haven’t yet figured out how to truly decentralize it:
# Account Migration
### ⚠️ Warning ⚠️ ️
Account migration is a potentially destructive operation. Part of the operation involves signing away your old PDS's ability to make updates to your DID. If something goes wrong, you could be permanently locked out of your account, and Bluesky will not be able to help you recover it.
Therefore, we do not recommend migrating your primary account yet. And we specifically recommend _against_ migrating your main account if you do not understand how PLC operations work.
As well, the Bluesky PDS is not currently accepting incoming migrations (it will in the future). Therefore this is currently a one-way street. If you migrate off of `bsky.social`, _you will not be able to return_. However, you will be able to migrate between other PDSs.
Account Migration occurs in 4 main steps:
- Creating an account on the new PDS
- Migrating data from the old PDS to the new PDS
- Updating identity to point to the new PDS
- Finalizing the migration
### Creating an Account
show original
The Path to Decentralized Identity in ActivityPub is quite clear, but there’s still a lack of a concerted effort to get there:
hey all, was wondering, is anyone still actively working on #nomadicidentity for the fediverse? My interest in nomadic identity is somewhat inspired by scuttlebutt: to allow for migrating an account between servers, without needing the consent of...
Reading time: 16 mins 🕑
Likes: 84 ❤
The how is well on its way to being completed already:
matrix-org:main ← devonh:cryptoIDs
opened 06:17PM - 15 Nov 23 UTC
[Rendered](https://github.com/devonh/matrix-spec-proposals/blob/cryptoIDs/propos… als/4080-cryptographic-identities.md)
But the Matrix team has had to downsize, leaving this development hanging indefinitely. That is in spite of an obvious need for portable identity to solve fundamental UX issues in the Matrix experience .
I’ve encouraged the drafter(s) of this MSC (Matrix-speak for RFC) to consider applying for your grant.
2 Likes