Now if you try to cast over a certain amount of up/downvotes a day, you will not be allowed to by the code.
The Piefed staff has said that the motivation is in keeping people from voting ‘too much’ - ie, that users who use Piefed ‘too much’ should use it ‘less’ in the interest of ‘fairness’ to other users.
Even if this is reversed, that attitude - not the first time the Piefed staff has expressed that thought, but the first time they’ve actually implemented something non-optional along those lines - suggests that issues like this will continue popping up, even if this voting limit ends up being removed by public outcry.
“When people tell you who they are, believe them the first time”, and all that jazz.
Interesting! Not that i dont believe you but is there a PR or code sample i can see? Id like to see what the actual code is doing. Thank you for the explanation.
I may be able to curtail a pr to address or at least make this instance specific.
It is, at present, instance-specific, or at least, opt-out by admins. My issue is that I don’t have the morale to migrate all my comms to another Piefed instance. I’m done. The instability in the Fediverse has done me in. I’m not stable enough myself to deal with it.
No, this affects each and every PieFed instance that upgrades to v1.7 (I sent you in a different reply here the exact lines of code). PugJesus’ instance PieFed.social uses the now-default value of 240 as the daily vote quota. Admins may opt-out by setting the quota differently, however this will only impact votes accepted on your current instance. It will not affect votes accepted by other PieFed instances. e.g. if your instance uses 500 rather than 240, then someone looking at the identical content from PieFed.social will not see any of the second half of your daily votes: you will be able to OFFER them, and Lemmy will receive all of them, but each PieFed instance chooses itself how much it will receive or not.
And btw this information is not presented anywhere to show what these values are across each instance. Like the caps on posts and comments, it is silently effective, but not transparent in the least. So like the whole argument about whether defederations destroy the foundational principles of the ActivityPub Protocol-using Threadiverse, this new issue too is going to wreak havoc on the acceptance of PieFed in the wider Threadiverse & Fediverse communities. :-(
Now if you try to cast over a certain amount of up/downvotes a day, you will not be allowed to by the code.
The Piefed staff has said that the motivation is in keeping people from voting ‘too much’ - ie, that users who use Piefed ‘too much’ should use it ‘less’ in the interest of ‘fairness’ to other users.
Even if this is reversed, that attitude - not the first time the Piefed staff has expressed that thought, but the first time they’ve actually implemented something non-optional along those lines - suggests that issues like this will continue popping up, even if this voting limit ends up being removed by public outcry.
“When people tell you who they are, believe them the first time”, and all that jazz.
Interesting! Not that i dont believe you but is there a PR or code sample i can see? Id like to see what the actual code is doing. Thank you for the explanation.
I may be able to curtail a pr to address or at least make this instance specific.
It is, at present, instance-specific, or at least, opt-out by admins. My issue is that I don’t have the morale to migrate all my comms to another Piefed instance. I’m done. The instability in the Fediverse has done me in. I’m not stable enough myself to deal with it.
Please don’t go, I love your content.
Ah so this is just something on this server. Carry on.
Ive found my own infa is the most stable. Gotosocial is my favorite at the moment. Or at least the most fun.
Almost all of the fedi is volunteer and making negative money. Burning money in big buckets.
GL! Hope your next adventure is a fun one.
Everything is efferial. Even our silly messages on the internet.
No, this affects each and every PieFed instance that upgrades to v1.7 (I sent you in a different reply here the exact lines of code). PugJesus’ instance PieFed.social uses the now-default value of 240 as the daily vote quota. Admins may opt-out by setting the quota differently, however this will only impact votes accepted on your current instance. It will not affect votes accepted by other PieFed instances. e.g. if your instance uses 500 rather than 240, then someone looking at the identical content from PieFed.social will not see any of the second half of your daily votes: you will be able to OFFER them, and Lemmy will receive all of them, but each PieFed instance chooses itself how much it will receive or not.
And btw this information is not presented anywhere to show what these values are across each instance. Like the caps on posts and comments, it is silently effective, but not transparent in the least. So like the whole argument about whether defederations destroy the foundational principles of the ActivityPub Protocol-using Threadiverse, this new issue too is going to wreak havoc on the acceptance of PieFed in the wider Threadiverse & Fediverse communities. :-(
“migrate all my comms” what does that mean and why would you do it?
Re-creating the comms I run on a different instance.
Most of my activity is in those comms, and there’s not a lot in the way of alternatives for most of them, topic-wise.