Users report a bug where their own reply is incorrectly marked as unread when the “Don’t jump to my post after I reply” preference is enabled. elijah first noticed this behavior recently and confirmed it’s reproducible only when that setting is active — though it didn’t work on try.discourse initially due to the preference being ignored there. After troubleshooting, elijah provided clear steps to reproduce: enable the preference, log out/in, reply to a non-final post in a long topic, and observe the unread flag on their own post in “Latest”. jomaxro confirmed the issue persists, and Michael_Hunger emphasized its impact on high-volume communities. codinghorror requested repro steps and later suggested removing the preference entirely, jokingly noting his preference for deleting features. sam acknowledged the problem and proposed adding an “ephemeral” notification system to alert users when their post is created without navigation, since the current setting creates reading gaps. Finally, tgxworld noted the issue appears resolved after a specific commit (24ef4f7), suggesting the fix may already be in place.
Let’s say I’m tracking a topic. I’ve read everything in it, and then select a post besides the last one to reply to. My own post then gets flagged as a new unread post for me in “latest” or suggested topics. But I wrote it, so I have read it.
Is this intentional behavior? I didn’t notice it happening until the last few months.
As an aside, when I try to duplicate this bug on try.discourse, I can’t. It seems like the “Don’t jump to my post after I reply” preference is ignored there, so any post jumps me to that post and it is, thus, “read”.
Yeah @xrav3nz when you get started can you have a look at this?
@codinghorror one thing we did kind of forget about over the years is an “ephemeral” notification kind of thing built into Discourse. Then when a new post happens in a topic we could quickly notify users that there was new activity without being too noisy and when you post without navigating to the post we would notify you that the post actually happened.
Note, this option “don’t jump to post” does potentially create a fair amount of reading holes which we do not deal with at all.