I recently asked a question about why I couldn't see error messages logged from K9 using aLogcat on Jelly bean.
The only answer instead answered a different question (i.e. "How do I fix these errors with K9?") so after waiting a while for an update, I flagged it as not an answer.
My flag was rejected with the reason: declined - "Not an answer" flags are for posts that are not even attempts to answer.
A moderator then commented: Perhaps you should have asked that, we generally prefer questions that don't presuppose a solution.
These are not necessarily related, but overall this all seems to be rather poor form to me. I've certainly never seen this sort of reaction on any other stack exchange site I've used regularly. When I ask a question I want an answer to that question, not the question that someone thought I should have asked.
I don't blame the answerer for trying, in good faith, to answer the question he may have thought I was asking, but to clarify the question, still not get an answer and then be told by a moderator that I shouldn't have asked that question in the first place is a double blow.
So, should a moderator decline a "not an answer" flag just because they think that you asked the wrong question, even if the answer did not in fact answer your question?
If so, then why has Android Enthusiasts decided to disregard what is considered stack exchange best practice, as detailed in Flags Too Often Marked [declined]?