Conversation

Notices

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Friday, 11-Jul-2025 07:41:17 JST silverpill

   • ActivityPub for WordPress

   @activitypub.blog

   Documented support for FEP-844e.

   Cool, I'll add you to the implementation list.
   Do you have any feedback, or suggestions? This FEP is very new and probably needs refinement

   • Embed this notice
     Konstantin Obenland (obenland@mastodon.social)'s status on Friday, 11-Jul-2025 21:27:42 JST Konstantin Obenland

     in reply to

     • ActivityPub for WordPress

     @silverpill @activitypub.blog I think the main motivation for me to add it was to advertise our new support for #RFC9421. Having a proposed standardized way to do that felt neat.

     On the receiving end, I'm not sure we'd do any pre-flight requests to understand what an instance implements before acting on it, we'd probably rather stay conservative or do things like double-knock with caching, would be my guess. Might be different if it was something we could grab with a HEAD req.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 11-Jul-2025 21:27:42 JST silverpill

     in reply to

     • Konstantin Obenland
     • ActivityPub for WordPress

     @obenland @activitypub.blog

     >pre-flight requests

     This is needed for signed GET requests, right? Because when POSTing to inbox, the actor (and its capabilities) should be already known.

   • Embed this notice
     Konstantin Obenland (obenland@mastodon.social)'s status on Monday, 14-Jul-2025 08:01:03 JST Konstantin Obenland

     in reply to

     • ActivityPub for WordPress

     @silverpill @activitypub.blog `implements` is a keyword in PHP, Java, TypeScript, that some quality tools will flag if used as a variable in function signatures. It was fine in our case as a class property, but it's possible others might run into something like that.

     Maybe there are alternatives that could be considered? `supports`?

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 14-Jul-2025 08:01:03 JST silverpill

     in reply to

     • Konstantin Obenland

     @obenland I would prefer to keep implements because there are 4 or 5 implementations of this FEP already... The clash with a reserved keyword in some languages shouldn't be a big problem -- type is even more common keyword yet it is everywhere in ActivityPub.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 14-Jul-2025 08:05:02 JST silverpill

     in reply to

     • Konstantin Obenland

     @obenland I didn't realize that either, and it makes FEP-844e less attractive. However, capability discovery might still be preferable to double-knocking because RFC-9421 is not the last upgrade. Some applications are already starting to use EdDSA signatures, and that requires triple knocking. In the future we will need to switch to post-quantum cryptography and so on. The number of knocks always increases, but capability discovery requires a constant number of requests.

     #rfc9421

   • Embed this notice
     Konstantin Obenland (obenland@mastodon.social)'s status on Monday, 14-Jul-2025 08:05:03 JST Konstantin Obenland

     in reply to

     • ActivityPub for WordPress

     @silverpill @activitypub.blog Oh, I did not consider that! That's right!