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.

https://lemmy.world/post/23471887

you are viewing a single comment's thread
view the rest of the comments

[–] Blaze@lemmy.dbzer0.com 8 points 4 months ago (8 children)

This is is wild.

The wildest thing is that it has been like this for a while: https://lemmy.world/post/20575394

[–] Alphane_Moon@lemmy.world 6 points 4 months ago (7 children)

I guess it's good that this issue is in the process of being resolved while the network is small and primarily consists of technically minded users.

[–] Kichae@lemmy.ca 5 points 4 months ago (6 children)

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.

[–] Die4Ever@programming.dev 6 points 4 months ago* (last edited 4 months ago)

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.

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

load more comments (5 replies)