I dunno if you’ve noticed but federation between kbin and lemmy is shaky at best. By doing even a quick comparison between some original instances and their kbin pages, it is easy to see that comments and sometimes entire threads do not get synced and are practically invisible to the other side.

Has there been any official acknowledgement of this issue, an analysis done on what % of content gets lost due to these syncing errors or anything of the sort? Are these failed syncs being logged somewhere and will there be a way to retry them a later point perhaps?

I understand that we had a lot of issues in the first month after the reddit exodus and I understand this is still immature software in active development, but the traffic must have stabilized by now and I feel like just losing data like this should be the first thing to get fixed if we want to have actual faith in a federation. If we’re supposed to have different accounts for every instance in order to actually reliably get the content from there, then that kinda defeats the purpose of it after all.

  • Chris@rabbitea.rs
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    There’s this bug I have encountered and proven: https://codeberg.org/Kbin/kbin-core/issues/875 Basically other instances posting to a magazine, those posts don’t get pushed out to anybody else until interacted with (not 100% sure if it happens with comments, but you can experiment with this comment if you like)

    There’s a separate issue with kbin.social and error messages on submit, which stops those posts from federating AIUI.

    • Kaldo@kbin.socialOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Thanks for responding, that could account for part of the issues for sure. I think the majority is due to bugged domain blocking however, I found other people here talking about it when I checked it out logged off. I really don’t understand why was this left as a bug for over a month now instead of being removed or disabled if it doesn’t work properly, or at least there should have been an announcement about it >.>