comment on

I guess you mean "genuine criticism" in the sense of the intro line from the old series The Critic: "It Stinks!". I think that intro line was meant to be ironic.

I meant it more in the sense of "downvoting a crappy node" versus "exercising a vendetta against a poster". In my opinion, there are plenty of reasons for downvoting out of genuine criticism:

incorrect answer to a question
boring or otherwise uninsightful meditation
bad suggestions for changes to Perl Monks
inappropriate language (profanity, personal attacks)
trolls

In many of those cases, it's not even worth the time for a written reply -- so I guess in that sense, a downvote does just mean "It Stinks!"

N.B. I missed the $vtavg in the chance of losing XP in my first readthrough -- that does lessen the impact substantially and probably does away with the need for my suggestion #2.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re^2: History now influences voting by xdg
in thread History now influences voting by tye

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.


Don't ask to ask, just ask
	PerlMonks