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.
It should have. The backend added parallel syncing since a few versions back. By all accounts it should be going down.
The final bullet point of https://lemmy.world/post/23471887 suggests that that feature may not have been enabled yet.
That would be very unresonable imho. It’s the most important feature for them.
Perhaps they wanted to assess as few changes as possible simultaneously before turning on any optional features. I would imagine they will get to it fairly quickly.
https://lemmy.world/post/23471887