Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 26-Nov-2024 00:47:29 JST Christine Lemmer-Webber

   I think the "quadratic at scale" concern is the one thing I failed to share from my summary thread of the differences between "shared heap" in ATProto and "message passing" in ActivityPub.

   In short: if everyone fully self hosts in message passing, you send messages between just send messages to relevant recipients

   In a shared heap approach, to *not* miss relevant messages, all users must receive copies of all messages (including irrelevant ones), which is quadratic if everyone fully self-hosts

2. Embed this notice
   arcanicanis (arcanicanis@were.social)'s status on Tuesday, 27-Feb-2024 08:11:36 JST arcanicanis

   in reply to

   Cleaner syntax (@method and @path are separate, versus rolling it together as (request-target)), clearly lays out the expectations of which implementation decisions must be made when rolling it into a larger protocol/system (section 1.4), more standardized signature methods (including ed25519), and can be possible to build and make use of well-tested reusable libraries than having to need some niche implementation that only applies to ActivityPub.

   In cursory glance, it's just a few syntax changes to 'upgrade' existing implementations. But part of it isn't just RFC9421 itself, but an opportunity to fix the state of HTTP Signatures in ActivityPub within the same effort.