These posts are really useful to get a grasp of ActivityPub (if you have a programming background): https://rknight.me/building-an-activitypub-server/ https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/

And of course the official spec (although its less useful): https://www.w3.org/TR/activitypub/

And a followup question: wouldn’t it be more efficient for big instances to use WebSockets to federate? Making a HTTP request for every action your users take seems unnecessarily wasteful.

Amazing blog post! Been reading the ActivityPub spec and found it rather lacking. It’s only when you add WebFinger and signed messages that things start to make sense.

+1 Or perhaps lottery numbers? I’m not picky

I’ve started using it a couple of weeks ago. For now, I’m having it capture emails with invoices and moving the PDFs to a folder in my Google Drive.