Posts List

A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 6

A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 6

You can find the index and other parts of this series here. We are almost done! Thank you for coming all the way into this journey. In this part we will learn how to broadcast (aka federate) your site posts to your folowers. Overview The federation of your posts is pretty straighforward: sequenceDiagram BroadcastTool-Storage: Retrieve followers (actor uris) BroadcastTool-Follower-instance: Get actor info (including inbox uri) BroadcastTool-Filesystem: Get note json (post) BroadcastTool-Follower-inbox: Send a create action (wrapper of note) The Inbox receives POST HTTP requests for different actions.

A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 6

A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 6

You can find the index and other parts of this series here. Let’s dig in into the most controversial part of my guide: the inbox. As far as I know, there is no way to make this inbox static. However, thanks to the fact that ActivityPub does not require the inbox to share the same domain as the other elements, we can host it anywhere. I believe it could be controversial for two reasons.