“users by default have a rate limit of 1-comment-per day” and “1 post per week.”
Imagine a system that lets a user write their comments or posts in advance, and then publishes comments according to these limits automatically. Then these limits wouldn’t be enough. On the other hand, if you want to write a comment, you want to write it right away, instead of only starting to write it the next day because you are out of commenting chits. It’s very annoying if the UI doesn’t allow you to do that and instead you need to write it down in a file on your own device, make a reminder to go back to the site once the timeout is up, and post it at that time, all the while remaining within the bounds of the rules.
Also, being able to reply to responses to your comments is important, especially when the responses are requests for clarification, as long as that doesn’t turn into an infinite discussion. So I think commenting chits should accumulate to a maximum of at least 3-4, even if it takes a week to get there, possibly even more if it’s been a month. But maybe an even better option is for all but one of these to be “reply chits” that are weaker than full “comment chits” and only work for replies-to-replies to your own comments or posts. While the full “comment chits” allow commenting anywhere.
I don’t see a way around the annoyance of feasibility of personally managed manual posting schedule workarounds other than implementing the queued-posting feature on LW, together with ability to manage the queue, arranging the order/schedule in which the pending comments will be posted. Which is pretty convoluted, putting this whole development in question.
An obvious issue that could be fixed by the UI but isn’t, that can be worked around outside the UI, is deliberate degradation of user experience. The blame is squarely on the developers, because it’s an intentional decision by the developers. This should be always avoided, either by not creating this situation, or by fixing the UI. If this is not done, users will be annoyed, I think justifiably.
a reason to actively facilitate users having an easier time posting as often as possible
When users want to post, not facilitating that annoys them. If you actually knew that we want them to go away, you could’ve banned them already. You don’t actually know, that’s the whole issue here, so some of them are the reason there is a site at all, and it’s very important to be a good host for them.
Imagine a system that lets a user write their comments or posts in advance, and then publishes comments according to these limits automatically. Then these limits wouldn’t be enough. On the other hand, if you want to write a comment, you want to write it right away, instead of only starting to write it the next day because you are out of commenting chits. It’s very annoying if the UI doesn’t allow you to do that and instead you need to write it down in a file on your own device, make a reminder to go back to the site once the timeout is up, and post it at that time, all the while remaining within the bounds of the rules.
Also, being able to reply to responses to your comments is important, especially when the responses are requests for clarification, as long as that doesn’t turn into an infinite discussion. So I think commenting chits should accumulate to a maximum of at least 3-4, even if it takes a week to get there, possibly even more if it’s been a month. But maybe an even better option is for all but one of these to be “reply chits” that are weaker than full “comment chits” and only work for replies-to-replies to your own comments or posts. While the full “comment chits” allow commenting anywhere.
I don’t see a way around the annoyance of feasibility of personally managed manual posting schedule workarounds other than implementing the queued-posting feature on LW, together with ability to manage the queue, arranging the order/schedule in which the pending comments will be posted. Which is pretty convoluted, putting this whole development in question.
LessWrong already stores comments you write in local storage so you can edit it over the rose of the day and post it later.
I… don’t see a reason to actively facilitate users having an easier time posting as often as possible, and not sure I understand your objection here.
An obvious issue that could be fixed by the UI but isn’t, that can be worked around outside the UI, is deliberate degradation of user experience. The blame is squarely on the developers, because it’s an intentional decision by the developers. This should be always avoided, either by not creating this situation, or by fixing the UI. If this is not done, users will be annoyed, I think justifiably.
When users want to post, not facilitating that annoys them. If you actually knew that we want them to go away, you could’ve banned them already. You don’t actually know, that’s the whole issue here, so some of them are the reason there is a site at all, and it’s very important to be a good host for them.