43
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jul 2023
43 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 1 year ago
I'd like to know exactly how this works as well. I've seen people say there's no real downside to joining a smaller kbin instance as you can still get to other magazines in different instances, but this seems like it would be a drawback if you can't browse old threads in a remote magazine. Or would it eventually pull all the threads in? Would be nice to know what the expected behavior is.
I've noticed that sometimes new threads from federated magazines sometimes don't show up for me in Kbin, as well as older ones. I think there may be some sort of syncing issue that causes that, perhaps Kbin refreshes data from other instances at set intervals or something.
Yes, this is the issue I'm referring to!
@Treedrake
One thing that also plays a role is the size of the queues on the different instances. Kbin.social may get things pushed to it, but with queue sizes reaching 500 thousand or more, it takes time to process them.
@Xepher @Chozo
I think it's actual data loss, not just lengthy queue times. I see new threads and comments appear but for some of the older threads, even days after they were active, I see missing comments if I compare it between kbin.social and the original instance truth.