Skip to main content
Meta Stack Exchange

Return to Question

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

Background:

Allow more than 1 comment upvote in 5 secondsAllow more than 1 comment upvote in 5 seconds Summary of that thread: "Can we change the 5 second limit on up votes?" Status: "Declined." My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you can't upvote on a comment again so soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Background:

Allow more than 1 comment upvote in 5 seconds Summary of that thread: "Can we change the 5 second limit on up votes?" Status: "Declined." My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you can't upvote on a comment again so soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Background:

Allow more than 1 comment upvote in 5 seconds Summary of that thread: "Can we change the 5 second limit on up votes?" Status: "Declined." My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you can't upvote on a comment again so soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Post Closed as "Duplicate" by Kzqai, CommunityBot
edited tags
Link
Jarrod Dixon
Jarrod Dixon
  • 38.4k
  • 4
  • 131
  • 162
Fixup of bad MSO links to MSE links migration
Source Link
Community Bot
Community Bot
  • 1

Background:

Allow more than 1 comment upvote in 5 seconds Summary of that thread: "Can"Can we change the 5 second limit on up votes?"" Status: "Declined"Declined."" My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you"you can't upvote on a comment again so soon"soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Background:

Allow more than 1 comment upvote in 5 seconds Summary of that thread: "Can we change the 5 second limit on up votes?" Status: "Declined." My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you can't upvote on a comment again so soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Background:

Allow more than 1 comment upvote in 5 seconds Summary of that thread: "Can we change the 5 second limit on up votes?" Status: "Declined." My interpretation of the reason: An altered time limit might lead to more noise in the signal, the very thing the mechanism is designed to avoid.

My take is this:

The problem is not the time limit, the problem is the failure message behavior. I believe the "you can't upvote on a comment again so soon" message's BEHAVIOR is complete overkill, though I understand the necessity for the underlying time limit mechanism.

Problems with the current error:

  • Brings up a popup.
  • Displays the most visually noisy red error I have yet seen on the site, total overkill.
  • Remains open until you manually click to close it.
  • Provides no indication of when the functionality will actually be available again.

All just to tell you that you're being a bit too eager in your non-value-changing upvoting.

So I argue that the problem isn't the mechanism, it's the presentation, and I think that we can propose something better and much less annoying.

What alternatives can we come up with?

Migration of MSO links to MSE links
Source Link
Community Bot
Community Bot
  • 1
Minor typo fixes.
Source Link
Kzqai
Kzqai
  • 1.4k
  • 8
  • 17
added 123 characters in body
Source Link
Kzqai
Kzqai
  • 1.4k
  • 8
  • 17
added 3 characters in body; deleted 9 characters in body
Source Link
Kzqai
Kzqai
  • 1.4k
  • 8
  • 17
added 86 characters in body
Source Link
Kzqai
Kzqai
  • 1.4k
  • 8
  • 17
Source Link
Kzqai
Kzqai
  • 1.4k
  • 8
  • 17