6

In the days of yore (i.e. before last Monday or so), on questions deleted automatically deleted by Community, one could see which process caused it to be deleted, e.g. RemoveDeadAbandonedQuestions. However, now it doesn't say that.

These reasons were nice; on the help page one can look for the specific reason to see which thing deleted the post and why, and it was just overall nice to have at least a wee bit of (vague) info about what the Community user was deleting questions for.

Can we get the ability to see these again? It was nice to have more info than that a thing deleted the post and a link to a whole big article.

  • 5
    Per the consensus here, voting to close this as a duplicate of New Post Notices are live network-wide. – Sonic the K-Day Hedgehog Dec 7 '19 at 6:23
  • 1
    @Sonic how is it "consensus" that you posted a -5 score question which has a 2 score accepted answer? – Stormblessed Dec 7 '19 at 16:23
  • The question only expresses a neutral point of view, while the answer, which advocates for closing them as duplicates, has a net positive score. – Sonic the K-Day Hedgehog Dec 7 '19 at 19:37
  • 1
    @Sonic no. The votes on the question are definitely about whether or not the proposal are good. – Stormblessed Dec 7 '19 at 21:25
  • 1
    Stormblessed, true. Not near a "consensus". See The Announcement Tag, near the bottom of the question. The "Announcement + Discussion" tag used by an employee (especially with a specific statement requesting "Feedback") means that 'answers' can be offered as "feedback" to the 'question' (announcement). So, usually you would post the above question as an "answer" there (the dupe link) except, in this case Sonic has already filed a report - which makes this no less a duplicate of that link, with the answer already given there. – Rob Dec 7 '19 at 21:35
  • 1
    @SonictheReinstateMonica-hog and the answer, too is at +7- 5, not really a consensus. Initially, I only downvoted the question to express disagreement with the premise. I have now, seeing the talk about consensus, extended that to the answer. That's not something I like to do, please don't put people in that position by saying there's a consensus when there isn't. – JJJ Dec 8 '19 at 1:58
  • @JJforTransparencyandMonica Ah, I assumed the downvotes on the question were simply because people thought it was a bad discussion that wasn't worth having, not because people disagree with the premise, since it wasn't a feature request. Also, I'm sorry that I mis-phrased it as a consensus in my initial comment; my goal was to vote for it as a dupe and edit in a link to the prior discussion where (in my view) a majority of people agreed with such closures. – Sonic the K-Day Hedgehog Dec 8 '19 at 6:50
  • It's also worth noting that the original post featured a disagreement against closing such questions as dupes, but I edited it out and made the question neutral because people were downvoting that initial revision, and I thought those downvotes were against that opinion and people thought they should still be closed. (TL;DR: I misunderstood the consensus of the community. The vote wasn't based on my personal opinion, but on what I thought was the community's opinion. I generally try to uphold it even if it's out of alignment with mine.) – Sonic the K-Day Hedgehog Dec 8 '19 at 6:54