Further, what it really depressing is that often, if you simply ask the question, many usenet replies will be "google it" (1) type answers. So, you go to a NG which is for a subject, you ask about that subject, and people there think you should already know the answer before going to the place meant to discuss it.
(1)Used to be "google is your friend", but oddly enough, I dont see that so much these days.
Troll: "HTML is a programming language"
Gullible douchebag: "%s" % wikipedia_article_on_HTML
Troll: "Troll successful"Works for me because I care more about winning than being right, so I'm not embarrassed to be wrong.
Lot's of reasons people withhold information for whatever reason. Most geeks are introverts, so are reluctant to speak up. Some people don't want to be embarrassed. Many, many aren't aware of what they know. It's easier to criticize than to create. And, yes, some people are gate keepers, hoarding information.
I remember reading Mitnick used this trick a fair bit.
This is very useful Usenet+ trick to get an answer to a question. You could be nice and simply ask a question: "How can I do X in Y?" and you might get an answer. Maybe.
Or you could simply assert, "It is impossible to do X in Y", and get a flood of replies because, well, xkcd 386 should cover it.
http://xkcd.com/386/
edit: It occurred to me that there may be a practical way to spin this when getting software requirements. For example, you could simply ask, "Is <some quality or feature or behavior> important?" Ir you could phrase it as an assertion: "OK, so I'm assuming that <some quality or feature or behavior> is not important." Or some variation.
I wonder if that difference in phrasing leads to getting better details. That is, in what way does how you phrase something (question or assertion, positive or negative) push a response in one direction or another?