this post was submitted on 09 Jul 2026
15 points (94.1% liked)

PieFed Meta

4767 readers
60 users here now

Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.

Wiki

founded 2 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] rimu@piefed.social 1 points 1 day ago* (last edited 1 day ago) (1 children)

The testing instance is not a source of traffic so the quota would have no direct effect on it. The savings there are a result of what's happening on other instances.

I'm showing that the vote quota reduced federation traffic for the whole threadiverse by 30% to 50%. What's happening there is lemmy.world, etc, where all the communities are, are sending less votes to everywhere (including to my testing instance). It's the community hosters that send copies of the votes to everyone, not the instance hosting the voter.

This is a huge win, especially for instances that host a lot of communities like lemmy.world, sh.itjust.works, etc.

[–] Vicinus@piefed.zip 3 points 1 day ago* (last edited 1 day ago) (1 children)

So looking at Piefed.world (on piefed version: 1.6.27):

  • Average Daily Posts (2026-06-26 -> 2026-07-02): 53.86
  • Average Daily Posts (2026-07-03 -> 2026-07-09): 50.14, (-6.90%)
  • Average Daily Comments (2026-06-26 -> 2026-07-02): 164.57
  • Average Daily Comments (2026-07-03 -> 2026-07-09): 133.29, (-19.01%)

Sh.itjust.works (Lemmy):

  • Average Daily Posts (2026-06-26 -> 2026-07-02): 131.57
  • Average Daily Posts (2026-07-03 -> 2026-07-09): 79.57, (-39.52%)
  • Average Daily Comments (2026-06-26 -> 2026-07-02): 1244.86
  • Average Daily Comments (2026-07-03 -> 2026-07-09): 1097.86, (-11.81%)

It would seem you need to normalize the packet rate for user activity to get an accurate picture. It should show a slight decrease of packets per active user (assuming same activity level), like you want and I said originally. But, it seems, the large decrease in the posted traffic graph is correlated to a large decrease in activity (posts and comments).

Piefed.social posts decreased 61.97%, and comments decreased 53.58% over the same period (much higher than a piefed instance that hasn't switched and a Lemmy instance). So, I don't think we should call this a "huge win" and would like to reiterate what I've been saying, the possible network stress reductions are not worth the downsides of limiting people (at this scale).

To me, you seem to be ignoring what I write and to repeat roughly the same thing over and over. That's fine to do, just please let me know so I can stop responding (it'll just save me and you some time).

Edit: formatting, and a word change

[–] hendrik@palaver.p3x.de 2 points 22 hours ago (1 children)

What's up with OP's votes anyway? My instance shows exactly 1 vote in the database, which is a bit of a mismatch against the original question?! But they've been here for a long time.

[–] Vicinus@piefed.zip 3 points 21 hours ago (1 children)

I'm confused on your question.

Are you saying the post only has one upvote (I see 14 up and 1 down?

Or are you saying your database only shows them as having used 1 vote? It's a "daily" vote limiter so maybe it reset? Also, they aren't on your instance so you may not be federated with everywhere they used their votes.

Or are you asking something else?

[–] hendrik@palaver.p3x.de 1 points 20 hours ago* (last edited 20 hours ago) (1 children)

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?

[–] Vicinus@piefed.zip 2 points 16 hours ago

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.