By advantage I mean posts from those instances receiving more visibility than others on feeds that sort by score (active, hot, top).
There seems to be at least two ways in which posts from instances that don’t allow downvotes receive an advantage:
- They don’t federate downvotes. That means other instances only count downvotes from their own users but not from the rest of the fediverse.
- A downvote sometimes can be counted and federated as an upvote. This happens when you first upvote a post and then change it to a downvote.
Let’s see an example. Suppose we are a user from instance A that allows downvotes and we want to vote a post on instance B that doesn’t allow downvotes. Watch what happens on instance C that also allows downvotes.
-
Before the vote this is what users from each instance see (upvote - downvote = total score)
A: 10 - 0 = 10
B: 10 - 0 = 10
C: 10 - 0 = 10 -
Now we upvote the post:
A: 11 - 0 = 11
B: 11 - 0 = 11
C: 11 - 0 = 11 -
We misclicked, we meant to downvote the post:
A: 10 - 1 = 9
B: 11 - 0 = 11
C: 11 - 0 = 11
If the post was hosted on an instance that allowed downvotes users from instance C would see a total score of 9.
It seems odd to me that we would federate with instances lacking such basic functionality. Not allowing their users to downvote is one thing, but if they don’t recognize downvotes from other instances, that sort of ruins the whole upvote/downvote dynamic for everyone.
I was on Beehaw and they block downvotes. I didn’t think much of it until I went to a federated channel with low participation (it was a new channel) and I wanted to downvote some bot-spam… but couldn’t cause Beehaw didn’t allow it.
I understand (but don’t agree with) the site operators intention, but their rational breaks down if you view the fediverse as something more than the single instance you’re registered with.
Fortunately, it’s easy to “vote with your feet”.
Beehaw seems to want to only be beehaw lol. I’m honestly not sure why they’re even using lemmy to host their community.