In the previous tutorial we have learned how to send a reply to another ActivityPub server, and we have used mostly static parts to do it. Now it’s time to talk about how to subscribe to other people and receive messages.
The inbox Primarily this means having a publicly accessible inbox and validating HTTP signatures. Once that works, everything else is just semantics. Let’s use a Sinatra web server to implement the inbox.
A committee of members of the European Parliament have voted to approve Article 11 and Article 13, which pose a risk to the decentralization of the web and freedom of creative expression.
I follow many talented artists on Mastodon, and over my 2 years of being on the platform I have noticed some common patterns that may help a newcomer find their audience on here, too.
Today we’ll be looking at how to connect the protocols powering Mastodon in the simplest way possible to enter the federated network. We will use static files, standard command-line tools, and some simple Ruby scripting, although the functionality should be easily adaptable to other programming languages.
First, what’s the end goal of this exercise? We want to send a Mastodon user a message from our own, non-Mastodon server.
So what are the ingredients required?
