@dansup @supapp @HolosSocial is also working on encrypted messages on #activitypub will they be compatible?
I've started my exploration of using @timbray's Quamina project for saving some compute time in the filters module of #GoActivityPub
Currently the GoAP storage backends iterate over resources (usually stored as raw JSON bytes), unmarshal them into GoActivityPub object structs, and *only* then apply the custom filtering logic on those objects. Since the majority of the objects generally fail the filtering logic, all that JSON decoding is wasted compute time and makes things slower.
Ideally quamina will allow me to check the raw JSON payloads directly against the filters, streamlining the execution and speeding things up.
20.2.02026
Vermischtes | Sudoku | Feedbackhttps://kuemmerle.name/20-2-02026/

RE: https://mastodon.social/@dansup/116103413892360695
We can all win in the Fediverse đ.
Big thanks for making this web possible! It wouldnât be possible without the contributors to projects, and all the awesome people within the fediverse.
#Fediverse #ActivityPub #OpenSource #FOSS #Decentralized #CommunityDriven #ThankYou #Fedi
Funny and strange. Andrew Nesbitt has posted a far too elaborate alternate history of #activitypub
https://nesbitt.io/2026/02/20/activitypub.html
Internationalise The Fediverse
https://programming.dev/post/46064439
If we have those #ActivityPub patterns we can speak together in a higher-order domain language that is closer to actual solution design, and that will make ecosystem participants happy (as happy or happier than our friends in the #ATProto atmosphere).
I agree with what you say.
On the use of "stream(s)" I did a search in both specs, and it is only very sparsely used in the meaning of a stream rather than an Activity Streams document or object.
One time mentioned as "Activity Streams consumer" in #ActivityStreams core and another mention in the Security considerations section.
> Publishers or Consumers implementing Activity Streams as a stream of public data ..
And twice in #ActivityPub where it says both inbox and outbox where it mentions "the outbox stream", "the inbox stream", and one other mention in definition of "Social API" where it is said to provide a "social stream of the user's actor".
So I would not consider this formal language terminology right now. That said, it would be good to further formalize the concept of a Stream, as it is a higher-order concept that'll help lift discussions out of nitty gritty impl detail territory.
#ActivityPub, a *great start* providing the key ingredients.
#Fediverse, where things are cooked into a mush, by pragmatic though unsustainable fast-food preparation.
Recipe:
- Mash everything into #ActivityStreams
- Overload the semantic frying pan
- Sprinkle in combinatorial complexities
- Cook until too hot
Then simply keep stirring with increasing whack-a-mole maintenance burdens until project phased out.
Or become the post-facto #interoperability leader and dominate the restaurant chain.
Recipe improvement tips:
- Add #FEP spice to the mix where you can!
- Participate in #SocialCG collective cooking.
đ Castopod : Et si votre podcast devenait un citoyen du #Fediverse ?
Marre des jardins fermés (Spotify/Apple), j'ai testé @Castopod.
C'est du lourd pour la souveraineté :
* Auto-hébergement (Licence AGPLv3)
* Intégration #ActivityPub : vos épisodes sont des posts interactifs
* Podcasting 2.0 : chapitres, transcriptions et WebSub pour l'instantanéité
* Respect du RGPD et stats IABv2 anonymisées
Le RSS ne meurt pas, il évolue enfin.
Pour mon analyse complĂšte, les liens sont en commentaires
#OpenSource #SelfHosted #Podcast #SouveraineteNumerique #Castopod

I was really confused why when I made requests to wafrn URLs I was getting HTML back. At first I thought maybe it was a 404, but, no, wafrn instances are returning 200 responses despite my Accept header requesting ActivityPub content.
So apparently, if wafrn requires a signed request to /fediverse/post/:id/ or /fediverse/blog/:url/outbox, and if the request is either not signed or use RFC-9421, then wafrn will respond with a 200 text/html representation of the content.
And, also... Strangely...
My requests to collection endpoints (even /fediverse/post/:id/replies) do respond correctly.
I do appreciate implementations that return HTTP error responses (401, 403, and 406). It allows me to catch the error and try again until all signature types are exhausted (RFC-9421 first, then cavage-12). But I guess now, in order to workaround wafrn behavior, I cannot assume a 200 is a successful response and will resend the request if the Content-Type is not ActivityPub content.
And this behavior also confuses browser.pub.
