← Feed

Posts

• Limiting Group Membership Metadata Exposure

  This is a discussion thread for an open issue on GitHub: https://github.com/swicg/activitypub-e2ee/issues/83

• Adding E2EE Task Force

  We had a meeting of the E2EE Task Force. One participant asked for a way to participate in discussions without using GitHub. I think having a topic here on activitypub.space would be a great way to do that, and the task force agreed (notes here: https://pad.w3.org/p/ActivityPub_E2EE_Task_Force_28_Jul_2026). How do we add a space for it, like the other task force spaces? @julian ?

• Basic Profile for Social API Servers

  There's a new draft of the basic profile for Social API Servers from the ActivityPub API Task Force: https://swicg.github.io/activitypub-api/basicprofile It covers some very basic features for getting an interoperable set of clients and servers working together to provide simple social networking functionality.

• Post #2537944

  @reiver@mastodon.social That's not true. Most of those are not correct AS2. Only '"type": "Banana"' is correct. Activity Streams says, The serialized JSON form of an Activity Streams 2.0 document MUST be consistent with what would be produced by the standard JSON-LD 1.0 Processing Algorithms and API [JSON-LD-API] Compaction Algorithm using, at least, the normative JSON-LD @context definition provided here. So, assuming that you've defined some Banana exten...

• Our X-RateLimit-Reset headers are bad and we should feel bad

  I've found at least four different formats used on the Fediverse for the X-RateLimit-Reset header: A datestamp (Mastodon) Unix epoch in seconds Time offset in seconds (N seconds from now) Unix epoch in milliseconds (Holos) It's possible to use some heuristics for these (looks like a date, looks like an integer, range of the integer), which are pretty reliable. The new RateLimit headers from IETF are very nice, but don't seem to be well-supported yet.

• Federating servers

  @silverpill@mitra.social really? How does it work?

• Federating servers

  So, one part of the popular imagination about ActivityPub I've seen is the idea of server federation. I think the idea is that if two servers have interacted in some way, all (?) public (?) content from one server will be sent to the other server, and vice versa. This comes up a lot with new servers; people ask to have a post shared broadly so that their server rubs shoulders with others, getting the federated feed flow going. ActivityPub does in fact have a mechanism defined for this:...

• Double-knock strategy for HTTP Signature

  In the HTTP Signature Report we suggest a double-knock strategy for deploying RFC 9421. Basically, try RFC 9421 first, and if you get an error, downshift to draft-cavage-12 and try again. I just realised, in testing with Pixelfed, that this doesn't work if the remote server doesn't check signatures in the Web routes. Pixelfed returns a 200 response for POST requests signed with RFC 9421, but its backend workers reject the input because Pixelfed doesn't understand RFC 9421. So, it s...

• 23 Apr 2026 Groups TF Meeting Minutes

  A link here to to the W3C etherpad: https://pad.w3.org/p/ActivityPub_Groups_TF_2026-04-23 I'll add the link to the official meeting notes page once they're merged on GitHub.