And I guess this question is two parts: 1. Regarding the current lemmy implementation, and 2. The activityPub protocol in general
And I guess this question is two parts: 1. Regarding the current lemmy implementation, and 2. The activityPub protocol in general
if it is a hindrance on the entire network, it would be interesting to explore the idea of “instance pools” in the future. Many smaller instances act as a single instance when it comes to network federation, but still maintain data separation, moderation and management. I would assume these instances would just have to have the same federation list.
I’m not aware of real-world fediverse examples, but a common approach to this kind of thing in distributed systems in general would be to introduce a federation hub/proxy that relays messages from the main instance, and who’s only job is to handle the fan-out load required to copy one stream of federation messages from the server to become many streams to all the federated subscribers. There are also approaches to have a pool multiple such proxies.
Again, no idea how these suggestions apply to ActivityPub, but many systems do this kind of thing and I’d sort of expect it would work with ActivityPub (or could be made to work with some effort once the network is big enough to warrant it).