lemmy.world seems to be unique in that it's allowing post pop-in. Another lemmy instance I checked doesn't have this, so how can I prevent it? It's literally making the site unusable for me...
10 comments
It's not unique to lemmy.world, every instance has this problem. I run my own instance and I'm seeing the same issue.
It's caused by Lemmy's websockets implementation. It will probably be fixed in Lemmy v0.18. Bear with it for now, Lemmy will improve over time :)
my polish friend uses szmer.info and he says there is no pop-in, I don't speak polish so I don't use that site so I can't confirm...
I saw another thread where an instance owner said he had done a fixe for it himself until the fix comes out by the lemmy dev team. So maybe the same thing? I sadly do not remember the instance name (it was pretty off topic)
Do they have an ETA for the fix? I've had several people I know quit Lemmy because they were frustrated by it. I'd hate for it to be a reason to prevent people from migrating.
It's an open source project, so there are no timelines and no ETAs.
But, I can tell you they are actively working on it. If you, or someone you know, can help out with the code, they are always accepting PRs :)
forgive my ignorance, but what's "pop-in" in this context?
When on the main aggregator page if you stay scrolled at the top long enough, new posts will "pop-in" and push the rest of the posts down. This also closes any open post (image, text posts). If you have it set to "All" then it gets really crazy, I had like 5 posts per second loading with "Hot" sorting...
I propose the much more accurate name Automatic Self Scroll, or ASS for short.
It's not unique to lemmy.world, every instance has this problem. I run my own instance and I'm seeing the same issue.
It's caused by Lemmy's websockets implementation. It will probably be fixed in Lemmy v0.18. Bear with it for now, Lemmy will improve over time :)
my polish friend uses szmer.info and he says there is no pop-in, I don't speak polish so I don't use that site so I can't confirm...
I saw another thread where an instance owner said he had done a fixe for it himself until the fix comes out by the lemmy dev team. So maybe the same thing? I sadly do not remember the instance name (it was pretty off topic)
Do they have an ETA for the fix? I've had several people I know quit Lemmy because they were frustrated by it. I'd hate for it to be a reason to prevent people from migrating.
It's an open source project, so there are no timelines and no ETAs.
But, I can tell you they are actively working on it. If you, or someone you know, can help out with the code, they are always accepting PRs :)