I have the opposite issue. I joined a local community and could see all posts. Then I posted something myself, and now I can only see my own post. If I use incognito I see them all, my own included.
this post was submitted on 14 Jun 2023
1 points (100.0% liked)
Ask Lemmy
26279 readers
1652 users here now
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
founded 1 year ago
MODERATORS
Incognito and then logging in with my account lets me see them as well. Even if I have all the same extensions available in incognito mode.
I was unable to see my own posts until I checked "show read posts". I take it you're on desktop? Try clearing your cache; since incognito shows the posts, that suggests either a caching issue or a plugin/extension conflict, and the former is more likely.