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. 🥂
marius
@mariusor@metalhead.club
Mostly a programmer. Implementing #ActivityPub in the #Go programming language. Current projects: * #GoActivityPub - a library to use ActivityPub in Go. * #FedBOX - a generic ActivityPub service supporting the client to server API. * #brutalinks - a link aggregator inspired by (old) reddit, hacker news and lobste.rs built on top of FedBOX. * #oni - a single user ActivityPub server with minimal fuss.
metalhead.club
Speaking of #ONI, I can't wait for the Sanitizer DOM API to start making an appearance in mainstream browsers later this month.
Currently the biggest chunk of the 140K that make the JavaScript application that comprises ONI is composed of the dompurify library I'm using now to do sanitization of NaturalLanguageValues in #ActivityPub objects.
You've seen all posts