Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 03:36:24 JST Alex Gleason
   Was reconsidering whether I should add ActivityPub support directly to Ditto, vs having a separate self-hosted bridge service that can integrate. But now I'm thinking what if we do it and just go straight to FEP-ef61: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 03:42:44 JST Alex Gleason

     in reply to

     • silverpill
     @silverpill have you actually implemented this in Mitra already?
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 13-Jan-2024 04:12:32 JST silverpill

     in reply to

     @alex Not yet.

     But what I'm planning to do is similar to what you're doing in Ditto (if I understand it correctly).

     - Client interacts with the server using Mastodon API.
     - When the user performs some action, the server creates an activity and sends it to the client.
     - Client signs the activity and sends it to outbox (per FEP-ae97).

     So, I think implementing FEP-ef61 in Ditto may make sense.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 04:15:13 JST Alex Gleason

     in reply to

     • silverpill
     @silverpill This will be interesting.
     
     I think I can even use the Nostr keypair directly: https://w3c-ccg.github.io/did-method-key/#secp256k1
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 04:16:48 JST Alex Gleason

     in reply to

     • silverpill
     @silverpill @ottman We're going to make the portable objects thing happen.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 13-Jan-2024 04:26:58 JST silverpill

     in reply to

     @alex Yes, it should be possible. Fediverse projects will likely end up using Ed25519 keys, but with FEP-ef61 it is easy to support many different types of keys and signature algorithms.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 04:28:49 JST Alex Gleason

     in reply to

     • silverpill
     @silverpill We have to push for this. Mastodon will never implement it, so everybody else has to.
     Sexy Moon likes this.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 13-Jan-2024 05:02:42 JST silverpill

     in reply to

     @alex Many Mastodon users want data portability, so I wouldn't rule that out. But even if Mastodon devs will implement it, they certainly won't be the first.

     Right now FEP-ef61 is just an idea. Some parts are not quite elegant, (especially inbox discovery), W3C standards which FEP-ef61 is based upon are unstable, likely this proposal is not compatible with JSON-LD... So there's a lot of work to do (and your input is welcome!).

     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 13-Jan-2024 10:49:04 JST Alex Gleason

     in reply to

     • arcanicanis
     • silverpill
     @arcanicanis @silverpill I don't think that much thought was put into it. It's the same curve as Bitcoin. It works well enough for Bitcoin, where actual money is at stake, so it couldn't be a bad choice for shitposting. Even if others may possibly be better.
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Saturday, 13-Jan-2024 10:49:11 JST arcanicanis

     in reply to

     • silverpill

     Wait, secp256k1 (as in Koblitz curve, as used in Bitcoin/Ethereum, only meant for a specific narrow use and supposedly has much more ways to be easily misused, making key compromise easier) versus P-256 (secp256r1) or the much simpler/performant Curve25519? Was there a reason for adopting specifically secp256k1 in Nostr above all others?