Absolutely. But this is not a way in which pain is superior to a pop-up box. If the pop-up box that replaced intense pain had alarms and flashing lights attached, and the one for more minor pains did not, I would pay attention to the alarms and flashing lights.
Speaking in terms of real pop-up boxes, you might be surprised at how easy it is for people to ignore the content of even the most blaring, attention-grabbing error messages.
A typical computer user’s reaction to a pop-up box is to immediately click whatever they think will make it go away, because a pop-up box is not a message to be understood but a distraction from what they’re actually trying to accomplish. A more obnoxious pop-up box just increases the user’s agitation to get rid of it.
As rationalists, we try hard to avoid falling into traps like these (I’m not sure if there’s a name for the fallacy of ignoring information because it’s annoying, but it’s not exactly a high-utility strategy), but part of the way we should do that is to design systems that encourage good habits automatically.
I like Firefox’s approach; when it wants you to choose between Yes or No on an important question (“Really install this unsigned plugin?”), it actually disables the buttons on the pop-up for the first 3 seconds. You see the pop-up box, your well-honed killer instinct kicks in and attempts to destroy it by mindlessly clicking on Yes so you can get back to work already… but that doesn’t work, you’re surprised, and that jolt out of complacency inspires you to actually read the message.
I suspect a “Hey, have you noticed that something has penetrated the skin of your left foot?” warning might benefit from having the same mechanism.
That doesn’t seem a lot better—I know what it wants me to do with an unsigned plugin prompt—review the site, verify the download hash, review the plugin source code, look for reviews of the plugin, author, site...
What I actually do is wait 5 seconds, then click “yes do it” as soon as possible. So the utility is … well intentioned, but still ineffective.
It’s true that it’s less than perfectly effective, but it serves some purpose: I almost always install plugins from the Mozilla plugin site, where a rating is immediately available, and where a virused plugin would probably get removed very quickly. Under those conditions, I know that I’m fairly safe just installing it anyways.
However, a malicious site could attempt to infect my browser by installing a plugin, which is where the timer comes in handy. It could even attempt to hide the plugin dialog with lots of other useless dialogs (“Really submit this comment?” Yes. “Really really submit this comment?” Yes. “Really really REALLY submit this comment?” Yes. “Install this plugin?” Yes. Oh, hold on, wait! Crap.)
More generally, timed dialogs are helpful because they increase the chance that you notice what it is you’re confirming. If you know you’re doing something risky and want to do it anyways, so be it… but at least you know what it is you’re accepting, and are given a greater opportunity to back out if you are surprised by the level of risk.
Absolutely. But this is not a way in which pain is superior to a pop-up box. If the pop-up box that replaced intense pain had alarms and flashing lights attached, and the one for more minor pains did not, I would pay attention to the alarms and flashing lights.
Speaking in terms of real pop-up boxes, you might be surprised at how easy it is for people to ignore the content of even the most blaring, attention-grabbing error messages.
A typical computer user’s reaction to a pop-up box is to immediately click whatever they think will make it go away, because a pop-up box is not a message to be understood but a distraction from what they’re actually trying to accomplish. A more obnoxious pop-up box just increases the user’s agitation to get rid of it.
As rationalists, we try hard to avoid falling into traps like these (I’m not sure if there’s a name for the fallacy of ignoring information because it’s annoying, but it’s not exactly a high-utility strategy), but part of the way we should do that is to design systems that encourage good habits automatically.
I like Firefox’s approach; when it wants you to choose between Yes or No on an important question (“Really install this unsigned plugin?”), it actually disables the buttons on the pop-up for the first 3 seconds. You see the pop-up box, your well-honed killer instinct kicks in and attempts to destroy it by mindlessly clicking on Yes so you can get back to work already… but that doesn’t work, you’re surprised, and that jolt out of complacency inspires you to actually read the message.
I suspect a “Hey, have you noticed that something has penetrated the skin of your left foot?” warning might benefit from having the same mechanism.
I appear to be a mutant: I always read pop-up boxes.
By all means, please adapt my analogy to something that you would actually pay attention to.
That doesn’t seem a lot better—I know what it wants me to do with an unsigned plugin prompt—review the site, verify the download hash, review the plugin source code, look for reviews of the plugin, author, site...
What I actually do is wait 5 seconds, then click “yes do it” as soon as possible. So the utility is … well intentioned, but still ineffective.
It’s true that it’s less than perfectly effective, but it serves some purpose: I almost always install plugins from the Mozilla plugin site, where a rating is immediately available, and where a virused plugin would probably get removed very quickly. Under those conditions, I know that I’m fairly safe just installing it anyways.
However, a malicious site could attempt to infect my browser by installing a plugin, which is where the timer comes in handy. It could even attempt to hide the plugin dialog with lots of other useless dialogs (“Really submit this comment?” Yes. “Really really submit this comment?” Yes. “Really really REALLY submit this comment?” Yes. “Install this plugin?” Yes. Oh, hold on, wait! Crap.)
More generally, timed dialogs are helpful because they increase the chance that you notice what it is you’re confirming. If you know you’re doing something risky and want to do it anyways, so be it… but at least you know what it is you’re accepting, and are given a greater opportunity to back out if you are surprised by the level of risk.
The about:config option “security.dialog_enable_delay” allows one to reduce the delay to 0.