While I think the ideas are good, one of the problems that we get here, that was recently mentioned in the thread about Newsgroups, etc, is that there are newbies that do not want to do the 'homework' that reasonably ought to be done before posting their question; they want *a solution* (not just an answer, the difference between like giving a hungry man fish, and teaching a hungry man how to fish) within a few minutes time. One solution that I've mentioned is to disallow the posting by new users for at least 3 days; this would prevent PM from being bogged down by those that want the fast answer and don't want to further work with the community (Anyone have any good stats on how many level 1 accounts are still active?) But this solution will fail as long as there is the Anon. Monk, and I don't believe it's wise to get rid of that. One similar solution is that if you are posting as AM, you are informed that your root-level post will not be visible to the bulk of the users for 24 hrs, and program this in specifically; again, this might drive off those looking for *a solution* inside of an answer.

Sure, there are things that we can do without any modification of the engine by vroom, but there's only so much that we can do in this case, many of the above suggestions are good. But again, I think it does come down to a bit of frustration seeing questions that are clearly marked in the man pages or FAQs asked over and over without indication that they even tried. (two nights ago in the CB, there was discussion of a Tutorial of How to RTFM. This really doesn't sound like a bad idea in this case...)

---

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

---

---

• 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.