It looks like some issues may arise if/when an instance's domain name changes. Is there any way we can change federation so that we don't need to rely on such a central point of failure?

you are viewing a single comment's thread
view the rest of the comments

[–] silverpill@mitra.social 33 points 2 days ago (2 children)

Yes, domain names can be replaced with cryptographic identifiers: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

[–] Auster@thebrainbin.org 11 points 2 days ago (2 children)

How interesting. Isn't the did: system also what AT Protocol (Bluesky) uses? 👀

[–] silverpill@mitra.social 9 points 2 days ago

That's correct.

did: prefix is used to denote cryptographic identifiers, in theory one could even take a did:plc identifier from Bluesky and then use it as identity for an ActivityPub application:

https://github.com/bluesky-social/atproto/pull/3943

[–] onlinepersona@programming.dev 3 points 2 days ago (1 children)

DIDs aren't unique to Bluesky

[–] Auster@thebrainbin.org 8 points 2 days ago

Didn't mean it was. Just mentioned it as it was the most common example I knew. But thanks for the link! Reading it now.

[–] gammaray@sh.itjust.works 6 points 2 days ago (1 children)

Thanks. This is a little complicated to wrap my head around. Is this already implemented and we just have to toggle it, or is this something that needs a special/unreleased version of lemmy in order to activate?

[–] silverpill@mitra.social 12 points 2 days ago

I doubt that it will be implemented in Lemmy, the application architecture needs to be different in order to support cryptographic identities.
But there are other implementations (they are listed near the end of the document).