Recently, I have noticed that when I make a post anywhere on the fediverse, I am no longer able to see that post, or any comments in it. If someone does post a comment, I will get the notification, and will be able to see the first few words of the comment, but if I click on the notification to see the full thread, it’ll not show up.

Feel free to post comments in this thread all you want. However, if you want to reply directly to me, you’ll probably have to use a DM, because otherwise I won’t be able to see your full comment or reply to it.

And if none of that is an issue today, and my post doesn’t disappear after I post it…well, then, hooray!

    • CarlsIII@kbin.socialOP
      4·
      1 year ago

      Strangely, that fixed it.

      So thank you, but now I might have to see stuff from those problematic instances, so, kind of a lateral move I guess.

      • FfaerieOxide@kbin.social
        4·
        1 year ago

        I know, it’s weird. And if you post a new image it should say “We are working on the issue” but the image will still post.

      • ryan@the.coolest.zone
        2·
        1 year ago

        It’s related to this issue: https://codeberg.org/Kbin/kbin-core/issues/1019

        Also, this appears to be very kbin.social specific at the moment at least. I went around and checked kbin.cafe, kbin.melroy.org, fedia.io; disabled federation on each but all of them had their own domains shown for local posts. It seems only kbin.social is currently stripping domains from new posts made to kbin.social, causing the inability for any kbin.social users to view those posts if they block any domain (to clarify, this affects kbin.social posts FOR kbin.social users. You won’t be able to see this issue from a remote instance, as the posts do show as the domain kbin.social over on say, fedia.io. It’s only on kbin.social that posts to kbin.social are losing the domain)

        Basically, this was fixed in the source code a month ago, but kbin.social itself (the only instance experiencing this issue) doesn’t have the fix loaded in yet.