Conversation

Notices

1. silverpill (silverpill@mitra.social)'s status on Friday, 15-Mar-2024 07:02:38 JST silverpill

   @mikedev The path can be different, for example it can be /ap/ instead of /.well-known/apresolver/.

   Though with /.well-known/apresolver we can be sure that it is not used by any existing AP server.

   • silverpill (silverpill@mitra.social)'s status on Friday, 15-Mar-2024 07:35:49 JST silverpill

     in reply to

     • marius

     @mariusor @mikedev webfinger adds a layer of indirection, ObjectID -> JRD -> Object

     However, there's a proposal to allow skipping JRD: https://socialhub.activitypub.rocks/t/using-webfinger-to-resolve-the-actor-for-an-acct-without-parsing-for-a-self-link/3941

     I would still prefer a separate resolver endpoint because DID URLs don't need to be URL-encoded in this case and the resulting HTTP(S) URL is shorter. (By the way, the term 'resolver' was borrowed from "Decentralized Identifier Resolution (DID Resolution) v0.3" specification https://w3c-ccg.github.io/did-resolution/)

   • marius (mariusor@metalhead.club)'s status on Friday, 15-Mar-2024 07:35:50 JST marius

     in reply to

     @silverpill is there a reason why the did can't be a resource for a regular webfinger request?

     /.well-known/webfinger?resource=did:ap:key:z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2/path/to/object
     @mikedev