Support / questions about Lemmy.
From what I have read, I believe this behavior will change when they finish the update changing from websockets to HTML. Last I saw they said they were about 80% done so it seemingly is fairly close but that is relative as I don't know the pace of development. Then presumably you'd still have to wait for your instance to be updated.
As far as I know that's the only solution unless somehow someone made a script that prevents the page from updating.
I found another posting discussing the topic in the "Lemmy" community: https://lemmy.ml/post/1162972
I like the behavior personally but it won't scale since its keeping a websocket open for each active user. On the plus side it makes notifications pop up in real time.
But i guess I'm OK with ordinary http refresh.. And it does have advantages, like you mention. I do get a bit lost on page reload also.
I would also prefer a static feed page to scroll through. It sometimes refreshes right at the moment, when I want to click a post, so I hit something I did not intent to. It also messes up, when you read a post and use the back button up return to the feed. Often times it already moved on or you land on the top of the feed and have to scroll down again.