The past month has been:
- Implementing more of
apcore, the FLOSS ActivityPub server framework in Go. Goal is to basically be plug-in-your-mux for web handling, plug in functions for ActivityPub processing, and just launch (with either S2S / C2S or both). Provides lots of sensible behavioral defaults for the
activitylibrary, lets admins have lots of configuration options, etc…
activity/astoolcode generation. This has been a big one, formally supporting the
securityontology (which has type-less “types”), and trying to cram JSON-LD’s square peg into static typing’s round hole, but investing early on in the multi-vocabulary understanding of the tool paid off rather well otherwise. Code generation as metaprogramming still is a sucky problem.
- Fixed a hash sum bug in
httpsigfor Digests. Proof that the
hash.Hashinterface in go was foot-gun designed. Yes,
httpsignow does both HTTP Signatures and Digests, but still behind a very simple interface.
I’d like to thank Ben for stepping up and filing issues against Go-fed as he’s been building out a Guild Wars 2 guild application of some sort.
Also I am slightly late to the topic here but apparently go-fed’s serialization strategy of non-functional properties can cause problems in pleroma. That’s a TODO of some sort for someone, I’m sure.
This winter I hope to get the
No matter if it is the
apcore, or any sub-packages, always open to collaboration.