Bottom of topic shows "There is 1 unread remaining" when there are actually 0 unread topics remaining

[ganncamp (G Ann Campbell)]

Was composing this followup:

This seems… to be fixed. I haven’t noticed these self-notifications for a week or so…

When I got a “See X new or updated topic” notification at the top of the Latest list, clicked it, and got more self-notifications. :-/

For the record, I updated threads in previously opened tabs, and landed back at my Latest list (my personal hompeage). No self-notifications.
When to New and back to Latest to check. self-notifications.

Began composing this update & got the blue “new or updated topic” notification in my still-open other window. Clicked it & bam self-notifications.

[glimfeather]

See this all the time on the half dozen Discourse sites I’m on although the numbers vary. Have even seen it here!

And right when I need some “proof” this counter example came along.

[glimfeather]

Another example but as my previous two posts were merged I cannot add it directly. This one is from a certain Discourse installation.

[ganncamp (G Ann Campbell)]

Posting here because it seems related.
Topic list here on Meta says there are 168 new posts in the thread:

But most of them have been cleaned out, so there’s only one:

[JammyDodger]

I’ve reported this before too, but I was pointed to this post:

Number of unread replies is different than number of topic replies due to reply deletions

We have had this reported a few times before, it is fiendishly hard to fix. If a large number of posts are deleted then unread count is artificially incredibly high. We could I guess do a client fix that caps numbers but it just replaces imperfect with more imperfect. Problem with counting deleted replies is that there is no cheap way of do it. You may have read 17 of the 32 deleted replies.

[glimfeather]

I’m coming to the conclusion that this type of error is caused by using multiple systems to access the same Discourse install. I regularly switch between my desktop Mac and my MacBookPro when accessing varions Discourse incarnations (up to 12 at the moment reflecting my professional and hobbyist interests where I see this error on all of them) and Unread/New counts are never accurate. Wondering whether the serviceworker.js script is at fault and not coded to cope with such user behaviours.

[Sevencasper]

For some time (over 6 months) I have been having this problem and these issues also (using windows 11 and edge browser (Version 113.0.1774.42 (Official build) (64-bit)) :

Discourse jumps back 20 posts in post history when navigating to new topic

Recently our users have noticed (myself included) that sometimes when navigating to a new topic Discourse will jump back 20 posts (consistently 20) in post history. It’s driving people crazy. We are on the latest version of Discourse as of today and it’s still happening. We have people reporting this with Safari, Chrome, and Firefox. Any help is appreciated.

I initially thought it was from switching between my phone and pc but it continued after I stopped using the phone to access the forum.
I posted about it on the forum where it was occurring and it was suggested to try a different browser (der).

I have changed to Firefox browser (Version 113.0.1 64 bit) and all my issues with discourse forums have resolved.

[wmamrak]

This issue has been reported by several users of our community recently. We are on the latest version (3.4.0.beta3-dev (45ecb34aec)).