As the title said, I’ going through the feed and new posts are adding pushing what I read down, which is annoying, is there a way to stop this?
Very soon (within a couple days) this feature will be disabled, which will also greatly improve performance. You can follow progress here: https://github.com/LemmyNet/lemmy-ui/pull/1081 For the future, this sort of question is better for !lemmy_support@lemmy.ml
Thanks you! That’s great news
The changes might get merged into the codebase in a couple of days, but it’ll take a while longer for a release to be made and each instance to upgrade their software.
This is true, though many instances are quite bleeding edge at the moment
Yeah definitely not a fan of that either. Sure hope they remove it in a future version.
It’ll stop soon. The Devs are currently pushing through a big UI rework that changes the way the frontend communicates with the backend. Once that’s released and your instance updates, the auto-refreshing will end.
let us know if you find a way, I’m not a fan of it either
I’ve found that if you change the Sort Type (at the top of the web ui) to either Hot or Active, it slows down or stops the screen refresh. There should also be a way in your profile settings to make either of these your default.
Still learning it myself, so there may be better answers out there…
Just adding my agreement to this post it would be nice to toggle it off or have a button at the top to click when new posts are ready to be loaded
I use an apk for android called Thunder. This doesn’t happen for me.
I don’t have an answer I’m afraid, but I’d like to know that too! Upvoted
I don’t know, but I just tried turning off javascript in ublockorigin and then I noticed the username in top right wasn’t mine. Weird
Change the sort setting at the top from active to something else like Top.
I’m new here as all of us. but if you don’t sort by new you won’t get the feed being refreshed all the time. you might want to play with the sorting and report back
Nope even with top I’m getting them but it should solved soon
It’s a bug. There’s a GitHub issue for it, although I don’t have a link. It’s floating around on here if you look or you could go through the issue tracker.
