EDIT: After discussing this on Matrix, I believe the answer is in the mod logs. The author of the post in question was issued a temporary ban in another community on lemmy.ml, which I suspect is affecting the display of this user’s content across all of lemmy.ml even though the post in question is in a different community from the one that issued the ban (which is kinda screwy tbh).

Description of the problem

The last several months, I’ve been trying to build up the community over at !caps@lemmy.world. It’s going mostly well, but one thing that has me scratching my head lately is that when I’m browsing from lemmy.ml (i.e. https://lemmy.ml/c/caps@lemmy.world), which is 99% of the time, I can’t see the most recent post. Oddly enough, the author is also from lemmy.ml, and I have previously interacted w/ the same user in the comments of older posts, so I know it’s not a user-specific issue. I’ve double checked my profile settings and haven’t blocked the community, instance, or user. This issue seems specific to lemmy.ml because I can see it when I browse to the community from other instances.

Any ideas why this could be happening and what I can do to resolve it? Thanks.

Steps to reproduce the issue

Actual result

The post is not there.

Expected result

The post should show up in the feed.

  • Björn Tantau
    link
    fedilink
    118 days ago

    Probably due to language settings. I haven’t looked but I guess that the post in question is set to a language not in your language list.

    • @yo_scottie_ohOP
      link
      English
      118 days ago

      I hadn’t thought of that, but after a quick investigation I don’t think it has to do with language settings for a couple reasons:

      • The post in question is set to English, which I have selected in my Lemmy account settings (as well as Undefined).
      • I see other “English” posts in the same community and other communities.
      • I also see comments from this user in other posts in the same community; the comments are set to “English.”

      Any other ideas? Could this be a technical glitch of some kind?