Another point of view might be that a list of single word titles as search results is useless. Then, by all means, fix the search functionality. It shouldn't report something that's considered useless.

Also single word titles are more likely to duplicate than multiword titles. Yes, and? One should realize that titles are just, uhm, titles. They are not a list of keywords to an index. If books can have 30 long chapters with one-word titles that don't screw up the index, certainly a one word title for a node of a few lines should be ok.

Also if it is a single word "Haxml" and somebody searches for it then they get directed immediatly to this Haxml node instead of being given a list of nodes related to Haxml. Is this broken behavior? That depends. If it's the only node with "Haxml" in the title, it's not broken. If it's a top level node whose title consists of just "Haxml", and there are no other top level nodes with "Haxml" in the title, it's not broken. If it's an 11 level deep reply, and there are other nodes with "Haxml" in the title, I'd sure call that broken behaviour.

I think the advantage of discriptive titles and better searching is far more important than single word subject lines. Now you are implying two things I disagree with. First you are implying that one word titles could not be good subject lines. That I disagree with. It doesn't mean that any one word subject line is good, but it's certainly not true that any one word subject line doesn't describe the node accurately. The second thing you imply is that the search functionality is good, and people getting send to the wrong pages, or presented a wrong list of options, is caused by people using one-word titles. I'd say, the search functionality is broken. (I haven't bothered with "search" for years - I always go straight to super search. Search seldomly gives me what I want). Don't blame the data if the algorithm is broken.

In reply to One word titles by Anonymous Monk
in thread Appealing a consideration? by sleepingsquirrel

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.