I am noticing that some comments, which are coming from users on other verified (via /instances) federated instances, do not show up on a post. For example: https://programming.dev/post/13648105

Does not show this comment on it: https://lemmy.ml/comment/10803786

Any ideas why? I checked the modlog and the comment wasn’t removed, and their post history to me does not look like someone that is likely to be banned from the instance, so I’m not sure what else it could be.

    • some_guy@lemmy.sdf.org
      2·
      7 months ago

      Oh, maybe that’s why sometimes there are more comments counted but they don’t display. So, in theory, if I find a post where that’s the case and then visit it after it’s been dormant for a while, I’d see the formerly-missing comments. I’m going to test that. I hope that’s the source.

    • refaloOP
      1·
      7 months ago

      That doesn’t show the same comment for me, it’s one of the child comments… “show context” and “view all comments” still don’t show me this comment, nor does the user’s profile page.

      • AtegonMA
        3·
        7 months ago

        The comment language is set to german, do you have that disabled in your language settings?

  • OpenStars@discuss.onlineEnglish
    4·
    7 months ago

    https://feddit.de/ returns a server error, so it is a problem with the federation - i.e. lemmy.ml was able to pull the comment at some point, but programming.dev could not.

    Federation issues like this are common in my experience, but ofc ymmv bc it depends heavily on from where to where. e.g. I am using my discuss.online account rather than my startrek.website one for similar reasons, where the latter server often randomly fails to receive or to post something lately.

    • refaloOP
      1·
      7 months ago

      How is the index page returning an error indicative of federation problems?

  • some_guy@lemmy.sdf.org
    2·
    7 months ago

    I’ve been experiencing the same for a few months now. There was one that I found in my replies that didn’t show up in the original thread on my instance. I thought someone must have been aware and it’d get fixed, but maybe it’s just going unnoticed by most people.