this post was submitted on 17 Nov 2023
47 points (100.0% liked)
Blahaj Lemmy Meta
2379 readers
7 users here now
Blåhaj Lemmy is a Lemmy instance attached to blahaj.zone. This is a group for questions or discussions relevant to either instance.
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
Sounds like a client issue. I have a working downvote button on this very post.
Because you’re on an instance that enables downvotes. Some instances like lemmy.blahaj.zone have them disabled.
Upvotes and Downvotes exist separately from each other and when Downvotes are disabled, just the Upvotes are being counted on our clients.
Same with any content that lives on our instance, if a federated user on an instance that supports them downvotes our content their downvotes just don't get federated, at all. The downvoted contend only recieves a downvote on their instance and all other instances won't recieve it, though only applies to content where the original is on an instance without downvotes.
However, because the post was made to a Blahaj Lemmy community, those downvotes will only be visible to folk on your instance, because Blahaj Lemmy just ignores downvotes that federate to us, and doesn't federate them onwards.
Interesting.
So if I'm on the instance "Adama" and downvote a post on "Blahaj", does someone on "Cremmy" see the downvote or not - will Adama tell Cremmy?
If the community is hosted on Blahaj, Blahaj won't federate it to Cremmy
But if the user is a Blahaj user, posting on a group on instance Django, Django will forward the downvote to Cremmy.
However, in both of those scenarios, Blahaj itself will ignore all downvotes, meaning that the sorting algorithm for Blahaj users looking at content, local or remote, doesn't take downvotes in to account
Interesting, thanks for explaining.