The Voting Quota has ruined my workflow

submitted by edited

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?

28
17

Back to main discussion

Parent comment

No worries. Appreciate the clarification.

That does sound weird. Could be a different account. I believe the servers only store the last like 3000 votes and drop the older ones (my votes last about a week). So, maybe something with that. Maybe a Piefed.social admin removed them because they considered them invalid or wasteful.

I think we’d need to ask a piefed admin or OP to get a better idea of what happened and why.


Insert image