/kbin meta

16 readers

2 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

What's up with "The magazine from the federated server may be incomplete. Browse more on the original instance."? Is this working as intended or is it a bug? (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by Treedrake@kbin.social to c/kbinMeta@kbin.social

26 comments fedilink hide all child comments

I've been seeing this for quite a bit, and thought it'd resolve itself once CloudFlare was taken off, but I'm still seeing it on many external communities from e.g. Lemmy. Not all posts or comments are visible from Kbin. Any idea on what's going on?

Edit, clarification: when I visit e.g., https://kbin.social/m/technology@beehaw.org the above mentioned sentence shows up, and I'm not able to see threads created even 13 hrs ago, like this one on the original instance https://beehaw.org/post/927935?scrollToComments=true. New content doesn't seem to be pushed to this instance at kbin.social. This is the issue I'm referring to.

Edit 2: This is probably the answer: https://kbin.social/m/kbinMeta/t/131241/What-s-up-with-The-magazine-from-the-federated-server-may#entry-comment-517045

you are viewing a single comment's thread
view the rest of the comments

[–] LexaPrime@kbin.social 6 points 1 year ago (1 children)

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.

[–] Treedrake@kbin.social 4 points 1 year ago (1 children)

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.

[–] Pamasich@kbin.social 3 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] Treedrake@kbin.social 3 points 1 year ago

Yes, but this is regarding magazines from e.g. lemmy.world, which to my knowledge is not defederating from kbin.