Greetings! Big news this week, from multiple directions!
Mastodon and ActivityPub, together at last!
First of all, Mastodon has launched version 1.6 with ActivityPub support! This is a huge piece of news. While Mastodon is not the first implementer of ActivityPub, they are by far the largest existing implementation, with approximately 850k registered users. We're excited to have them on board!
A new Candidate Recommendation!
This week we published a new Candidate Recommendation (aka "CR") of ActivityPub. This release contains two major changes:
Follow
requests are now explicitly replied to with either anAccept
orReject
.publicInbox
is now renamed tosharedInbox
and in addition to being used for distributing and reading public posts, it may also be used to deliver posts to followers to reduce the number of HTTP requests made on followers-only posts between federated servers.
These changes are normative, so update your implementations!
The Candidate Recommendation is the period in which we try to stabilize the standard and get enough implementation to make it to Recommendation status. We don't take normative changes lightly, but sometimes we such changes are found to be necessary in this stage... in this case, we found that both of these changes were necessary for Mastodon, and projects the size of Mastodon, to adopt ActivityPub.
What's next?
We've quietly launched the test suite... very quietly, because not all test suite functionality is added yet! Only the "client-to-server server" section is yet working. However, we're working on the rest of it and hope to have it up sometime within the next few weeks.
That's it for now. Happy implementing, everyone!