“The magazine from the federated server may be incomplete. Browse more on the original instance.” - why does this appear and how can I turn it off? I cannot log in to other servers to post
“The magazine from the federated server may be incomplete. Browse more on the original instance.” - why does this appear and how can I turn it off? I cannot log in to other servers to post
It’s probably meant to head off complaints/issues about posts/comments that are missing if a user go to a server, but it hasn’t synced with kbin completely yet.
Not entirely sure if it’s simply due to Lemmy servers not being Kbin servers, so there’s a slight mismatch/synchronisation delay going on, but that’s also not out of the realm of possibility.
As I say, I get the point, but it is not presented as a helpful note, but as a failure warning. And to be honest, maybe that’s the reality of the situation…
I’m working on a bot for baseball game day threads, and part of my testing is checking out the synchronization between instances. How long do edits take to sync? Comments? Should I reduce my update time to improve the reliability? etc.
The synchronization between two lemmy instances (fanaticus.social and lemmy.world) is almost instantaneous. I can’t even get kbin.social or fedia.io to acknowledge the existence of fanaticus.social. Meanwhile, a community on lemmy.world that did manage to get federated to kbin.social is missing most of the posts in that community.
Kbin and Lemmy both need to do a better job with error handling and reporting, specifically with respect to federation. If the method for me to federate is to search for a community, returning “not found” is not acceptable. If the instance is blocked (or not whitelisted), it should tell me. If the server is starting federation and I just need to wait a while, it should tell me. Honestly, the only reason I’m using Lemmy over Kbin is that it is (mostly) working. Kbin appears to be way too focused on being monolithic, and I see federation as the heart of what makes this platform work.