I like ActivityPub and the decentralized social Web as much as the next person but we all know that scalability is a massive problem and I haven't seen too many convincing approaches to fix that. So let's not pretend this is just a magic silver bullet.
Blogs and the web didn't scale to actual web traffic (which admittedly many blogs never needed), centralized caches and services were necessary for this stuff to work. Which is exactly why we got so much centralization.
Solving that for decentralized social networks is the core issue.
I really don't know how often we need to go down this path, but here we go again
#Activitypub is a #W3C specification
It is not an implementation, it is not code, it is not an "app"
#Mastodon, an Activitypub --> based <-- software implementation in executable code, current is run on some 12,040 Active Servers
Here: https://fedidb.org/software/mastodon
How "decentralized" do you need to be?
@FinchHaven yeah, you're missing that that's exactly what's being addressed.
The protocol in the specification has scalability issues outside of any implementation.
All of the implementations have to deal with those specified scalability issues.
