I’ve been reading, of course, Mike Russo’s Let’s Play: Counterfeit Monkey. But the issue is, if I open the post, read part of it, and then move on to other things, Discourse assumes I read the entire post and jumps me down to the bottom, where it presumes the next unread post is (spoilers!). Is there a way to prevent this?
1 Like
That shouldn’t be happening - one of Discourse’s main features is it is supposed to remember where you’ve read. Assuming you have no severe cookie-blocking or browser security feature interfering, make sure you’re not clicking the bottom of the timeline and jumping to the end - in that case there’s a temporary “back” button where you started from.
Are you accessing your account from different devices that might be doing weird things to your read pointers?
If you keep the forum open all the time, you might want to close and re-open it, or log out and back in if you haven’t tried that yet.
Here’s Discourse Meta’s usual on-brand philosophy…
1 Like
I suspect this is about reading half a post and then coming back later to read the other half. (The CM thread has very long update posts.)
4 Likes
Yeah. I’d read part of the post (not the thread) and then when the page reloads I’d be at the bottom of the post. Sometimes then the next post is short enough that Discourse assumes I’d read it too so it moves me down even more.
1 Like
Only about a third of them hit the character limit!
(But yes, pretty sure that’s what’s going on).
3 Likes
this is a hacky solution but if you save the link to the post and put the url in your browser again, it’ll send you to the top of the post. eta: actually, since the url changes as you scroll posts, you can just refresh on the correct url and it’ll work the same.
I popped into this thread I haven’t looked at since last year. Look for the “last visit” line.
That makes total sense. If you watch how the URL changes as you scroll, it’s remembering the last post you “saw”, and if it’s a skyscraper Discourse is not recording where you were within the post. It knows you looked at it and expects you’ll want to continue on.
Right, so the question is whether there’s a way to manually circumvent that behavior. I’ve been resorting to leaving the CM thread open in a separate tab, which is not ideal.
Me too, but if the page reloads I have the same issue.
It looks like there really isn’t a good solution. Thank you everyone for your help!
I felt like my solution was alright 
2 Likes
I’d rather not copy/paste a URL just to reload it. Mine doesn’t do what yours seems to. But yes, that is a solution, just not one that I like haha
1 Like
the gif wasn’t me copying the url, it was just refreshing the page, but alright