Ultimately the primary constraint on almost any feature on LessWrong is UI complexity, and so there is a very strong prior against any specific passing the very high bar to make it into the final UI
On the low end, you can fit the idea entirely inside of the existing UI, as a new fancy way of calculating voting weights under the hood (and allowing multiple clicks on the voting buttons).
Then, in a rough order of less to more shocking to users:
showing the user some indication of how many points their one click is currently worth
showing how many unused “voting points” they still have (privately)
showing a breakdown of recevied feedback into positive and negative votes
some simple configuration that allows to change the default allocation of budget to one click (e.g. how many percent, or pick a fixed value)
And that’s probably all you ever need?
This in particular limits the degree to which you can force the user to spend a limited number of resources, since it both strongly increases mental overhead (instead of just asking themselves “yay or nay?” after reading a comment, they now need to reason about their limited budget and compare it to alternative options)
This should be much less of an issue if the configuration of this is global and has reasonable defaults. Then it’s pretty much reduced to “new fancy way of calculating voting weights”, and the users should be fine with just being roughly aware that if they vote lots lots or don’t post anything on their own, their individual votes will have less weight.
On the low end, you can fit the idea entirely inside of the existing UI, as a new fancy way of calculating voting weights under the hood (and allowing multiple clicks on the voting buttons).
Then, in a rough order of less to more shocking to users:
showing the user some indication of how many points their one click is currently worth
showing how many unused “voting points” they still have (privately)
showing a breakdown of recevied feedback into positive and negative votes
some simple configuration that allows to change the default allocation of budget to one click (e.g. how many percent, or pick a fixed value)
And that’s probably all you ever need?
This should be much less of an issue if the configuration of this is global and has reasonable defaults. Then it’s pretty much reduced to “new fancy way of calculating voting weights”, and the users should be fine with just being roughly aware that if they vote lots lots or don’t post anything on their own, their individual votes will have less weight.