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

rimu@piefed.social

Improvement for the vote quota implementation (cake.kobel.fyi)

submitted 23 hours ago by squirrel@cake.kobel.fyi to c/piefed_meta@piefed.social

17 comments fedilink hide all child comments

After a couple days of discussions about the newly implemented vote quota, I'm kinda exhausted. It seems like a situation we won't ever agree on. Me personally, I don't want to argue like this over a piece of software that I have high regards for. It tears us apart, where we should work together.

It's okay if there is a quota on piefed.social the instance.
It's not okay if there is a default quota of 240 on PieFed the software - and thus for all instances.

I suggest it should be implemented like this:

It should not be a default value
It should be an empty input in the admin interface, where instance admins can set a vote quota if they want to, or leave it empty to disable the vote quota.
The /about page should display the set vote quota.

That way all instances can decide for themselves and users can see the instances' vote quota transparently.

you are viewing a single comment's thread
view the rest of the comments

[–] Snoopy@piefed.social 2 points 19 hours ago* (last edited 19 hours ago) (1 children)

If you go that way, the instance chooser should indicate the vote quota set by admin.

But, honnestly, the vote quota is so high that very few people can reach it. For me, it work as the scaled filter for post.

[–] OpenStars@piefed.social 3 points 18 hours ago (1 children)

THIS CHANGE DOES AFFECT YOU.

"It does not affect me directly so I do not care" is not a good argument. e.g. if you drive rather than ride a bicycle to work, then you are still impacted by shutting down or opening up bike lanes - if nothing else by the increased/decreased traffic on the road that you do use.

This change affects us ALL - some users directly in the sense that they cannot offer as many contributions as they used to, while others indirectly by seeing an overall cooling effect with fewer votes overall across all posts, but particularly in niche ones where the impact of just 1-2 extra votes would have made all the difference. Posts that would have hit your Subscribed feed (not sure if you use that or not but it would be affected either way:-) are now going to languish, having no additional votes (beyond the OP's self one) to boost them there.

And if this change is extended to include comments as well - and why wouldn't it? How are they so different, really? - then likewise the Active filters will be impacted as well.

[–] rimu@piefed.social 1 points 5 hours ago

This change affects Snoopy in a good way - his votes are no longer being drowned in a flood of indiscriminate votes that water down the effect of votes from more selective people like him.