Goofed Home

Before commenting, please notice that Blento can do stuff like having cards that show account own’s collections: basically the fact that the blento site and the other app data are on the same repository allows for nice interactions. There is no need for crosslogin or cross-apis and pull or push stuff, it’s everything already there. So it’s not just about taking blento and having a webring that speaks activitypub somehow.

Before commenting, please notice that Blento can do stuff like having cards that show account own’s collections: basically the fact that the blento site and the other app data are on the same repository allows for nice interactions. There is no need for crosslogin or cross-apis and pull or push stuff, it’s everything already there. So it’s not just about taking blento and having a webring that speaks activitypub somehow.

Meeting minutes from the last Social Web Working Group call, which covered topics like discovery, groups, trust and safety, and more.

https://github.com/w3c/socialwg/blob/main/meetings/2026/2026-04-03-CG-WG-joint.md

Reminder that the fediverse is a "group project" and really does take a village.

Care to join in and help?

#fediverse #ActivityPub #W3C #SocialWeb

Cache-Control and Vary

Thanks to everyone who replied! Unfortunately HTTP caching is not our strong suit in the ActivityPub world; HTTP Signature header(s) are a real public cache buster. But you can do at least some good caching per user. tags.pub provides ETag, and sends If-None-Match and If-Modified-Since, but doesn't do Last-Modified well yet.

The problem with Signature: and Signature-Input:

If the server wants to say, "this content is different for different users", you use the Vary header. For OAuth, you'd use Vary: Authorization, say. And the cache knows to separate data for different users. Same OAuth token, you can reuse the cached data.

We include our ID in the Signature (or Signature-Input) header. But we also include a timestamp there, so every single request has a different signature (by design).

@oli @julian yeah, so I'm interested in what filters applications need, and a good future feature will be "filtersets" which don't affect the public API but do change the admin experience (e.g., you could create a "silence" filter that includes these named filters, so you can apply them all at once repeatedly, but to a consumer it's still clear you're recommending they take these specific actions

And remember: the datasets only contain recommendations, they're not prescriptive. Any consumer can decide to ignore your recommendations as a dataset producer and do something different.

@julian writing all the docs takes a huge amount of time 😅

I also don't think I've structured them right yet

@julian I already have access to the package.

@julian anyways, moved and shipped!

https://www.npmjs.com/package/activitystrea.ms

@julian I was informed of one gap in the documentation but the API is very follow your nose

@julian so suspend is either reject or drop as a recommendation; reject say you should tell the sending server "I reject this activity" drop is "I acknowledge this activity but it quietly goes to /dev/null

@julian waiting for implementations to give me feedback