No, that says what revision of the node was in place when I finished my reply. It says much less about what revision of the parent node was in place when I started my reply (or, more accurately, what revision was in place when I loaded the page from which I later started my reply). And I can envision some members objecting if we started publishing how long it took them to reply, so I don't think publishing the start date would be an unmixed blessing.

But I agree with others that the important thing is that people should not make non-trivial updates to their nodes without 1) making it obvious that an update took place, and 2) making it clear what (at least mostly) the node looked like before the update. It is also important that people be discouraged from making major updates to nodes at all. There are too many features that don't work well in the face of major updates so it is more important to discourage those than to publish details about how long (even just in terms of count of revisions to the parent node) it takes people to reply.

This way, at least readers would be warned that they should think before assuming that the replier is an idiot

I'd rather people think before assuming a replier is an idiot even if there has been no update made.

- tye        

In reply to Re^2: Marking replies to updated nodes (dates) by tye
in thread Marking replies to updated nodes by sfink

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.