After a week of development, and using existing code to get a head start, I have the beginnings of an ActivityPub server written. It currently does very little in the way of ActivityPub processing: there is an /inbox that dumps all requests to a queue for later processing (along with the information needed to validate the HTTP signature minis the public key), there is an /owner/actor and there is a very basic webfinger implementation.

This is enough to get the account viewable thru existing software (see @teknomunk), but not enough to actually interact with anyone. Implementing code to get incoming follow requests working is my next priority.

I'm already getting activities delivered (mastodon.social keeps wanting to Delete @bappity for some reason).

If this project doesn't stall, and enough projects I've started have stalled for me to hedge here, I expect to move to the new server when enough of the basic functionality is in place so that all my normal activities can be done without me switching accounts.