I was editing one of my posts and saw a “View votes” in the dropdown hamburger for the post. Now I can see who serial downvotes. Nice.
I was editing one of my posts and saw a “View votes” in the dropdown hamburger for the post. Now I can see who serial downvotes. Nice.
Tying votes to accounts is pretty much required by the way activity-pub works; an upvote is basically the same as a heart/like on old Twitter and with federation it needs to know where the vote is coming from and where it’s going.
Piefed has an option to try to circumvent this by creating a second, “fake” account with no obvious connection to your own account and sends all your votes using that account. If the instance doesn’t have many accounts, though, it can still be obvious who’s voting.
As others have mentioned, other front ends or services can show the votes publicly to anyone who wants to see it. Even on other platforms that use a voting system one should always assume the votes are tied to one’s account.
Piefed stopped that actually and now instead have an option to not have your votes federate to other instance entirely.
How does the algorithm work then for hot and top?
The same. But a vote that does not federate will only have an impact on the instance where it was cast.
I’m not sure. Here’s the post where it went live, with links to the lead up at the bottom. I guess just ask @[email protected]
Oh, I’d missed that update!
Here’s the link in case you didn’t see my other comment here.
Thanks, so this was recent!