Please don't post about US Politics. If you need to do this, try [email protected]
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Logo design credit goes to: tubbadu
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 :)
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 :)
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)
I can't seem to find an easy way to do it looking at the code base myself. Like they said, the connected websocket emits the "new post" event and then the page loads it using an ajax request. I was going to write a browser extension that blocked those requests but I feel like that will affect more than just the pop-in, so I don't wanna waste my time
Yea, it is better to wait, they are already on it. And I am unsure if he did an easy fix or just did a dirty fix that is good enough. I haven't actually checked the code and I didn't ask or check if what the instance owner said is true. I use the app instead so I am not eagerly waiting. Just happy for everyone when it will be easier for them to use lemmy
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.
