The problem, as everyone else already sufficiently pointed out, is that oftentimes, the seeker does not understand his own problem well, and will therefor have a hard time distinguishing good from bad answers, or will even not want to hear the good answers.

Of course, it's not the first time you're asking a question in this vein. The problem you are trying to solve is, I believe, fundamentally unsolvable. If someone asks a question that requires specific skills in an area that isn't common knowledge, it is a matter of luck whether their question will be answered. It's pretty much a matter of statistics, odds and probably Murphy.

A note to add is that I find that even when people ask about unusual topics, if they know how (not) to ask questions the smart way, esp if they keep trying to figure out their problem on their own and then later come back to post a reply with their conclusions so far, their chances of getting useful replies, with at least good pointers if not so much as a solution, are greatly increased.

Makeshifts last the longest.

In reply to Re: How node in SOPW is answered? I suggest author's ability to reject bad answers by Aristotle
in thread How node in SOPW is answered? I suggest author's ability to reject bad answers by Chicken

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.