Timeline for Flag for "Not an answer" should be re-worded
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 3, 2013 at 17:03 | comment | added | slhck Mod | One of the reasons for this policy is simply that you can't always have moderators evaluate whether an answer is correct or not. We can easily delete obvious things like spam, follow-up questions and their likes, but actually reading and understanding the entire question and then figuring out whether the answer addresses the problem sometimes requires technical knowledge which a moderator might not have for every topic. Finally: In the case of that answer, at least three users saw it, but nobody downvoted the post, even though they thought it was not useful. (cc @scott) | |
| May 3, 2013 at 17:00 | vote | accept | Scott Chamberlain | ||
| May 3, 2013 at 16:57 | history | edited | Scott Chamberlain | CC BY-SA 3.0 |
added 23 characters in body
|
| May 3, 2013 at 16:57 | comment | added | Scott Chamberlain | I misinterpreted your answer after the quote. With your first sentence I thought you where arguing the opposite point. I reworded that first sentence, you can change it back if I am still wrong. | |
| May 3, 2013 at 16:52 | comment | added | James Mertz | No your flag should've been denied. It was flagging an answer as "not an answer" but really was, even though it was a wrong answer, it still was an answer to the question. If you felt that it was "very low quality" then you should've flagged it as such. However that would've been denied as well (in this case) as the quality of the answer isn't bad either. Again, the answer may be completely wrong or inaccurate, but it's still an answer none the less. | |
| May 3, 2013 at 16:49 | comment | added | Scott Chamberlain | If that is so, my flag should not have been denied. | |
| May 3, 2013 at 16:45 | history | answered | James Mertz | CC BY-SA 3.0 |