The purpose of voting is for individuals to say "this node is of helpful to the community" and "this node is harmful to the community".

I don't agree. I think that a reply like "read this documentation" or "I have an article on that" might be helpful to the community but I often downvote them, especially if a better answer occurs in the thread. In fact, my normal strategy for voting on the replies in a thread¹ is to try to order them best to worst (IMHO, of course) when viewed by reputation. I do that by first upvoting the reply which I think is best and sometimes by downvoting nodes which have a higher reputation than it does. (I order by rep so I know the relative order.)

For a node's reputation to have any meaning as a number, you'd need several other statistics

Other statistics would be nice. They aren't necessary.

Do you vote with any strategy other than a random one? Because, if you do, then you don't act as if node reputation is meaningless. It's ridiculous to cast a vote with intention and then argue that node rep is meaningless. I wholeheartedly agree that the meaning of a node's reputation is hard to pin down. It exists only in context. It's entirely relative. But that doesn't mean that it doesn't exist. I vote as if it does exist; therefore, it does.

My rule is, "Any moderation system that causes conversations to degenerate into discussions about the moderation system is broken." Omphaloskepsis is the death rattle of a community.

I think that contemplating the moderation system is a bit more like pondering one's tactile nervous system than his belly button.

1. This is the strategy I usually apply to replies to technical questions. On matters of opinion, like this thread for instance, I usually just upvote nodes I agree with. I upvote meditations and replies to them if I find them interesting.

Edit: Changed "A think" to "I think".

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Re: Re: A case for neutral votes by sauoq
in thread A case for neutral votes by dws

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.