#goactivitypub

2 posts · Last used May 06

Back to Timeline
Marius @Marius@marius.federated.id · Apr 30, 2026
Huzzah!! After about a little less than one month I have managed to deploy the new versions of the #GoActivityPub libraries containing RFC9421 for both outbound request signing and inbound verification, to both #FedBOX and #ONI. During this tme we contributed to another Go module to add support for our use cases, then we ended up replacing it all together with another one having a simpler API. In the process I managed to simplify the go-ap/auth module to contain only the verifiers for OAuth and HTTP-Signatures (in both draft and RFC compatible flavours). This post is in fact, the first one that uses them for remote dissemination, and if you see it on your timeline it doesn’t neccessarily mean that your instance supports this signature type, but rather that the “double knocking” mechanism of retrying with the old draft version is functional. Here’s to hoping it won’t be needed for much longer. 🥂
0
3
0
marius @mariusor@metalhead.club · Apr 17, 2026
I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month. Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus. This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable. Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker: #ActivityPubDev #fedidev #httpsig
7
1
1

You've seen all posts