Ok, this is a weird problem I’ve had happened twice now. I make a post (one was to a kbin magazine, one to a lemmy community), and I’ll get notifications that there are comments. But when I go to the post to look at them, it will say “5 comments” but show none of them and say there are no comments. But, if I log out, I can see the comments. If I log back in, they’re gone. I’ve tried in different browsers (Safari and Firefox) and had the same issue.

If it was once, I’d think it was a fluke, but it’s twice now, and on different federated sites.

        • e569668@fedia.io
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          One more question if you wouldn’t mind, do you happen to remember if you got an error while posting this thread? Understandable if you don’t; one of the newer kbinmeta posts mentioned getting an error while posting and their thread doesn’t have a domain, but a different thread they posted afterwards does have a domain, so I’m trying to see if there’s a link between getting an error when posting and a post not having a domain

          • stopthatgirl7@kbin.socialOP
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            Also, I wonder if the null domain thing is causing another issue I just had pop up?

            I tried to post from kbin to a lemmy server, and got an error message. The odd thing is, the post shows up on kbin when I go to the community page, but it does not show up on lemmy. I took a screen cap of the error when I had it happen twice. For both, it was a new thread, so no link, so there’s no domain.

            Here’s the post on kbin: https://kbin.social/m/baldurs_gate_3@lemmy.world/t/375681/The-toughest-part-of-the-game

            But if you browse the community on Lemmy, it’s not there: https://lemmy.world/c/baldurs_gate_3?dataType=Post&page=1&sort=New

            Posts with links have gone through just fine, but the null-domain one did not.

            • e569668@fedia.io
              link
              fedilink
              arrow-up
              0
              ·
              1 year ago

              Believe you’re correct. I think cooperaj mentioned it in the issue but they experienced the same thing, when you get the error it does not appear to federate.

              It being interacted with, such a upvoting or boosting might make it federate after that. (I think this might actually be linked to https://codeberg.org/Kbin/kbin-core/issues/875 but am holding off without more proof.) Of course, it being interacted with to get it to federate is difficult on kbin.social where anyone who blocks any domains won’t even see it in the first place :(

              • stopthatgirl7@kbin.socialOP
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                1 year ago

                I have a beehaw account; I can try searching for it on beehaw and if interacting with that way helps it federate.

                Edit: wow, that super did not work. Searching for the federated kbin link returned this.

                • e569668@fedia.io
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 year ago

                  I don’t think you have to do anything that extreme, that is, you could just upvote your own post (and if you don’t want to do that, un-upvote it as well, haha). Although… I just clicked the link and lemmy.world appears to be down, at least when I tried, so maybe now isn’t the best time to try to post something to them >.> (edit: actually worked right after that, guess it’s just a bit spotty)

                  • stopthatgirl7@kbin.socialOP
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    1 year ago

                    Upvoting it didn’t work (neither did searching for it on Mastodon, but that did at least pull up the post, unlike the fail of trying to search for it through beehaw), but adding a comment did. Now it’s visible on lemmy.

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

            There was an error message, yes. I can’t remember if I got it on the image post, but I did get one when posting this one.

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

              But! I did get an error posting an image when I saw this post having the issue I was talking about - I posted the screenshot from my iPad as a new image post, and it gave me the same error message. I remember because I went to check to see if it had actually posted after seeing it by going to my profile. I saw the post there, but didn’t see it on the magazine page, and then deleted the post since it was having the same problem so would have been pointless.

      • e569668@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Thanks; it at least appears to match the pattern I’ve just updated the issue with, which is posts with no domain shown in parentheses next to the title get filtered out by any domain block at all, regardless of what it is. I assumed you could only achieve this with text posts but it’s good to know it’s possible with image posts as well