I don't know there's enough benefit to be worthwhile for pmdev to bother with. We already have:

There are other tools as well. I don't remember them all. But with the power to consider a node should also come the effort to understand what should be considered, and how well-formed posts ought to look in the first place:

I see far too many nodes considered for reaping. Obvious spam is ok. Obvious abusive language is ok. Blatent trolling is ok. Considering for trolling is a slipery slope, though, and for the most part I personally prefer to see less of that type of consideration, mostly because it tends to give trolls more to gripe about, but also because it becomes unclear where to draw the line. When I happen to see a node considered to be reaped for a reason that I feel doesn't clearly rise to the occasion, I vote keep. Even reaping duplicates is tricky. If the post is not 100% identical, then we're rewriting someone's history. If they are 100% identical then I prefer to keep the one that has responses. If both have responses I prefer to keep the most recent and to reparent the responses to the other node under the one that is kept. For duplicates time is of the essence; swift action can avoid gathering responses under each duplicate. The best approach is to upvote the keeper, downvote the duplicate, consider the duplicate for reaping, and make it clear in the consideration which is the keeper.


Dave

In reply to Re: Messaging the result of a consideration by davido
in thread Messaging the result of a consideration by chacham

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.