Same here. Just got one of those right after opening this post.
Also, just noticed the upvotes count changing frequently, like from 9 to 800+, then 400+, 100+, 800+ again. lol
this post was submitted on 13 Jun 2023
3 points (100.0% liked)
Lemmy.World Announcements
29035 readers
4 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 1 year ago
MODERATORS
The upvote jumping is caused by issues with the websocket implementation. As far as I heard they are going to get rid of websockets completely in the next version and have static page rendering instead.
Yup -- that's been reported too. It's not a great look. I've been looking at the up/down vote functionality, and it is literally triggering an INSERT to the DB every single time you click either button.
Is that because of some kind of event sourcing, though? That's not an uncommon way of handling these things.
Yes, of course it makes sense to do it that way. The issue is you can literally click the up arrow repeatedly as fast as you can and create some database load.
Usually, at least from my experience, it is good practice to put some logic client-side to prevent a user from repeatedly clicking a button accidentally (or on purpose -- hey, why did I get a double post?!). Even a quarter second delay can help.
Yeah, that kind of abuse prevention really shouldn't be client side at all. It's one thing to prevent a user accidentally causing harm, but if a bad actor can deliberately do it then we've got bigger problems.
It's a known bug, there was some talk about it on Beehaw yesterday. I've not spotted a pattern to it tbh but pretty sure it's nothing us individual users are doing wrong.