p3x.deThe Voting Quota has ruined my workflow
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?
Share on Mastodon
Share on Reddit
Share on WhatsApp
Sorry, I meant their outgoing votes. The post_votes table on my instance contains one upvote for the user account (this post’s self-upvote) and no other votes. No post_reply_votes either. But it should store data from the last 6 months. That could be due to perspective. But I don’t see any upvotes on piefed.social either. So I’m a bit confused since OP writes they hit the limit. Did they talk about a different account? Did the votes we talk about somehow get dropped? Or are we talking hypotheticals here and it’s been more than 6 months since they voted?
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.