Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

A newbie user posted Emergency! Our guestbook is getting trashed by HTML! For some reason, kutsu considered this node suggesting it be retitled to "Disallowing HTML Comments for a Chatroom." Out of the first 6 voters, I alone voted to keep it as is.

Hey folks, this is not a reasonable retitling request. It's a really bad one in fact.

The original title refers to a "guestbook" which was appropriate because the question was about the Guestbook from Matt's Script Archive. I gather that the poster has been using it as a chatroom sort of application, but that's beside the point. Furthermore, the title replacement seems to suggest that the question is about <!-- HTML comments --> but that's not really the case. The question is really about user comments that include HTML. Nevermind that the replacement suggestion is also bland and boring.

Bottom line is that you should have a good reason before you consider a node for retitling and, when you do, make a good suggestion for its replacement too. Many nodes need to be retitled because they are too general or offend the eye with all caps, too much punctuation, or what-have-you. Nodes that are formatted nicely and contain one or two keywords that successfully hint at the node's content should be left as is. A node's title is also often a small creative expression on the part of the writer. This is a Good Thing™. Not only does it keep things interesting, it helps to differentiate a node from all the others with similar content. So editing it should be done with forethought and respect.

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

Considered by hossman: "retitle: 'Advice on consideration of properly titled nodes'" Final vote: (keep/edit/delete) 19/7/1.
Unconsidered by davido: The majority has spoken.


In reply to Don't Retitle This Node by sauoq

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

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

    How do I use this? | Other CB clients
    Other Users?
    Others studying the Monastery: (14)
    As of 2014-07-31 17:08 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      My favorite superfluous repetitious redundant duplicative phrase is:









      Results (249 votes), past polls