Parallel sending of federated activities to other instances. This can be especially useful for instances on the other side of the world, where latency introduces serious bottlenecks when only sending one activity at a time. A few instances have already been using intermediate software to batch activities together, which is not standard ActivityPub behavior, but it allows them to eliminate most of the delays introduced by latency. This mostly affects instances in Australia and New Zealand, but we’ve also seen federation delays with instances in US from time to time. This will likely not be enabled immediately after the upgrade, but we’re planning to enable this shortly after.
I mean, it's not being resolved, since the issue is that LW is too big to effectively federate, and LW is refusing to take the steps to improve the situation. Weirdly enough, this is less of an issue if the network scales horizontally, with a large number of small nodes.
But also, this is a symptom of the current attitude of "it shouldn't matter where the community is hosted". The fediverse is a simulacrum of centralized social media, and a poor one at that. The more we try and beat it into that shape, the more it's going to get all weird on us.
Like, a significant issue here is the insistence people have had that up/down-votes be synchronized. People want to know what the global passive-aggressive opinion on a post or comment is, rather than the local one, which requires every single button press to be sent to each and every subscribing website. And people expect stuff to be sent out as a live stream, rather than being held back for batching, too.
There's a significant cultural issue to be sorted out here. Better mechanical features aren't going to solve it in the long run.
LW is like ~35% of Lemmy's 55K MAU, right? So around ~19K MAU. For the Threadiverse to be viable on a mass scale, support for an instance with ~20K MAUs is a must. I would argue it's a must for an instance with 2 million MAUs.
This includes graceful support for up/down votes.
The issue is more about the spread of active communities and their centralization on LW.
LW comments make it just fine to Aussie.zone on this community, as it's on Lemm.ee: https://aussie.zone/post/18681158/15483480
When you look at the most active communities on the platform, the vast majority of them are on LW: https://lemmyverse.net/communities?order=active
I get that, I just don't think at this particular point in time (with 55K MAU) it is viable to focus on distribution of communities.
It's not like we have 10 million MAUs and we are seeing too much centralization on LW.
Let's get to at least say 500 K MAU stable and then focus on decentralization.
On the other hand, it's probably easier to decentralize while we have 55K MAU rather than 500K
That's also true, can't argue with that.
I figure this could be reduced a lot if even just 1 minute worth of votes were batched together, although I don't think the ActivityPub standard technically includes batched activities currently