Conversation

Notices

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Monday, 20-Nov-2023 04:13:01 JST silverpill

   • arcanicanis

   @h @arcanicanis One way to mark object transient is to use different URI scheme like urn:uuid: instead of did: for its ID.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 20-Nov-2023 06:48:44 JST silverpill

     in reply to

     • arcanicanis

     @arcanicanis @h

     DID URLs are allowed by DID spec.

     did:key doesn't support DID URLs though. I think we can simply create a new DID method based on did:key (did:fedi?) where resolution of DID URLs will be specified (and other stuff like processing of hosts query parameter).

   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Monday, 20-Nov-2023 06:48:45 JST arcanicanis

     in reply to

     Additionally, if we’re to use the did:key scheme (or whichever), but end up treating it like a sorta-URL, it might actually be worth having a different scheme ID for referencing objects ‘grouped under’ that DID, because otherwise it’s stretching that scheme outside of it’s original use (being an identifier meant for representing a public key, but now also acting as a sorta-URL too)

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 24-Nov-2023 03:52:32 JST silverpill

     in reply to

     • arcanicanis

     @arcanicanis @h

     >did:fedi

     I started to write a more detailed description of DID-based ActivityPub:

     https://codeberg.org/silverpill/feps/src/branch/main/ef61/fep-ef61.md