Good idea. Would it be possible to just tag the bad nodes, i.e. <div ... class="badnode">, when logged in? That would allow to customise the appearance individually using CSS.

EDIT: Thus, censorship or not is kept an individual decision.
Suggestion for default CSS: Don't hide and don't mark.
Offer sample CSS or a configuration item in Display Settings, i.e. .badnode:before{ content: "Disputed: " }

If it is acceptable to just hide the content from AM (it's still in the source HTML), tagging might be good enough to reduce the implementation workload to just tagging plus CSS. However, search engines (and notorious HTML source readers) might still find bad nodes. Not sure if this is an issue, though.

In reply to Re: RFC: Hide Very Bad Answers From Visitors by Perlbotics
in thread RFC: Hide Very Bad Answers From Visitors by jdporter

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.