Feed gets randomly filled with new posts

When going through the post feed, I'll randomly get 5-10 new posts added to the top of the feed. These 5-10 posts are all new with 1 or 2 upvotes only. Sometimes all from the same community.

This happens on local, subscribed, or all feeds. It also doesn't matter what sorting option is selected.

Is this a known issue or an expected behavior?

11 points · 17 comments · view on lemmy.world

17 Comments

SmokeInFog@midwest.social · 7 pts · 3y

This happens to me a couple times a day

CannotSleep420@lemmygrad.ml · 5 pts · 3y (3 replies)

I think this has to do with websockets fuckery. It should hopefully be fixed when only HTTP is being used.

ImOnADiet@lemmygrad.ml · 4 pts · 3y (2 replies)

You've really gotta check their instances the OP can't see your comment on this one either (I feel like I've left this comment to you like 3 times now lmao)

CannotSleep420@lemmygrad.ml · 5 pts · 3y (1 reply)

Damn, everyone blocks lemmygrad.

ImOnADiet@lemmygrad.ml · 1 pts · 3y

yep, not literally everyone but if it's not a lemmy.ml or lemmygrad user you need to check their instance block list :/

sexy_peach@feddit.de · 4 pts · 3y (4 replies)

https://feddit.de/post/739125

I have this bug too. Don't know if someone reported it on GitHub, but it's been reported multiple times in the lemmy support community.

SmugBedBug@sh.itjust.works · 2 pts · 3y (3 replies)

Oh wow. Good that they were able to record it while it happened.

sexy_peach@feddit.de · 2 pts · 3y (2 replies)

I just ran a screen recorder and waited a few minutes until it happened again, then cut the waiting part of the video.

poVoq@slrpnk.net · 4 pts · 3y (1 reply)

I hope this gets fixed as a side effect of the upcoming removal of the websocket connection.

sexy_peach@feddit.de · 2 pts · 3y

Yes that's exactly what I've been hoping!!

Acester47@lemmy.ml · 4 pts · 3y

Me too. I read it was a known bug but I don't have the link handy. I hope it's fixed soon

such_lettuce7970@beehaw.org · 2 pts · 3y (2 replies)

It's a known bug. If you're using Firefox on desktop like I am, going to about:config and setting "accessibility.blockautorefresh" to "true" seems to be a workaround.

edit: doesn't work

SmugBedBug@sh.itjust.works · 2 pts · 3y (1 reply)

Thank you for this!

such_lettuce7970@beehaw.org · 1 pts · 3y

It helps a lot doesn't seem to stop it completely though.

edit: speak of the devil, I just got hit hard by the bug again. Sigh. Guess this solution doesn't work.

therealraluvy95@beehaw.org · -3 pts · 3y

One word: Enshittification