FWIW, I msg'd blokhead shortly after he considered it and tossed in a keep vote. What should someone do when they see a node improperly considered?
-sauoq
"My two cents aren't worth a dime.";
| [reply] |
What should someone do when they see a node improperly considered?
Promptly request an editor to unconsider the offending node.
HTH
_________
broquaint
| [reply] |
There may be other ways to handle this--I make no claims
this is the best. This is just what I'd prefer to encounter
if personally asked to unconsider a node.
Notify an editor, if one's around (or use the chatterbox), and wait with your
consideration vote to see if the editor needs it to
unconsider--unconsideration needs a certain number of keep
votes or a certain number of edit votes, and the post might
be lacking one of the right kind of vote to unconsider it.
If you get no response to your message, and the problem
hasn't been dealt with in about 5 minutes, the editor
probably isn't there.
If no editor is around, vote keep and message the editors
as a group. With only two keep votes deletion won't happen.
If you explain the reason in your message ("221876 was
thought to be a duplicate of 221901, but in fact it
isn't") the editor will spend less time verifying
and be able to unconsider more quickly.
| [reply] |
At first glance I thought it was a dupe. Most people probably assumed it was becuase 999 of 1000(~) times it is. No excuse for not paying attention while moderating but it would be wise to not post 2 nodes back to back with the exact same specific title.
-Lee
"To be civilized is to deny one's nature." | [reply] |
Funny thing is, it seemed to be something of a taboo subject, based on comments from a few weeks ago. So when I saw the nodereaper...
| [reply] |