this post was submitted on 03 Jul 2023
42 points (100.0% liked)
/kbin meta
2 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I see it as a just-in-case message, to let you know that you're browsing a non-kbin community and that some federation features may break on either side, even if they are not broken at the moment. There may also be some differences in how posts and comments are sorted between kbin and the original instance, and - I'm not sure if that's exactly how it works - potentially you may see different comments depending on who the two instances federate with.
I think the main issue is that I'm not getting all comments or posts from the other magazine, even though all the posts and comments are from that same magazine (but on the other instance). There might be some delay involved and that it sooner or later will retrieve them as older posts seems to have more comments on them.
Keep in mind that some instances might just not be federating with kbin. If they did in the past, then I imagine their magazine remains available on kbin but no new posts or comments will appear from the defederated instance. Not sure if that's how it works though, just my assumption.
In particular, I don't know if lemmy.ml is still blocking kbin, but don't be surprised if their posts won't appear.
Yes, but this is regarding magazines from e.g. lemmy.world, which to my knowledge is not defederating from kbin.