This is not a SFW instance. NSFW communities will be tagged, and efforts will be made to keep SFW communities clean, but proceed at your own comfort level.
Oh sorry, I didn’t actually read the post you linked and assumed it was his going away message. Another L for reading comprehension on fedi.
Rimu added a feature to Piefed a coupla-few releases ago to limit the number of upvotes and downvotes each account can give per day. The meter you have in your screenshot is how many of your quota you’ve used today; if you give too many you’ll get a little pop-up that has some “you’re doing that too much, come back tomorrow” message. The concern was that the cost of federating votes was disproportionate to its value – making the network connections and passing the events takes a lot of overhead. He set the quota to something where like 95% of users would never hit it, but bots and truly unhinged users like PugJesus and I do. I really do not want to sound critical of this decision – all development decisions are about tradeoffs, and if my instance goes under because Jerry can’t afford to run it anymore, I lose access to all my friends, not just one. It isn’t like with a corporate social media where cutting costs increases profits, it’s just decreasing the rate at which they’re losing money. And piefed isn’t the only service that doesn’t federate likes the same as other activities – on mastodon, you generally only see likes from your own instance. Pug was just tired and disabled and in pain a lot and took the change hard because he’d migrated from instance to instance many times (which I have too, and I completely understand the frustration at feeling like you have to start over), and so he announced he was quitting fedi completely rather than doing it again. The fediverse is an extremely hard problem space to work in because there are very diverse use cases, and basically no money allocated to work on solving them, and this is just something that happens sometimes when you have two well-intentioned actors trying their best.
As a slight clarification, Rimu specifically confirmed the change (voting restrictions) were not due to bandwidth concerns, but rather to curtail certain users from voting “too much”.
Also, confirmed the users in questions were not bots, just user who voted a lot (I’m in that category). My instance removed the limiter within a couple days of the update being implemented.
Yet, Rimu mentions it in the release notes, so that’s the “official” reason:
To reduce server load and network traffic, a maximum number of votes that can be cast each day has been set at a level that will only affect the top 2% of voters, leaving the bottom 98% unaffected. This quota can be altered with an environment variable. View a profile to see how much of their daily quota has been used.
Oh sorry, I didn’t actually read the post you linked and assumed it was his going away message. Another L for reading comprehension on fedi.
Rimu added a feature to Piefed a coupla-few releases ago to limit the number of upvotes and downvotes each account can give per day. The meter you have in your screenshot is how many of your quota you’ve used today; if you give too many you’ll get a little pop-up that has some “you’re doing that too much, come back tomorrow” message. The concern was that the cost of federating votes was disproportionate to its value – making the network connections and passing the events takes a lot of overhead. He set the quota to something where like 95% of users would never hit it, but bots and truly unhinged users like PugJesus and I do. I really do not want to sound critical of this decision – all development decisions are about tradeoffs, and if my instance goes under because Jerry can’t afford to run it anymore, I lose access to all my friends, not just one. It isn’t like with a corporate social media where cutting costs increases profits, it’s just decreasing the rate at which they’re losing money. And piefed isn’t the only service that doesn’t federate likes the same as other activities – on mastodon, you generally only see likes from your own instance. Pug was just tired and disabled and in pain a lot and took the change hard because he’d migrated from instance to instance many times (which I have too, and I completely understand the frustration at feeling like you have to start over), and so he announced he was quitting fedi completely rather than doing it again. The fediverse is an extremely hard problem space to work in because there are very diverse use cases, and basically no money allocated to work on solving them, and this is just something that happens sometimes when you have two well-intentioned actors trying their best.
That bandwidth excuse doesn’t make sense, if you are bandwidth limited then limiting image sizes would have much larger impact
I guess maybe it’s rather the number of individual requests. maybe votes are not sent in batches
As a slight clarification, Rimu specifically confirmed the change (voting restrictions) were not due to bandwidth concerns, but rather to curtail certain users from voting “too much”.
Also, confirmed the users in questions were not bots, just user who voted a lot (I’m in that category). My instance removed the limiter within a couple days of the update being implemented.
Yet, Rimu mentions it in the release notes, so that’s the “official” reason:
Rimu acting like china