Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Surprisingly, this request is not prompted by any specific problem I encountered. It's more from my uneasiness with updating my own nodes seconds after I post them (yes, I do preview first. Fingers still much faster than brain.)

Suggestion: in the database, label every reply with an id/timestamp/version/whatever of its parent. When rendering out nodes, mark them as "this reply was to an earlier version of a post" if that id does not match the current id of the parent node.

The problem it addresses is when an author updates a node with replies such that the replies are invalid or don't make sense. This way, at least readers would be warned that they should think before assuming that the replier is an idiot, and perhaps wonder instead about the original poster.

I suppose you could also allow repliers to update their posts to "certify" them with the latest version of the parent node, thereby removing the warning label. Not that they need bother.

I have no idea what the performance implications of this might be, although it seems like the parent node is already getting retrieved at the very least to print out its title. I'm also not sure if the problem it is addressing is big enough to bother with. But it popped into my head, so I thought I'd mention it.

Update: I could have just changed the entire contents of node to "anybody who replies to this node is a poopy head."

But I didn't.


In reply to 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 avoiding work at the Monastery: (6)
As of 2024-04-25 15:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found