mayel

@sindum@mstdn.dk @julian I hope you two can join the W3C social web working group's groups task force meeting today? https://github.com/swicg/groups/issues/37

we recently added RFC-9421 to @bonfire@bonfire.cafe : https://docs.bonfirenetworks.org/federation-interoperability.html#7-http-signatures-secure-fetch not doing double-knock but rather using different methods to try and discover what the other side supports (in priority order): Inbound signature caching: When a remote server sends us a signed request, we cache which format they used (cavage or RFC 9421) Accept-Signature header: When we receive an Accept-Signature response header from a remote server (on any response — WebFinger, object fetch, inbox POST), we cache RFC 9421 support for that host FEP-844e generator detection: Check remote actors' generator.implements or the instance service actor's implements property for RFC 9421 support URIs (see below) NodeInfo software version: Look up the remote's software name and version against a known-support map (e.g., Mastodon ≥ 4.5.0, Fedify ≥ 1.6.0, Hollo, Mitra) Default: Fall back to draft-cavage

@strypey@mastodon.nzoss.nz This sounds like what we're doing for publications like Jacobin DE and Totnes Pulse, as a cooperative effort that brings together @bonfire@bonfire.cafe, @lauti@bonfire.cafe for events, and @newsmast@newsmast.social for a mobile app, and integration with their existing Ghost and Wordpress sites/blogs.