I’m still having the same problem.
1 Like
It takes me three openings and readings for this site to acknowledge that a post has been read.
1 Like
@skieurope, @momofboiler1, can you please try in an incognito window to see if the problem persists?
I am not having the issue this morning.
But as a general rule, if I need to do something different to navigate this site effectively - go incognito, use a different browser, etc - that’s a “you” problem, not a “me” problem.
Thanks for confirming the issue is resolved. It looks like there was a cache issue. As per our tech team, the fix was deployed so you would need to clear your cache if the issue persists. The incognito ask was to determine if this is indeed a catching issue or a problem with the fix.
1 Like
When I logged onto the site from incognito mode, I had six unread messages but zero notifications.
And when you read the message, did the notice disappear? Did the unread persist even after you read them?
There was no notice at all.
I spoke too soon. It’s happening again.
Perhaps they have it set up that one needs to spend X number of seconds on a post to count it as read, with X being an overly optimistic value. Just spitballing.
There is a tiny blue dot next to each post. The post is counted as “read” once that blue dot goes away.
Do you find that a realistic expectation that a moderator needs to wait until the blue dot goes away?
I don’t know if that a “realistic” expectation. It is how the platform is built to function. Plus, it’s the same for everyone, be it a mod or regular user. Just going at the end of thread does not mean you read all comments. I am not debating if that makes most sense or is the best user experience, I’m trying to identify what the issue is so I help fix it (if there is indeed one).
I read your post, counted to 10, and the blue dot is still there. My point, and then I’ll move on, is that whatever time period, which is apparently more than 15 seconds per post, is too high a threshold.