Scott's Code Journal

2025-02-04 10:50:31

scott@codejournal.dev

I just had an interesting thought. There is a push towards using Decentralized IDs for user accounts. Bluesky uses DIDs to identify accounts. Hubzilla and (streams) have an internal hash generated from the user's cryptographic keys that serves as a DID.

Could Hubzilla and (streams) generate its own DID based on this information, and then include the DID over ActivityPub?

DID's issued by Bluesky would be: did:plc:12345

Whereas DID's issued by Hubzilla or (streams) or Forte would be: did:nomad:12345

If someone moved to another compatible server, they would keep their DID.

#fep @silverpill @Mike Macgirvin 🖥️ @Mario Vavti You know this stuff better than I do. Would something like that be useful?

show all 4 comments

2025-02-04 12:10:50

silverpill

silverpill@mitra.social

@scott Streams and Forte use DIDs for ActivityPub nomadic identity (they implement FEP-ef61). I am not sure if adding DIDs to Nomad makes sense, but generally, public-key-hash DIDs do exist.

2025-02-04 12:30:20

silverpill

silverpill@mitra.social

@scott

did:pkh for example (it was designed for cryptocurrency addresses, but a similar DID method can be created for other use cases)

2025-02-04 16:49:26

Scott M. Stolz

scott@loves.tech

@silverpill Nice. So it sounds like it was already implemented in (streams) and Forte, but it is called did:key instead of did:nomad. Once again, Mike is amazing and is the first to implement.