The server infrastructure that we provide is a commons - a finite shared resource that people use. Why would we let 0.02% of the people take half of it? Couldn't we just rein in that 0.02% and then spend way less money on servers?
You seem to keep flipping on this point, which is confusing to me.
If a limit must be applied for that reason, then so be it.
How much server costs would be saved though by this limiting, or is that simply a theoretical consideration?
Wouldn't more savings be possible by something else like limiting uploaded image sizes, or like only allow 10 images per month (uploading a new one automatically deletes the prior one)? And if so, what is the benefit of that other solution vs. the effects of throttling the top contributors? Both decrease the overall health of the network, so which at least maximizes the savings from having done so?
Addendum: Yes we know that you think ml/hexbear/grad are tankies and or .world are a bunch of liberals but it gets old quickly. Try and come up with new material.
This is not the place to start flamewars between Lemmy, Mbin and Piefed.
It is also about server load, yeah.
The server infrastructure that we provide is a commons - a finite shared resource that people use. Why would we let 0.02% of the people take half of it? Couldn't we just rein in that 0.02% and then spend way less money on servers?
You seem to keep flipping on this point, which is confusing to me.
If a limit must be applied for that reason, then so be it.
How much server costs would be saved though by this limiting, or is that simply a theoretical consideration?
Wouldn't more savings be possible by something else like limiting uploaded image sizes, or like only allow 10 images per month (uploading a new one automatically deletes the prior one)? And if so, what is the benefit of that other solution vs. the effects of throttling the top contributors? Both decrease the overall health of the network, so which at least maximizes the savings from having done so?