Couple of things just in case I run out of time,,,

Pubcrawl has a few interop issues with Mastodon, but nobody is willing to look into why on that side. What I've done is to go back to the spec and all the latest working group decisions and I'm trying to implement it faithfully. If there are problems making it work, you may have to wait for a real communications project to try and federate with before things get solved. Once there's interop with somebody/anybody, you can branch off that to open federation to the walled garden. At the moment we're trying to be faithful to the spec so that somebody can read the spec and look at the packets and figure out who's implementation is buggered.

Multimedia content is going to be sent as an 'Article'. There's a good chance Mastodon will never allow multimedia content. Fuck them. Try and find somebody sensible to work with. We'll send plain text and microblog stuff as a 'Note' which is what Mastodon uses. Attachments/images are all separate and appended to the end of the content, so this won't work at all for story-board narratives and signatures will break if you have to modify somebody's content to fit that representation. If you want to get support, look at News organisations of any kind. They know how multimedia content needs to work. The ActivityPub folks all have their noses so far up Eugen's bum that you aren't going to get any support from them and nobody therein has any experience with real world communications or federation issues. They're web people, and most are kids who've never done anything like this before.  

Apple appears to have removed third-party cookies entirely in its latest browser release. This is a problem for decentralised permissions; but thankfully only applies to images and media elements. My thinking if other browser vendors follow suit is to re-purpose the 'sslify' module to proxy private photos/videos. These can and should be buffered/streamed. At that point it's probably a good time to abandon the social networking space and concentrate on content management, since openwebauth will still work just fine; but private media in your stream is going to suck up extra resources to proxy. It's still workable but not as elegant.

Hopefully I'll still be around and will take care of all this stuff, but just in case I'm not....