I ask because I made an account on https://lemmy.zip and the kbin.social magazines there seems to have incomplete contents. e.g. kbinMeta@kbin.social there only have one thread from 25 days ago. RedditMigration@kbin.social there seemed more up-to-date but number of comments are still less than what I can see directly on kbin.social.

Another indication of trouble is that when I try to subscribe to a kbin.social magazine (like kbinMeta@kbin.social) it is stuck on Subscribe Pending seemingly forever and does not transition to subscribed/joined status.

At first I thought it is a configuration problem on lemmy.zip or some recent version Lemmy incompatibility with kbin, but I was able to subscribe to fedia@fedia.io there fine and it seems to be getting updated contents.

So somehow traffic is not flowing smoothly between kbin.social and lemmy.zip.

@ernest, I hate to bother you but are you seeing something like this with other instances?

  • 1Fuji2Taka3Nasubi@kbin.socialOP
    2·
    1 year ago

    Thank you for looking into it. I tried subscribing again and it went through, and several threads just got through to kbinMeta over there, so I’ll cautiously say it seems to be fixed now.

    Glad to hear federation is being worked on, it does feel it needs to be more robust to live up to the promise that one gets the same experience no matter which instance (local or remote) one view a magazine from. (I’m not being critical, interoperability is always a hard problem no matter which stage of development it is)

    Again, thanks for the good work and for bringing kbin to us!

    • ernest@kbin.social
      9·
      1 year ago

      Actually, I have a plan to improve the federation, but at this scale, I need to be super cautious. Just one mistake is enough to harm other instances. That’s why I want to prioritize setting up robust testing environments first, so that the every changes in this regard are thoroughly checked and validated.