This article sets out to compare ActivityPub and ATProto, but what it really compares is Mastodon and BlueSky;
It is useful however as a 'user story' about the failure modes of the existing, Mastodon-dominated fediverse.
(1/?)
This article sets out to compare ActivityPub and ATProto, but what it really compares is Mastodon and BlueSky;
It is useful however as a 'user story' about the failure modes of the existing, Mastodon-dominated fediverse.
(1/?)
These were part of OStatus, and Mastodon continued to support them when it implemented AP. With Mastodon servers as the majority of the AP network, other software was expected to keep using them too.
But BS style IDs are just as compatible with the AP spec. Also, as Takahē demonstrated, one AP server can support IDs using more than one domain name. Enabling the same BYOD (Bring Your Own Domain) that BS offers.
(2/?)
This is a political problem more than a technical one. But there are forms of network management that could reduce the churn. I laid out a proposal here for a numbering scheme that could automate a lot of moderation work, allowing human mods to spend more time considering edge cases together;
https://codeberg.org/fediverse/fediverse-ideas/issues/88
(3/?)
The solution to this is a fediverse made up of many more, smaller servers. With more people actively involved in the governance and funding of the server they use. As well as using AP software other than Mastodon;
https://delightful.club/delightful_fediverse_apps/
Almost all of which makes much more efficient use of server resources than Mastodon's creaking Ruby-on-Rails backend.
(4/?)
This is a bonfire demo instance for testing purposes