Voyager

Thank you :)

Score is not just upvotes minus downvotes.

The first 10 votes increase the score by much more than usual. Then the 20 after that are still worth more but not quite as much. Then the next 30 are worth only a little more than usual. After that 1 vote increases the score by 1. Lemmy does something like this too although they might be showing a simple upvote - downvote = score in their API.

The upshot of this is the 'Hot' sort surfaces new content quicker, resulting in a more interesting timeline.

The degree of early-vote amplification can be tuned by the instance admin but I have had zero questions about how to do this so I doubt anyone has played with it.

@wjs018@piefed.social

My guess is deleted/banned accounts, but I don't really have a way to confirm that. Even using my admin powers, I still only see the 12 upvotes and 0 downvotes, and none of those have a vote weight different than 1.

I have been digging into the code, trying to look at where the post.score is updated, which has led me to suspect it is deleted accounts (for whatever reason). When a vote happens, the vote is recorded in a table in the database, and the post score is adjusted based on the vote weight based on the voter's instance (in practice, this is basically always 1). However, when a user is banned/deleted, the votes recorded in the votes table are removed, but the post score is not adjusted accordingly to account for the now-deleted votes. The score just stays that number saved in the post table of the db.

@rimu@piefed.social - do you have any more insight? I was trying to think of the possibility of duplicate vote actions both contributing to the score, but I don't think that should happen. I can't really think of what else could make the score so out of line with the votes.