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.

  • e569668@fedia.io
    2·
    10 months ago

    Check out https://codeberg.org/Kbin/kbin-core/issues/1019#issuecomment-1064117 and https://kbin.social/m/kbinMeta/t/361909/-/comment/1870631 as well.

    I think when people get an error posting to kbin.social a text or photo post it doesn’t federate until, as floppy / stopthatgirl7 mentioned, it is interacted with.

    Edit: After reading your replies closer I see you were already aware, my bad for repeating information. There is a PR pending for the blocked domains so hopefully that is resolves soon

  • Kaldo@kbin.socialOP
    1·
    10 months ago

    Sorry for tagging @ernest (https://kbin.social/u/ernest ?) but I am not even sure if this thread is visible to other people now. I got an error while submitting it, I see it in my profile overview but it is not listed in the Threads tab. It is also not visible for me on https://kbin.social/m/kbinMeta/newest unless I log out with my account, which is similar to an issue I had on another instance when me and another other kbin users couldn’t see a thread there while the admin there could, but that was over a month ago.

    At this point I’m not sure if these are known issues, if it is somehow just an issue with some few select accounts or if it’s just bad luck with threads, but I’m hoping there’s an official stance or plan for it.

    • Chris@rabbitea.rsEnglish
      1·
      10 months 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
        1·
        10 months 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 >.>