Conversation

Notices

1. Embed this notice
   bengo (bengo@mastodon.social)'s status on Thursday, 17-Oct-2024 06:57:52 JST bengo

   • ilja

   @ilja ya! Good rec. I've been following it. Personally I don't love a new custom URI scheme vs just using did:, but on the whole it's a great contribution

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 17-Oct-2024 06:57:52 JST silverpill

     in reply to

     • ilja

     @bengo did: is not suitable because not all DID methods support DID URL syntax (for example did:key). In earlier versions of FEP-ef61, a wrapper DID method was used (e.g. did:ap:key:...) that could augment any DID method with DID URL capabilities, but implementation experience showed that ap URLs are easier to work with. They also better fit into origin-based security model used in vanilla ActivityPub.

     @ilja

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 17-Oct-2024 07:34:27 JST silverpill

     in reply to

     • ilja
     • silverpill

     @bengo

     >Identity/Authenticity/Data Decoupling

     In this section you're basically describing FEP-ef61. Do you know that implementations already exist?

     @ilja

   • Embed this notice
     bengo (bengo@mastodon.social)'s status on Thursday, 17-Oct-2024 18:41:07 JST bengo

     in reply to

     • ilja
     • silverpill

     @silverpill @ilja what's a good client i can download to create posts/URIs that conform to FEP-ef61?

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 17-Oct-2024 18:41:07 JST silverpill

     in reply to

     • ilja

     @bengo

     streams, a combined server-client by @mikedev

     The "decoupled client" is a subject of another proposal, FEP-ae97 (it's based on FEP-ef61). I made a simple command line client (https://codeberg.org/silverpill/fep-ae97-client), and implemented server-side C2S API in Mitra.

     @ilja