Find the index and earlier parts of this series here. We’re almost there! Thanks for sticking with me on this journey. In this final part, we’ll integrate replies and comments into your static website. Motivation Integrating replies is quite similar to how we handled subscriptions. Since our posts now exist in the Fediverse, we want to treat them as first-class citizens. This means replies to our posts should appear on our site.

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 (aka. sending your posts to live infitely in the fediverse) 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) In a few words, you will iterate your list of followers, get their inbox url, and send a request to such url to create an fediverse object (note, article, etc.

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.