"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
That is a Kbin warning letting you know that you're connecting to another server other than the one you're using, and that the community/magazine on the server you're using might be a little out of date. It then offers you a link to check out the server directly, should you wish to.
You cannot log into other servers, since the account is tied to kbin.social for the time being, and if you want an account elsewhere, you will have to register one there.
I do not believe that it is possible to remove thst warning just yet.
I get the point, but the prominence of it makes it look like an error. Frankly, I find it a bit anti federation, like the only reliable content is on-instance.
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.
@T156 This is very odd then; I thought this was meant to be all linked together, albeit on different servers. I didn't see any notifications for your post, I had to manually find it in my profile.
So... if I want to post anywhere else I have to sign up for more accounts, which may result in needing lots of them with different user names etc? I don't get what this federation thing is then if it's all not linked together properly. I saw the explanation that Gmail doesn't need an Outlook account to message them, yet here I do?
I also get this when I click the error-looking link: 404: FetchError: invalid json response body at http://lemmy:8536/api/v3/site? reason: Unexpected token 'T', "Timeout oc"... is not valid JSON
So… if I want to post anywhere else I have to sign up for more accounts, which may result in needing lots of them with different user names etc? I don’t get what this federation thing is then if it’s all not linked together properly. I saw the explanation that Gmail doesn’t need an Outlook account to message them, yet here I do?
It probably just takes some time. To catch up, even before errors and things come into play.
I also get this when I click the error-looking link: 404: FetchError: invalid json response body at http://lemmy:8536/api/v3/site? reason: Unexpected token ‘T’, “Timeout oc”… is not valid JSON
Yes, this server is having some problems with the latest Lemmy early update, which is probably why notifications aren't showing properly.
It's because your instance pulls content AFTER someone joins the community in another instance. You don't log in to other instances to post, you can do so in your current instance.
@ABCDE it's just telling you that having subscribed to a community on another instance after it was created there may be older posts that are not present on your instance and providing you a link to the same community on the home instance if you want to look at older/not yet federated content.
Not sure if you can turn it off though.