Don’t know if this is my fault. I’m using firefox 131 on linux.
I see Unread (1) in the page on visiting this discourse, but when I click on the tab it says there’s nothing to read.
Puzzled-ly yrs
4 Likes
I suspect that the unread message was evident Spam (or otherwise manifestly undesirable) and is removed by admins before you clicked..
If that’s the case why does the (1) reappear when I leave and come back to the discourse?
I see this too after refreshing in Chrome. It feels buggy to me.
2 Likes
I’ve seen this before. I’ve always just assumed that the “Unread” count is slightly unreliable, and not worried about it.
Moderator actions like locking a thread, or as @tjguk said removing spam, seem to confuse the unread count occasionally, as well. Someone moving threads from a topic you monitor to one you don’t is another edge case that I think affects it. If it matters to you, try clicking around a bit (I tend to check “New Messages” as well) - that sometimes clears it.
1 Like
Click on your profile button, top right, and look at what is listed there. You may find a clue as to why your have an unread count.
I see nothing obvious some hearts etc etc. I tried clicking on various of the latest threads to ensure they are muted, but also see nothing obvious. It’s not a browser based issue as I see the same behaviour in google-chrome.
Tried clearing all the cookies and logging back in. Still persists. 
I wen tthough all the ‘latest’ threads and marked normal → muted etc etc. Somehow that has cleared the problem.
I will have to look at latest for a while and check if a thread I’m interested in appears.
One problem I noticed doing this is that some threads are so long it’s quite hard to change the notification level as the page grows too long.
Side note: if there is a bug or something of the sort, it probably does not belong to discuss.python.org but rather to discourse.org, for example I found this:
I noticed this happening and scrolled through “latest” until I saw an unread notification. Once I clicked on that thread it stopped happening.
Maybe the problem is that the “unread” tab is failing to fetch information about the thread it wants to show you.
2 Likes