I can completely understand why that wouldn’t be, like imagine if an instance got big and had say, 1k communities. When a community is indexed, it loads 50 posts initially, then the target instance federates updates over once a person subscribes. Then, every time a new instance discovered them, they’d be sending 50k posts over and getting bogged down.
I think the top 5/10 communities could be reasonable, though. This could also be accomplished with a bot either managed by an instance interested in pulling that data, or a user wanting to automate subscriptions a bit.
Last I checked there were 10k communities and a few 100 instances total, which is tiny in computer terms. As it grows larger maybe it would be an issue, but really even millions of instance names properly compressed shouldn’t be onerous for a one-time download.
I can completely understand why that wouldn’t be, like imagine if an instance got big and had say, 1k communities. When a community is indexed, it loads 50 posts initially, then the target instance federates updates over once a person subscribes. Then, every time a new instance discovered them, they’d be sending 50k posts over and getting bogged down.
I think the top 5/10 communities could be reasonable, though. This could also be accomplished with a bot either managed by an instance interested in pulling that data, or a user wanting to automate subscriptions a bit.
Last I checked there were 10k communities and a few 100 instances total, which is tiny in computer terms. As it grows larger maybe it would be an issue, but really even millions of instance names properly compressed shouldn’t be onerous for a one-time download.