Yeah, at worst it’s a necessary evil to prevent a rogue user on a second instance from mass downvoting. Your username is tied to your vote, because otherwise a rogue user could just spam downvotes at whatever they didn’t like.
Instance 1 has a post. Instance 2 has a user who disagrees with that post. User is able to spam downvotes, because instance 2 is not binding their username to the vote. So Instance 1 has no way of knowing if the votes are multiple different users, or all one user. The only real solution here is to disable external voting, but the entire point of the fediverse is cross-compatibility and self-hosting. By binding the username to the vote, instance 1 is able to detect repeat votes and disregard them.
irelephant@lemmy.dbzer0.com 2 months ago
lemvotes.org
LemmyThinkAboutThat@lemmy.myserv.one 2 months ago
irelephant@lemmy.dbzer0.com 2 months ago
Sure, but how many people have read the docs?
LemmyThinkAboutThat@lemmy.myserv.one 2 months ago
🤦🏻♀️okay, good point.
InFerNo@lemmy.ml 2 months ago
This always givea me a 404
rumba@lemmy.zip 2 months ago
Just tested your post here, your instance def opted out.
irelephant@lemmy.dbzer0.com 2 months ago
your instance may have opted out.
Obi@sopuli.xyz 2 months ago
Or just buggy results.