PieFed Meta

4771 readers

77 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 3 days ago by squirrel@cake.kobel.fyi to c/piefed_meta@piefed.social

50 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

[–] OpenStars@piefed.social 3 points 2 days ago

Others have calculated and said that this is false. Remember we are not discussing merely votes on posts but also comments. Someone mentioned that the quota could be reached in two hours at a vote every 10 seconds. I cannot even see the numeric value of the vote quota so I am relying on the math of others who have studied this in greater depth.