Also the software needs to be efficient. Use less RAM and CPU cycles. And I don't think the ActivityPub protocol in itself is very efficient. I'd like those aspects compared to an old federated technology like NNTP or email.
But I'd agree on the things in top. Content should get compressed and cached on demand. Neither transferred every time from the original instance, nor transferred without a user ever viewing it. Caching on demand or a DHT (P2P) storage backend could do that.
I think the author is a bit late to the game. There are like 20 different forks of Mastodon to address exactly that, which some developers have already migrated to. Additionally there are Misskey, Pleroma with their respective forks. Some of them are pretty active.