I'm just saying it's not an argument in favour of restoring content.

I think the potential loss of context is an argument in favor of restoring content.

When context is lost, the site itself loses cohesiveness and that's detrimental to everyone, not just the author of the reply that's left in limbo.

Unfortunately, not everyone quotes context like you and I do. You can't really force people to quote.

I'm in favor of making the whole revision history available. Short of that, though, I think restoring lost content is sometimes best for the site and should be done in cases where it is appropriate to do so.

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Re: Taking away edit-own-nodes privledges. by sauoq
in thread Taking away edit-own-nodes privledges. by theorbtwo

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.