Skip Navigation

Posts
6
Comments
67
Joined
3 yr. ago

  • yep a did can be anywhere even did:nostr:publickey its part of the same system

  • what by having all users exist on a centralised server? That sounds like vendor lock in which is exactly what federation was trying to avoid.

  • Due to how the fediverse works if users can be given a did so can a community. It would only migrate for services that support did but wouldn't be all to different.

  • DID already exist they are a Decentralised IDentiy (DID) it is a keypair and user data so usernames, profile, bio, and a list of accounts across different instance that allows associating post comments likes etc.

  • im lazy i used llm to write issue and post.

  • That's essentially how ATProto does it and they publish other instance actors under "also known as" in the did. that's essentially what im proposing.

  • i didn't name it that's what its called.

  • we add a did to objects and keep the id the same. supporting platforms will use did old ones will carry on using id.

    did is what ATProto uses this is a step in that direction

  • No thats the whole point of a DID. Its an existing standard that has been established to manage decentralised identity. Their exists multiple ways to handle it so a did is did:source:id where the source can be many different things blue-sky uses a group of trusted identity server, but u can use a selhosted file, the blocckchain all sorts of things. Hell u could even use bluesky u could have the same login for ATproto (bluesky) and activpub (lemmy)

  • Yeah but u cant see this comment from my .ee account

  • Nar its lagging now. Ps Can only see this cos im on a .world alt

  • Ive already go that in my video feed tubular juat slips it in next to my yt vids.

  • All of the above

  • Well peertube is struggling already so thats a valid question. Idk if they using peertube style bitorrent video delivery that might help offload the cost a little.

  • Its not big tech unless they are abusing a monopoly.