Wait a minute - you’re a Lemmy.World user! And we didn’t need to wait a week to see you comment on a thread we moved on from ages ago! This is a big deal!!
Is there problems between Aussie zone and Lemmy world instances? I’m out of the loop on that one. I don’t use Lemmy heaps. I was looking for friendly social places to avoid awful reddit behaviour, but ended up finding some similar things on Lemmy last year so deleted my account. But now I’m back but engaging less. Perhaps I should have got an Aussie.zone account instead.
The issue isn’t specifically between aussie.zone and LW. Its actually federation of large numbers of activities to a remote instance at “high” latency. Due to the way lemmy works, only ~3 to 4 activities can be sent from one instance to another per second (not 100% accurate, but close enough)… Activities in excess of this are queued for sending.
The most recent version of the lemmy server software (0.19.6) adds the ability for admins to send multiple activity streams at once. This should greatly improve the rate at which activities are federated… but requires the sending instance (LW) to upgrade and enable the feature. FWIW I’ve already upgraded aussie.zone and enabled this feature.
(posted from my LW @ 17:55 11/11/24 AWST for testing)
edit: you’re welcome to sign up at aussie.zone if you like, though once LW is upgraded you’ll be able to interact with AZ just fine from here.
The problem basically boils down to a design feature (or flaw) in the original Lemmy code. The different instances update each other transaction by transaction. Each lemmy.world upvote, post, comment etc is sent to the other instances one by one. Because lemmy.world is in Finland and Aussie.zone is in Sydney, that takes about a quarter of a second.
Lemmy devs never pictured a situation where one instance would get so big that they couldn’t update everyone in a timely manner. Basically, lemmy.world generates more than four upvotes, comments, posts etc per second. So it took until this afternoon for me to see your comment.
The latest version of Lemmy code allows instances to open more than one stream of updates. When/if lemmy.world upgrades to that version, they’ll be able to open several channels to update the other instances.
Wait a minute - you’re a Lemmy.World user! And we didn’t need to wait a week to see you comment on a thread we moved on from ages ago! This is a big deal!!
Is there problems between Aussie zone and Lemmy world instances? I’m out of the loop on that one. I don’t use Lemmy heaps. I was looking for friendly social places to avoid awful reddit behaviour, but ended up finding some similar things on Lemmy last year so deleted my account. But now I’m back but engaging less. Perhaps I should have got an Aussie.zone account instead.
The issue isn’t specifically between aussie.zone and LW. Its actually federation of large numbers of activities to a remote instance at “high” latency. Due to the way lemmy works, only ~3 to 4 activities can be sent from one instance to another per second (not 100% accurate, but close enough)… Activities in excess of this are queued for sending.
The most recent version of the lemmy server software (0.19.6) adds the ability for admins to send multiple activity streams at once. This should greatly improve the rate at which activities are federated… but requires the sending instance (LW) to upgrade and enable the feature. FWIW I’ve already upgraded aussie.zone and enabled this feature.
(posted from my LW @ 17:55 11/11/24 AWST for testing)
edit: you’re welcome to sign up at aussie.zone if you like, though once LW is upgraded you’ll be able to interact with AZ just fine from here.
Thanks mate. I might do that as this seems like a nice part of the fediverse.
The problem basically boils down to a design feature (or flaw) in the original Lemmy code. The different instances update each other transaction by transaction. Each lemmy.world upvote, post, comment etc is sent to the other instances one by one. Because lemmy.world is in Finland and Aussie.zone is in Sydney, that takes about a quarter of a second.
Lemmy devs never pictured a situation where one instance would get so big that they couldn’t update everyone in a timely manner. Basically, lemmy.world generates more than four upvotes, comments, posts etc per second. So it took until this afternoon for me to see your comment.
The latest version of Lemmy code allows instances to open more than one stream of updates. When/if lemmy.world upgrades to that version, they’ll be able to open several channels to update the other instances.