Lemmy.World Announcements

29099 readers

25 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email [email protected] (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 2 years ago

MODERATORS

How to prevent auto-loading of new posts? (self.lemmyworld)

submitted 1 year ago by maythebananabewithyo to c/lemmyworld

8 comments fedilink hide all child comments

Not sure if it has been mentioned, I couldn't find anything. I think one of my biggest issues is that no matter how I sort things I will scroll half way down the page then suddenly everything shifts because of posts added to the top being <1m old.

Is there anyway to prevent new post from auto-populating so i can actually make it to the bottom of a page? Or is it something janky on my end that is causing it?

you are viewing a single comment's thread
view the rest of the comments

[–] maythebananabewithyo 1 points 1 year ago (1 children)

Not on GitHub, but on the "known issue" post locally.

https://lemmy.world/comment/101300

[–] Fabulous 1 points 1 year ago

Thanks for the link!

From your link:

I found a post or two claiming that the issue is that the API is implemented using websockets only, so it’s not as simple as just turning it off. I really hope that is not the case, since I currently can’t read anything on the frontpage that takes more than a few seconds!

I also see in the GH issue that I linked there is a mention of that issue:

New posts should probably never even be added to your feed automatically. They should only change if you refresh the page.

A maintainer replied that the issue may be fixed in 0.18.0 (not sure whether it fixed both issues or only one of them though–will see I guess).