5 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

I don't see much point in the comment rate limit in generalI don't see much point in the comment rate limit in general, and the rate limit should at least be smoothedsmoothed outout to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

I don't see much point in the comment rate limit in general, and the rate limit should at least be smoothed out to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

I don't see much point in the comment rate limit in general, and the rate limit should at least be smoothed out to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

4 Fixup of bad MSO links to MSE links migration
source | link
3 Fixup of bad MSO links to MSE links migration
source | link

I don't see much point in the comment rate limit in general, and the rate limit should at least be smoothed out to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

I don't see much point in the comment rate limit in general, and the rate limit should at least be smoothed out to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

I don't see much point in the comment rate limit in general, and the rate limit should at least be smoothed out to allow reading several comments on one post, then upvoting more than one. Still, I understand the rationale behind declining this feature request: it would make comments easier to use.

But there's a case when the comment rate limit is not only annoying, but also counter-productive. Consider:

  1. I write a comment and post it.
  2. When I post, I discover a new comment, posted seconds before mine.
  3. I read this comment and realize it's similar to mine.
  4. I decide to delete my comment (ok) and upvote the earlier one.
  5. I need to wait 5 seconds before upvoting the earlier comment.

What I learn from the system's reaction is that I shouldn't remove my duplicate comment. Which I'm pretty sure is not intended. So, at least, don't count a comment deletion and a comment upvote against the same rate limit.

2 Migration of MSO links to MSE links
source | link
1
source | link