As was mentioned this is a known bug. Itβs always existed but was easy to not notice when there were only dozens of contributors. Now that those dozens have turned into ten of thousands virtually overnight itβs a much higher concern.
post
Mastodon has a good solution for this where the user can choose between continuous scrolling updates and manually updating the feed. Would be good to have a similar option here.
Besides that I also feel like it has to do with the way lemmy gets new content from other server. I've noticed a downpour of post from the same sub on the new feed happening all at once several times now. With some of the posts already being several hours old.
If you're on Android you can use Jerboa. It doesn't do that.
if i understand correctly it's a known bug thats going to be fixed
That entry says that a recent update should have fixed it, yet it's obviously still happening.
They're saying that the issue is fixed in the next release that's coming out (0.18). Right now the stable version everyone's using is (0.17.4)
0.18 is only in release candidate stage so isn't in a final version yet. And the instances themselves won't necessarily immediately to jump to the new version I would suspect.
Yeah this has been greatly annoying me as well. It's not a problem on Jerboa though and I find myself just using that more often now.
Hopefully it'll be fixed with the next update!
Try sorting by daily top as a workaround until this gets properly fixed.
This must be a Lemmy thing right? I havenβt experienced this at all on kbin.
I think the issue is that the scroll is also updated when the posts list is updated. They need to implement this like twitter where new posts are loaded from above and not the whole page ever X seconds.
top 21 comments