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?
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/[email protected] 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.
From what I’ve come to understand, which I am no expert, I think it means that the posts from those magazines start when someone on kbin subbed to that particular magazine. I had found a pretty small mag on Lemmy that only had maybe 5 posts when going to the original instance but after I subbed to it I would see nothing on kbin. They made 1 post after I subbed to it and that is the only post to show up on kbin, even to today even though it’s been a week or so since I subbed to it.
I had read somewhere on here that when it comes to the individual communities, kbin will only federate with that magazine after one person on here subs to it, after that anyone in kbin will see posts from that day forward.
Again, I could be very wrong, I’m just guessing based on my experience.
TLDR: the magazine only shows posts from when someone subbed forward so it will always be incomplete, I think.
I've heard this as well, but this is regarding new posts and comments not showing up. Not the old ones. And when they do show up after some unknown time, it might still be incomplete.
No, once somebody (anybody) from your instance has subscribed, all posts from the community from that point on 'should' mirror. The warning is in relation to older posts.
That said several of the Lemmy servers have been struggling with load over the last week or two (and kbin.social has occasional downtime too). Occasionally some posts might not push out to all other instances properly.