So I flagged an answer here as "not an answer"
https://graphicdesign.stackexchange.com/a/58220/3270
The flag was declined as declined - flags should not be used to indicate technical inaccuracies, or an altogether wrong answer
Huh? That post is nowhere near an answer. It's merely asking a very ambiguous question of the original poster. Are the mods now stating any answer which happens to include a screenshot must be an answer? Remove that screen shot and it's just a question. So.. why was my flag out of line?
I ask because I also had a flag declined on this answer: https://graphicdesign.stackexchange.com/questions/60585/i-am-having-problems-with-my-final-products/60622#60622 Which I flagged again as "not an answer" This has nothing to do with go-meek. My flag was due to the fact that the answer is essentially just rambling about things that may or may not go wrong, possible intricacies based upon ambiguous print providers. This is not a forum. While I don't fault go-meek for the post in any way. it's still not an answer to the question being asked (which really can't be answered as posed). It is purely general commentary, accurate and knowledgable commentary.. but commentary. In fact, she clearly posts herself "No one can tell you why your prints are too red unfortunately." So an answer which states "no one can answer" is now a valid answer?
So.. am I flagging too much?? I mean, I'll stop because clearly I'm suddenly not understanding what deserves to be flagged.