The whole algorithm (AppView) is centralised. While it’s technically possible to host with enough capital, a second AppView server would also double bandwidth required for every message sent on the network. This gets worse the more AppView instances you add, as every message has to be sent to every AppView server (exponential growth)
No, ActivityPub only send messages to the recipients. Uninvolved servers don’t get the message at all until one of their users explicitly searches for it.
In the worst case where every user has their own server, one message per recipient is sent. Adding another recipient on their own server means one more message being sent and so forth.
The whole algorithm (AppView) is centralised. While it’s technically possible to host with enough capital, a second AppView server would also double bandwidth required for every message sent on the network. This gets worse the more AppView instances you add, as every message has to be sent to every AppView server (exponential growth)
Thats the same issue with activity pub, is it not?
No, ActivityPub only send messages to the recipients. Uninvolved servers don’t get the message at all until one of their users explicitly searches for it.
In the worst case where every user has their own server, one message per recipient is sent. Adding another recipient on their own server means one more message being sent and so forth.