Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (4)
As of 2024-03-28 15:30 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found