The constant stream of new posts makes scrolling/browsing unusable.

https://sh.itjust.works/post/95822

The constant stream of new posts makes scrolling/browsing unusable. - sh.itjust.works

Has anybody figured out a workaround or fix for this? The behavior I’m describing is when sorting by All > anything (top, hot, whatever) you get a feed. Great! I start scrolling and then the page jumps. Then jumps again. And again and again and again… it makes trying to actually preview or click anything a nightmare. Scrolling back to the top of the page shows why - a ton of new posts from across the Fediverse are up there! But I’m not sorting by New, so what gives?

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

This is from websocket. Will be removed in 0.18.0

Good to know, thanks!
I have two ideas. First, I haven't had the jumps on Jerboa; I only see jumps using my browser. Second, I didnt see the jumps when sorting by top. I honestly still enjoy sorting by top as default, even on Jerboa.

Yeah, they’re still there for me even when sorting by top, unfortunately.

And I can’t use Jerboa because I’m on an iPad (which also makes the Mlem client problematic for now, they don’t have iPad scaling yet - but I can confirm that the problem does not occur in the app)

So that leaves me with the good ol’ webpage. /sad (lol)

That’s ok though! I understand it’s early days for Lemmy, and the fix is on the way! I can be patient to kick Reddit squarely in the nuts 😁

https://testflight.apple.com/join/6jaRU6rD

There’s a new one.

I just installed it and I can’t seem to reply to comments on the app and I can’t seem to make a post. Am I overlooking something or does it not have those features yet?
Currently replying from Memmy (the new app linked). Replying, along with voting on comments, is done by swiping. Not sure if there’s another way to do it yet
I see this all the time on the web page for new posts. My solution: fight my way to the bottom of the page, then click "Next". That page won't automatically refresh.
I do the same! And that seems to do the trick indeed.
There's allegedly a patch rolling out soon for this. It's a known bug.