I see. So essentially the issue is built in to the way Activity Pub is designed. It is a scaling issue. Your browser may not blink at loading 100 resources, bu

I see. So essentially the issue is built in to the way Activity Pub is designed. It is a scaling issue. Your browser may not blink at loading 100 resources, but say you were constantly reloading 100s of tabs, it would start to grind down. Rewriting in a more efficient language would help, but that would just mean it would start to grind down when you have 20,000 users rather than 10,000. I'm surprised it doesn't do some kind of batching peer to peer communication instead. Maybe that wouldn't be as real time. Thanks for the insight.