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

This does not make sense to me even on an abstract mathematical level.

How much does reducing these contributions save - 2x, 3x, 5x? To be on the safe side let’s balloon that up and call it “10x”. Even so this isn’t a “storm”, this seems barely sprinkling?

How many people do we hope to pull in from the likes of Reddit, Mastodon (not leaving it but either adding a PieFed account or at least introducing new traffic to PieFed instances, via users existing Mastodon account), Bluesky, X(hitter), etc. - 10x? Or even people switching from Lemmy servers as those go down, and people switch to PieFed? PieFed.social has <1.5k MAUs, fedisnfw.app has 3.1k, and the rest are all exclusively <0.25k.

The other commentor said 400k or 4M (edit: as a potential target audience to aim for), so conservatively if you are counting 400k as “the storm”, then that’s 100-fold higher traffic levels!! (And a target of 4M is 1000-fold.) A mere 10x decrease from actual contributions by users is nothing in comparison.

If we aim to grow by 1000x more MAUs, then perhaps we should work on more efficient network traffic sending - e.g. federate batches of votes (although this I recall was already done), though person perhaps this is a problem that should wait until we get closer? In chess you have to get through mid-game before end-game strategies begin to become relevant at all.

And for now PieFed looks like it needs all the engagement that it can get? There was a time only a few months ago when increased levels of contributions were being touted as a “GOOD thing”? While now, I guess posts and comments are, but votes are somehow not? This all makes my head spin though - where did this come from? How long until comments are no longer desired either? Is the aim to become an RSS reader / “news aggregator”? Is there some publication you can point us to read to help us understand why the sudden switch in behavior? In advance I doubt I’ll agree with its premise but I would very much like to know more where any of this is coming from?

Also, why bother making PieFed pull in posts from Mastodon then, if additional traffic is “bad”? To be clear I am not calling Mastodon traffic as bad in the content sense, but numerically speaking… it IS a “storm”, in the sense that it has >800k MAUs. If a PieFed instance cannot handle a mere 2-10x amount of traffic, then how could it hope to pull in… let’s see, 800k/5k that’s = 160-fold higher traffic stats from trying to pull in all Mastodon users. Tbf maybe that’s not what you are trying to do in the first place, so ignore this part of my comment in that case.


Insert image