this post was submitted on 16 Jul 2023
22 points (100.0% liked)
/kbin meta
39 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If federation updates were missed e.g. during the DDOS attacks, on Lemmy or just when instances were creaking from reditMigration demand, these updates won't be resent. Instances never activity seek out missing information to resynchronize.
...basically if it has been weeks, it's just not going to happen.
Also worth noting downvotes don't federate they are only know to each local instance.
My perception is that it is all working pretty smoothly now. I quite often switch between my Mastodon account and kbin and they always seem to be aligned.
Its not that one post is weeks behind and just got missed in a federation update. Its that zero posts have been federated in weeks. Its not a skipped record, its entirely halted.
That's very much not what the post I replied to describes. I quote:
What you are describing sounds more like you are looking at a community/magazine which hasn't been subscribed to from the other instance so, by design, posts don't clone. This is expected and intended behaviour.
I think you misread communities as posts. The entire communities are up to weeks behind, not just certain posts from them
and no we're not talking about unsubscribed communities.