Visualising ActivityPub vs. Atproto Architectures for Non-Tech People
Convener: Joan Pla (@joanpla@mastodon.social)
Participants who chose to record their names here:
- Scott Jenson (@scottjenson@social.coop)
- Aditya Singh (@adixingh@hachyderm.io, @aditya.myatproto.social)
- Evan Prodromou (@evanprodromou@socialwebfoundation.org)
- Jeremiah Lee (@Jeremiah@alpaca.gold)
- Lexi (@AlexisBushnell@Toot.Wales)
- Misha (@MishaVelthuis@social.edu.nl)
- Tommi (@tommi@pan.rent)
Notes
EP: network of people is more evocative than a network of software or instances
EP: I really don’t like https://en.wikipedia.org/wiki/Fediverse#/media/File:A_view_into_the_Fediverse.png
ActivityPub is a social layer for existing Web technologies. It scales like any website and using the same scaling methods. RSS, email, and websites scale to billions of reach without requiring larger intermediaries for basic functionality.
ATProtocol will always require some large compute for app views. It can be low cost to host your own data, but creating the social network experience requires infrastructure larger than a typical person would operate.
Aditya: I wrote about it as well ;) https://openfuture.eu/blog/public-money-public-platforms/
Aditya: The “+1 Principle”, have governments commit to posting on at least 1 other open social platform in addition to the commercial services. Easier ask than asking people to not be on a commercial service, which means giving up reach.
