I'm doing a deep dive into documenting #ActivityPub for a soon-to-be-released software project and in doing so, found a few parts of the standard I weren't aware of was in the standard. Therefore I'm now writing up a document distilling the AP spec so folks can check their own implementations against it.
It sounds like there might be some useful convergence there between your efforts!
Sadly this writeup, much like other writups, is missing all the client to server interactions.
While I agree with C2S stuff in AP could be a bit better (and I've talked about ways I think it could happen), I am a bit frustrated by the idea that implementers should just ignore it.
I'll give it a B+ ;)
My minimal AP implementation doesn't do authentication. I've been deciding whether or not to add client support. The additional 100 lines in both client and server seem worth it, but we'll see how it goes.
My reason for writing the application is for a testing ground for some of the stuff I'm working on re-anti-spam and also Golem re-implementation.
emacsen.net is one server in the network