Quantcast
Channel: I raised an "other" flag after a Not-an-answer flag was declined, but it was declined too, though I don't agree. What should I do now? - Meta Stack Overflow
Viewing all articles
Browse latest Browse all 2

I raised an "other" flag after a Not-an-answer flag was declined, but it was declined too, though I don't agree. What should I do now?

0
0

Some time ago I found an answer in the First Posts review queue that made me raise a Not an answer flag. The question was:

The code snippet below checks whether a given number is a prime number. Can someone explain to me why this works? This code was on a study guide given to us for a Java exam.
(follows some code)

And the answer was:

This is how I would do it:
(follows some code that is quite different from the original)

So he provided a different approach. In my opinion this was a "Not an answer", since "it does not attempt to answer the question", as the flag description says, so I left a comment and flagged it. To my surprise, the flag was declined. I then searched on meta and I found a lot of discussions on the correct use of that flag. In short,

mods do not (automatically) see the question when going through NAA flags, and will therefore tend to reject any flags for answers the look like they're answering some question

Ok, so I know why it was declined. But what should I do about that answer then? I found another discussion, where a mod answered that

Most of the problems with poorly interpreted "not an answer" flags come from people using that and expecting us to understand the context in which they flagged it. For cases where a little more information is needed, people can easily use an "other" flag and write out why an answer needs to be immediately deleted.

and furthermore, in one more place the same solution was suggested: raising a custom flag.So I did that. I raised a custom flag, and I made sure to add a link to Brad Larson's answer as reference:

The question asks to explain some code, but this answer doesn't even try to do it, instead it proposes an alternative approach. I had raised a "not an answer" flag which has been declined. On Meta I have discovered that mods don't check the context (= the question) when reviewing NaN flags; when some context is needed, "other" flags should be used. Reference: meta.stackoverflow.com/a/286476/3982001

I've discovered this second flag has been declined again, for the same reason: "flags should not be used to indicate technical inaccuracies, or an altogether wrong answer". Now I am not sure what I should do. I feel that answer is really NAA, and if mods are uneasy about judging the technical accuracy of questions, well that's not the case, as in this case the reason isn't technical. You don't need to know Java here, and that's why I feel my flag should have been accepted.

So what should I do in this case, and all the others that are like this? There's another answer to that question that in my opinion should be treated the same way, and I've just stumbled on another one (which is blatantly NAA, and has been downvoted to -5, but it's still there).


Viewing all articles
Browse latest Browse all 2

Latest Images

Trending Articles





Latest Images