Real Account Portability: Move your entire account – posts, comments, followers – to any new instance seamlessly. Your identity travels with you.

This is nice in theory but comes with edge cases that are hard to account for. Like, what if you have a post and your new instance defeds the instance the post's community is on? You either have to allow banned content onto the instance or the user loses data, neither of which are acceptable.

This is part of why ATProto's decoupling of user data from app logic is kinda genius and the direction we should go in if we want portable actors in Lemmy/thredi.

Full Fediverse Compatibility: We can add DIDs to Lemmy while staying fully interoperable with Mastodon, Kbin, and all other ActivityPub platforms. No breaking changes, just a powerful upgrade.

Not really, every fediverse platform that people use expects an Object's id to be a https URI it can just fetch the resource from. This is part of why FEP-ef61 specifies a way of translating a DID to a https URI. That's not to mention that moving existing actors from their current ID to a DID will cause all sorts of interop problems.

Edit: Also, is this AI-generated? It has all the tells of Gemini output, especially the the issue on Github.

fep/fep/ef61/fep-ef61.md at main

fep - Fediverse Enhancement Proposals

^Codeberg.org

joinfediverse.wiki/Nomadic_ide…

As far as I can tell Hubzilla seems to do it by having alts on different instances and then having a way to associate them with each other, so every instance knows that all the alts they're the same user. It's a bit clunky but it avoids as many fundamental changes to ActivityPub because most things under the hood are the same as without nomadic identity and the UI just treats several actors as the same user.

It will probably need it's own RFC but let's hear from the devs if they want to do it. (In my experience it's hard to push through the desired change)

You will have better time trying to implement this in piefed

DIDs are cool and all but I would trash your proposal because that is clearly llm bullshit. Put effort into it, seriously.

Oh and also, for big changes like these, you need to make a new RFC: github.com/LemmyNet/rfcs

GitHub - LemmyNet/rfcs: Requests for comment for changes to Lemmy

Requests for comment for changes to Lemmy. Contribute to LemmyNet/rfcs development by creating an account on GitHub.

^GitHub

FEP-ef61: Portable Objects describes how to use DIDs with ActivityPub. Here's a slightly less technical introduction: codeberg.org/ap-next/ap-next/s…

It's not easy, though. Adding this feature to an existing project will require a lot of work, especially if you don't want to share signing keys with servers. This was discussed in #3100, Lemmy devs are not opposed to FEP-ef61, but they don't plan to work on it.

Also, I don't recommend copying solutions from ATProto, their did:plc and did:web are not really "decentralized".

fep/fep/ef61/fep-ef61.md at main

fep - Fediverse Enhancement Proposals

^Codeberg.org

Whelp here I go again

Why not GPG!!??

I've been working on my own idea for what the "fediverse" should be, I'm calling it userless because I want to avoid users in the database and I wanna use GPG as the individuals identity because it already exists and can yes perfectly verify for me who created a post, I'm not sure why we need more than that.

I haven't flushed the whole thing out yet and I plan to hand write proper docs for the protocol.

But GPG has been around since forever. I've been told that it's too hard to use, it's insecure, it's too old. And when I use the thing I just don't agree, there is nothing technically wrong with the product like it should be way more popular.