23
The Voting Quota has ruined my workflow Solved (piefed.social)
submitted 4 months ago by to c/piefed_meta@piefed.social
7 comments fedilink hide all child comments
 

So, I used to vote on posts constantly—not really to give karma, but as a quick way to mark them as read to get them out of my feed. It was perfect: a single click, much faster than actually opening the post. But now with the new voting quota in place, I can't do that anymore without hitting the limit. According to discussions on the instance, the quota was implemented to limit voting activity, and it's already affecting users who vote frequently.

The "Hide posts I've interacted with" setting is still there, but it relies on that interaction happening . What am I supposed to do now? Opening each post to mark it as read is significantly slower. Is there another way to mark posts as read in bulk that I'm missing, or is this just how it's going to be now?

all 7 comments

sorted by: hot top controversial new old
[–] 17 points 4 months ago (2 children)

It may just be me, but I don't think this is what voting is intended for.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 17 points 4 months ago* (last edited 4 months ago) (1 child)

    Yeah, I think so, too. It's not really helpful for OP in any way. But the quota seems to do what it's designed to do. Make it more difficult for people to do weird things with the voting buttons. Reminds me a bit of xkcd #1172 "Workflow".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 16 points 4 months ago

    I agree, the way OP is using voting isn't really what it's intended for and the "mark read on scroll" is a better option for what they want.

    However, what damage are they doing? They are basically giving encouragement to everyone to keep posting. If the worry is bandwidth, Piefed is only at ~5k and the threadiverse at ~40k. If bandwidth is a problem now, how will the platform scale to 400k or 4M active users?

    I would upvote your and Nusm's comments, because they contribute to the discussion, but I already hit my limit for the day (took under an hour). If you want more of my perspective. OpenStars and Squirrel also provide their viewpoint on the situation in the post (I don't know how to specifically link to my comments so you got a link to someone who replied to me).

  • permalink
  • fedilink
  • source
  • parent
    • [–] 12 points 4 months ago* (last edited 4 months ago) (1 child)

    You could export your settings and switch to an instance with a higher vote quota. It can be changed by admins from the default 240 to any number by setting VOTE_QUOTA in .env.docker

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 10 points 4 months ago* (last edited 4 months ago)

    But how would anyone know which servers have done so?

    Trial and error, and then it could still change at any time? I don't see it anywhere in the About sections e.g. https://feddit.online/about. Edit: and even after you've made an account, I see no method to arrive at a numeric depiction of the quota - it's merely depicted as a visual bar, but it doesn't say whether that represents 10, 100, or 1000 votes, so there is no way to figure that out except start voting and see how fast it fills up to reach the cap?

    And the Instance Picker is already an absolute mess - e.g. see https://piefed.zip/auth/instance_chooser, or try to decipher what "Defederation: Good" means (is that... high? low? loose? strict? "Good" for who - a tankie, banning any criticism of Russia, China, or North Korea? or a former non-technical normal user coming from Reddit?), plus I see no mention of how a vote quota would be represented here (lowering "Newbie friendly" status I would presume, since this goes against expectations, as e.g. set by Reddit that does not place any limits upon engagements).

    This new "anti-feature" is not very transparent at all.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 8 points 4 months ago* (1 child)

    I’m horrified that you’re using Piefed for work.

    Have you considered using Piefed client that has „mark all as read” button or „mark as read on scroll” features? Voyager does this, I’m pretty sure many others do. Another approach is to browse content sorted by new. In such setup all you need to know is if content is above or below your scrolling position. Hopefully these can make your work less tedious.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •