this post was submitted on 03 Jul 2024
25 points (96.3% liked)
Technology
37719 readers
79 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The mechanism for how it works is that as a remote instance sends in it's downvote count, Beehaw immediately drops the message without modifying the database. Part of this exchange is an expected response of the total updated downvotes. However, Beehaw sends back "0" and the remote instance knows it can't be zero, so it treats it's local count with higher validity.
Essentially, this all ends up meaning that what ssm will see is the total of all downvotes from users on their own instance, and nothing else. This might be just their own downvote, especially being on a smaller instance. But I've seen lemmy.world users be confused about it bc the count they see is say, -5. Have been told my instance obviously has them enabled 😅
Remote instances don't communicate their vote tally's with each other for a third instance's post.