this post was submitted on 02 Jul 2023
7 points (100.0% liked)
Lemmy.world Support
3227 readers
1 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
To open a support ticket
You can also DM https://lemmy.world/u/lwreport or email report@lemmy.world (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I haven't studied the federation code, but my understanding is that it's on a retry basis. A message that fails delivery would retry for "a while", long enough to handle an instance getting rebooted or going down for maintenance for an hour.
But if something fails delivery for days, the sending server will probably stop trying... which is kind of a desirable property to prevent a server coming back online from getting inundated with a backlog of failed deliveries it can never catch up on.
A backlog reconciliation feature would be cool, but I don't think it works that way today.
Fair enough. Yeah backlog reconciliation would be really nice especially for new instances that spin up. It would be nice if you could do the "site:lemmy.world [search query]" trick at some point. Without backlog reconciliation that may not work as well.
Yes, I get the impression that content changes are pushed between instances, rather than trying to synchronize entire communities.