submitted 3 months ago* (last edited 3 months ago) by to c/fedimemes@feddit.uk
 
Cat with 90% of daily vote quota used standing up hiding around corner from dobermen.

all 21 comments

sorted by: hot top controversial new old
[–] 24 points 3 months ago (10 children)
  • [–] [S] 16 points 3 months ago (5 children)

    Yes it was just recently added from the Piefed 1.7 Update.

    To reduce server load and network traffic, a maximum number of votes that can be cast each day has been set at a level that will only affect the top 2% of voters, leaving the bottom 98% unaffected. This quota can be altered with an environment variable. View a profile to see how much of their daily quota has been used.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 17 points 3 months ago (3 children)

    Approximately how many upvotes are the limit? I tend to upvote a lot of content that I like as well as comments.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 3 months ago (3 children)

    It turns out that 10 people are casting more votes than the bottom 50% of us are. Effectively, 10 people are determining what is popular and what is not, on this platform.

    https://piefed.social/c/fediverse@piefed.social/p/2190040/who-decides-what-you-see-on-the-fediverse-a-look-at-voting-patterns

    The vote quota is an attempt to address that.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 3 months ago (2 children)

    You said in the release notes that this was about server load, but now it's about people voting too much for your tastes? 14K unique people cast at least one vote in the past day, I really doubt 10 people are having a great impact on the rankings. And if you think people are bots manipulating the rankings, then wouldn't it be better to bring it up in the admin chats so they get banned?

    Also, what's the methodology you've used there? You say the top voter has 23K votes, but from feddit.uk's data the top voter is at 19K, who happens to be a p.s user mind you.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 months ago (1 child)

    It is also about server load, yeah.

    The server infrastructure that we provide is a commons - a finite shared resource that people use. Why would we let 0.02% of the people take half of it? Couldn't we just rein in that 0.02% and then spend way less money on servers?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 3 months ago

    You seem to keep flipping on this point, which is confusing to me.

    If a limit must be applied for that reason, then so be it.

    How much server costs would be saved though by this limiting, or is that simply a theoretical consideration?

    Wouldn't more savings be possible by something else like limiting uploaded image sizes, or like only allow 10 images per month (uploading a new one automatically deletes the prior one)? And if so, what is the benefit of that other solution vs. the effects of throttling the top contributors? Both decrease the overall health of the network, so which at least maximizes the savings from having done so?

  • source
  • parent
  • [–] 13 points 3 months ago (4 children)
  • [–] 7 points 3 months ago (3 children)

    My 241st vote when it realises it's going to a piefed instance:

    Vanellope banging against an invisible wall before getting sucked into a black hole.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 3 months ago* (last edited 3 months ago) (2 children)

    Omg this will really break the whole federated model won't it? It's already insane that different instances hold different vote counts from one another, but this adds a whole new twist on top.

    img

    Genuine question: does this mean that PieFed is now no longer ActivityPub compliant? Is it not fully part of the Threadiverse anymore, and is now its own little subset of that? Even Mbin still accepted vote counts, even though it added boosts ("increases" and "reductions" iirc?) on top of them.

    Could you tell from your look at the code if PieFed is only throttling its own users internally, prior to votes federating out, or throttling incoming votes from Lemmy as well?

    Also this is so ridiculously easy to get around: most of us have a variety of obvious and self-acknowledged alts across the Threadiverse, but I doubt PieFed is going to maintain a mapping among all of them and apply the throttle universally across the entire set. e.g. Blaze goes back to his empire of alts, one for each day of the week, and continues upvoting without restriction.

    The KISS principle would seem to apply - why needlessly complicate matters?

    Edit: I found your missing vote btw, here it is:

    img

    Edit 2: I thought the above image was from Black Hole Sun, but now I am not so sure of that... anyway it seems to fit, regardless:-P.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 months ago* (1 child)

    Genuine question: does this mean that PieFed is now no longer ActivityPub compliant? Is it not fully part of the Threadiverse anymore, and is now its own little subset of that? Even Mbin still accepted vote counts, even though it added boosts (“increases” and “reductions” iirc?) on top of them.

    Let's not catastrophise. Piefed is still ActivityPub compliant, or as compliant as it was. Nothing in the spec says you have to accept an activity, it'd be pretty nonsensical if it did because moderation wouldn't be possible.

    Could you tell from your look at the code if PieFed is only throttling its own users internally, prior to votes federating out, or throttling incoming votes from Lemmy as well?

    It's throttling incoming votes as well, you can see that here. It honestly wouldn't make much sense if it didn't, though it is irksome that it blocks announcing the vote to other instances. That makes piefed comms something the really active users will avoid.

    Also this is so ridiculously easy to get around: most of us have a variety of obvious and self-acknowledged alts across the Threadiverse, but I doubt PieFed is going to maintain a mapping among all of them

    Even if they tried to do that, people would just stop being forthcoming with their alts.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 3 months ago

    Thank you for your measured response.

    Throttling PieFed users is bad enough, but throttling users of other platforms seems akin to censorship. Like if you want to access the full Threadiverse then you can do so from Lemmy + mBin + nodeBB etc., but if you access via PieFed then you don't get the full range of activities. In some ways PieFed is Threadiverse++ (the API supports user & post flairs, polls, emoji reactions, etc., on top of internal organization goodies like categories of communities if you use the web UI), but in some ways it is also Threadiverse—, intentionally choosing to ignore some contributions from the wider Fediverse.

    At a minimum that would be quite... odd to explain to people.

    And thank you also for the additional code peek!:-)

  • source
  • parent
  • [–] 9 points 3 months ago
    [+] [S] 1 point 3 months ago (3 children)