just posted What algorithm is used to display the Badges multipliers on the user profile? question and it was shown there on the main page i.e. "newest" section and "recently active" section.
But, few minutes later my post got an answer that was totally irrelevant to what I asked for. So, I downvoted it and flagged it as "not an answer". I guess some other user also found that answer was wrong so he/she also downvoted it.
Here is the screenshot of my flag summary page:
My question does not have any downvotes or on hold status, but it's been taken out from the "newest" or "recently active" section. The only downvotes (-2) here are for the wrong answer given by newly registered user "Theodore Belleabs Theosop". Later, the answer was deleted by moderator. The only proof I have is the above screenshot. My question appeared at both the places after deleting the user's answer.
As per the threshold limit a score of -8 and lower cause the question to not be displayed in question lists. But, here my question has no negative score. So, how did it got disappeared? Can anyone please explain this.
Here is a screenshot of my "newest" page:
Here is a screenshot of my "recently active" page:
I just noticed the exact same behavior on "We should always be able to include explanation with moderator flags..." question just posted few minutes back. The post got disappeared from the newest and recently active page as soon as the answer on that post got first down-vote. I even posted my comment there. Later, upon receiving an up-vote (0 score i.e. no negative vote) the post reappeared at both the places.
There is something going on here for sure. It's also confirmed (read comment below) by Tim Stone (♦ moderator of Stack Apps). I
don't know how to reproduce this. I just witness it on my own question:"What is the correct count of all Stack Exchange Network sites?..." where I got down-vote for my answer and the post got disappear. I deleted my answer but if you have enough rep. you will see it. Can anyone from SE team please investigate this issue.