I know that to implement what I am about to suggest would be a major departure from the status quo, but I think it might be helpful. I just wrote a reply concerning voting and I started thinking that perhaps I might be on to something. Consider that currently people vote for or against a post without giving any idea why they are voting for or against. I've read a few different threads where people explain that they all have different reasons for voting for or against a post. Because of this, I am thinking that it might be helpful to have categorized voting.
Each post would have seperate scores for accuracy, helpfulness, etc. It would help newcomers feel more comfortable using certain posts as references, even if they themselves are not sure of the solution's accuracy. If this type of voting were adpoted, we could have accuracy ratings for authors (for example, if some user never wrote accurate posts, their rating would be low, and newcomers would know to stay away from that users posts when looking for information). I would recommend that these accuracy votes be limited to monks of a certain level, as I often read that lower level monks vote randomly to increase their XP/level. Anyway, just a thought...
--Ivory
-
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.
|
