Feed gets randomly filled with new posts

3 years ago by SmugBedBug to c/lemmy_support

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?

SmokeInFog 7 points 3 years ago

This happens to me a couple times a day

save

path: 0 24832, hotness: undefined, score: 7, children: 0

CannotSleep420 5 points 3 years ago

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

save

path: 0 24907, hotness: undefined, score: 5, children: 3

ImOnADiet 4 points 3 years ago

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)

save

path: 0 24907 25272, hotness: undefined, score: 4, children: 2

CannotSleep420 5 points 3 years ago

Damn, everyone blocks lemmygrad.

save

path: 0 24907 25272 25432, hotness: undefined, score: 5, children: 1

ImOnADiet 1 point 3 years ago

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

save

path: 0 24907 25272 25432 25442, hotness: undefined, score: 1, children: 0

sexy_peach 4 points 3 years ago

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.

save

path: 0 25103, hotness: undefined, score: 4, children: 4

SmugBedBug 2 points 3 years ago

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

save

path: 0 25103 25309, hotness: undefined, score: 2, children: 3

sexy_peach 2 points 3 years ago

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

save

path: 0 25103 25309 25321, hotness: undefined, score: 2, children: 2

poVoq 4 points 3 years ago

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

save

path: 0 25103 25309 25321 25364, hotness: undefined, score: 4, children: 1

sexy_peach 2 points 3 years ago

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

save

path: 0 25103 25309 25321 25364 25371, hotness: undefined, score: 2, children: 0

Acester47 4 points 3 years ago

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

save

path: 0 25015, hotness: undefined, score: 4, children: 0

such_lettuce7970 2 points 3 years ago

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

save

path: 0 33109, hotness: undefined, score: 2, children: 2

SmugBedBug 2 points 3 years ago

Thank you for this!

save

path: 0 33109 33111, hotness: undefined, score: 2, children: 1

such_lettuce7970 1 point 3 years ago

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.

save

path: 0 33109 33111 34228, hotness: undefined, score: 1, children: 0