this post was submitted on 09 Aug 2023
172 points (95.7% liked)

Fediverse

26737 readers
127 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

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.

  1. 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

  2. Now we upvote the post:
    A: 11 - 0 = 11
    B: 11 - 0 = 11
    C: 11 - 0 = 11

  3. 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.

you are viewing a single comment's thread
view the rest of the comments
[–] Anafroj@sh.itjust.works 2 points 11 months ago

You're welcome. :) Oh yeah, you probably use a lot of them, they are everywhere, although it's not obvious to the user. One way to figure it out is to open the browser inspector (usually control + shift + i, same to close it) and look on the "network" tab, which lists all network requests made by the page, to see if this list gets emptied when you click a link (if it's a real new page, the list is emptied and new requests appear).

My apologies, I spent an hour on the popstate problem before losing interest and calling it a day. Lemmy uses the inferno frontend framework (a clone of react), which uses the inferno-router router to handle page changes, which uses the history lib to do it, which… uses pushState as I expected it would. And yet, binding on popstate won't work. 🤷 Maybe I'll have an other look at it one day if it bugs me enough. :)