I keep noticing three very strange happenings here:
- Upvotes going wild for a bit before settling on the wrong values.
- Posts sometimes refreshing showing the contents of an entirely different post.
- Whatever this is where I’m viewing https://lemmy.world/post/163272, but it’s showing me a removed pornographic post with the comments from https://lemmy.world/post/163272
It’s caused by Lemmy-UI’s websockets client. It does weird stuff like this when the site is under heavy load (we broke Lemmy!)
It’s being removed in Lemmy 0.18 and being replaced with a more stable http client. No word on when that will release, but it looks like progress is being made fast.
Sources:
https://github.com/LemmyNet/lemmy/issues/3008#issuecomment-1588120660
https://github.com/LemmyNet/lemmy-ui/commit/2b1af707c3df6126b3e6890106c03c60ad49b1be
I’m looking forward to it so much, aside from fixing a ton of bugs it should make Lemmy MUCH more stable and lighter in the server-side because they don’t keep sending data constantly.
Yeah if you open the developer console, you can see the messages it’s sending (they log it to the console). Every vote, regardless of whether or not you have that post open or not, is sent to the client.
Regarding the wild upvote counts, Reminds me of Whose Line is it Anyway where the points don’t matter… 🤣
Meanwhile over on kbin, the points really do, in fact, not matter since comment ordering is dictated by the boost count.
Aren’t 2 and 3 the same? That’s a particularly annoying one, I’ve made some seemingly very nonsensical comments because they ended up on a different post than intended.
Tends to happen more often if you have multiple Lemmy tabs open at once. My completely uncorroborated pet theory is that the WebSocket messages get passed to the wrong tab on update.
I notice the same thing too. I have to refresh once or twice for the upvote count to be correct.
I have noticed this for sure, I have not seen any porn or offensive content yet fortunately. But I appreciate the warning, I will be careful using Lemmy in public until this is resolved.
