Disable autorefresh while scrolling?

3 years ago by menachem to c/lemmy_support

I'm trying to view Lemmy from the browser but have already seen most of the posts at the top, so to get new stuff I'm trying to look at all communities sorted by new. But as I scroll down the page keeps refreshing the posts automatically and pushing stuff I've already scrolled past into view again, and sometimes causing misclicks. Is there a way to disable that so I only get new posts when I refresh the page?

This problem is only going to get worse if the site gets busier.

kiwi 14 points 3 years ago

The lemmy ui is removing websockets in the next update replacing it with a REST API. I suspect that will stop any new posts from popping to the top after load.

People seem to not want new posts and comments moving things around on their page anyway.

https://github.com/LemmyNet/lemmy/issues/2841

path: 0 38016, hotness: undefined, score: 14, children: 0
sexy_peach 4 points 3 years ago

There is no auto refreshing, it probably is this behavior, which is a bug. Might get fixed with the next update, if we're lucky :)

path: 0 37842, hotness: undefined, score: 4, children: 9
menachem 3 points 3 years ago

I don't think it's the same thing. It looks like that user is watching the site reload the entire list, and inaccurately at that (they're looking at all by new but seeing days old posts in between minutes old ones?). What's happening to me is that if I just sit at the top of the page I can watch as new posts come in live, one at a time. Which sounds cool in theory, but really hurts the browsing experience!

path: 0 37842 37959, hotness: undefined, score: 3, children: 8
sexy_peach 3 points 3 years ago

Okay I see so it really is auto refreshing. I don't think there's a fix for that at the moment. The problem, that posts are coming in too fast always was a far away wish on lemmy xD

path: 0 37842 37959 37990, hotness: undefined, score: 3, children: 7
Menachem 2 points 3 years ago

That's concerning. There'll be a ton of problems like that if Lemmy actually sees a mass migration happen. Top of the list: what's stopping people from vote brigading posts with accounts from different instances? I've had to create 3 of them just to be able to consistently access the site as the first one didn't work and the second (this one) saw excessive loading times for a few hours.

path: 0 37842 37959 37990 38334, hotness: undefined, score: 2, children: 4
sexy_peach 1 point 3 years ago

Also unfortunately lemmy is still fairly beta software. We only have two full times devs and it's not been long ago that they were implementing some of the standard features we're using today.

We have to work with what we have.

path: 0 37842 37959 37990 38334 38378, hotness: undefined, score: 1, children: 0
sexy_peach 1 point 3 years ago

Top of the list: what’s stopping people from vote brigading posts with accounts from different instances?

I've had different reddit accounts as well, wouldn't this work there as well?

In short, nothing. Admins could check from which the votes are coming from and block that badly moderated server.

path: 0 37842 37959 37990 38334 38345, hotness: undefined, score: 1, children: 2
borari 0 points 3 years ago

So I just noticed this behavior while sitting at the top of the All/New feed on my instance. I noticed that the surge of "new" posts that came in were all pretty old, and all from one or two communities on another instance. I'm now wondering if maybe there's some sort of race condition going on with the interaction between the database and the front-end, where these old posts are being considered "new" when they're initially pulled in to the local instance db.

path: 0 37842 37959 37990 38229, hotness: undefined, score: 0, children: 1
sexy_peach 2 points 3 years ago

when they’re initially pulled in to the local instance db.

I know this, these posts are not pulled initially. Many times I have seen this with old posts that I had seen and voted on months ago.

Soon lemmy will get html posts instead of websocket, I think that might fix it??

path: 0 37842 37959 37990 38229 38262, hotness: undefined, score: 2, children: 0
lemmy_support

@lemmy.ml

login for more options
5112
1594
84

Support / questions about Lemmy.

Matrix Space: #lemmy-space

go to feed...