@amWhy : one of the problems in dealing with EoQS flags is that some of the poor questions related to EoQS violation are not in closed state. I do take help of CURED occasionally in such matters, but this leads to some delay in handling the flag.

@ParamanandSingh I can understand the problem. Best if we can first close the questions?

@amWhy Yes. Very much so.

I have trouble sending an EoQS message to a user if I have personally closed a bunch of questions which they have answered. Much easier if the questions are already closed.

@XanderHenderson That makes a lot of sense. Sometimes, it gets harder to wrap up closure, after an answer, which, when upvoted, at times translates into one or two upvotes on the question, and/or the answerer(s) cast reopen votes... At the same time, participation in CURED is at a low point. I imagine I've flagged answerers who flagrantly answer a question awaiting closure, which often prevents users from improving posts, so the act of answering, undermines the whole point of close votes.

@amWhy : no need to wait for closure, but don't forget to cast the close vote.

I'm not saying flagging at time of answering is the answer. But the various actions, all interdependent, make it sort of a chicken or egg quandary. It seems more difficult now, with CURED less active, to get posts closed. But I understand that should be a priority, before flagging, if possible.

@ParamanandSingh Indeed!

If there are a few close votes on the question i can use my vote to get it closed. But in absence of any vote the only recourse is to refer in CURED

Also, please note the my frequent willingness/commitment to downvoting, voting to delete answers, over time. Thanks, both of you, for the feedback!

6 messages deleted