Been a busy week #coding on my #fediverse client. I finally have my #python #framework (#Jenkwerx) doing exactly what it's supposed to so I've been preparing to follow my first user - me on #Mastodon!

..but I pushed pause because, while my inbox is rocking, I don't have my #ActivityPub outbox set up to process from a queue yet (it's still sending live). 😞 So back to unsexy "proper #code logic" for a bit..

..still confident I'll be following a few folks by Sunday tho - ugly test attached! 😆

@multiverseofbadness if you are open to having our derpy little instances send stuff to one another so we don't pollute the wider fediverse, wait a week or two for me to catch up? 😉

@multiverseofbadness see here's where I went back and forth a whole bunch.

GET /inbox is client to server, so optional if your goal is federation between services.

Wouldn't POST /outbox be similar? I'm bolting on #ActivityPub integration, so the concept of posting to the outbox is already achieved with my own #API.

I can see the advantage if you want to allow things like mobile apps to act on your behalf, but I guess that's out of scope for the initial implementation.