Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Re: Choose a maximum for Rep

by chipmunk (Parson)
on May 25, 2001 at 05:34 UTC ( #83206=note: print w/ replies, xml ) Need Help??


in reply to Choose a maximum for Rep

If you don't think a node is worthwhile, just don't vote on it. I'm afraid I don't see the benefit to putting this level of selection into the voting system.

If you're one of the first ten voters, your ++<10 vote counts, and then another person votes, so the node has a rep of 11 even though you didn't want to vote it above 10.

On the other hand, if you're the eleventh voter, your ++<10 vote doesn't count, leaving the node with a rep of 10, based on nothing more than the order in which the votes were cast.

This system would make the votes of monks who vote first less valuable than the votes of those who vote later.


Comment on Re: Choose a maximum for Rep
Re: Choose a maximum for Rep
by lemming (Priest) on May 25, 2001 at 06:06 UTC

    The reason I came up with this is because I find some nodes worthwhile, just not that worthwhile.

    I disagree that votes become more or less valuable. They're as valuable as you think they are. Another option is if you vote ++<10 and it's already there, you don't spend a vote.
    Several monks actually -- votes that are at certain levels because they feel that the rep has exceeded the actual worth.
    Sometimes you want to vote on a node just to see the rep and this would allow that.
    Of course you could extend the logic so that a vote with a cap of 10 would -- a node that already has 20, or set up some mathamatical expresion if you want to get more complicated.

    Anyway, it's just an idea. I'm not attached to it.

      I believe that, under your proposal, votes cast later would be more valuable than votes cast earlier.

      Here's a statistical proof. This code tries random orders of voting, keeping track of where in the order your vote is cast, and calculates the average reputations.

      #!/usr/local/bin/perl -w use strict; $| = 1; my @all = ((5) x 6, (10) x 6); # twelve voters: six voting up to 5, six voting up to 10 for my $own (5, 10) { # your own vote my $i = 0; my @others = grep $_ != $own || $i++, @all; # remove your vote from the list for now... my(%r, %n); for (1 .. 5000) { my @voters = shuffle(@others); # shuffle the other votes splice @voters, my $pos = int(rand @voters+1), 0, $own; # put your vote back in, and save the position my $rep = 0; for my $v (@voters) { $rep++ if $rep < $v; } # calculate the reputation $r{$pos} += $rep; $n{$pos}++; # adjust the stats for this position } print "$own:\n"; for (sort { $a <=> $b } keys %n) { printf " %2d %4d %4.2f\n", $_, $n{$_}, $r{$_} / $n{$_}; } # print position, number of occurences, and average reputation } sub shuffle { my @list = @_; for (my $i = $#list; $i >= 0; --$i) { my $j = int rand $i + 1; @list[$i, $j] = @list[$j, $i]; } @list; }
      And some results (your position / occurences / mean reputation):
      5: 0 411 8.77 1 404 8.80 2 409 8.77 3 414 8.74 4 411 8.76 5 452 8.25 6 393 8.36 7 425 8.28 8 409 8.32 9 417 8.31 10 444 8.29 11 411 8.23 10: 0 386 8.17 1 439 8.15 2 420 8.25 3 435 8.14 4 393 8.21 5 407 8.74 6 437 8.73 7 412 8.71 8 444 8.69 9 402 8.67 10 399 8.77 11 426 8.75
      Observe that the node's reputation will be closer to what you personally want if you vote later. If you're voting low, a later vote leads to a lower rep; if you're voting high, a later vote leads to a higher rep.

      Several monks actually -- votes that are at certain levels because they feel that the rep has exceeded the actual worth.

      <rant>
      If this is true, I do not see how this is any different from the personality voting that has been railed against so strenuously. Instead of voting (or ignoring) a node's content, you are voting its Reputation.

      If those doing this are against personality voting or would rather see more votes given to code, then I ask them to reconsider this practice. I do not believe it's necessary to "take a monk down a peg" for anything other than a bad node.

      Vote the node's content, not the poster nor the node's reputation.
      </rant>

      --f

        I do this quite a bit. I don't understand how this is "taking a monk down a peg"? The monk got 64 votes and a few dozen XP for a too-short, too-simplistic, mostly-but-not-completely-correct reply. After all of that, my downvote doesn't hurt much at all.

        Better than that, it helps (in some tiny, tiny way -- which is about all you can hope for with a single vote) to discourage monks from posting too quickly "just because" short, easy-to-understand, fast replies tend to get more ++ votes due to community dynamics.

        I also sort replies by rep and so I sometime downvote nodes that are "listed too high" in comparison to other replies.

        And none of this is "voting the reputation". I vote the node contents but I take the node's reputation (and the node's author) into consideration!

        I'm very reluctant to downvote newbies as that just leads to a bad initial experience when they don't even know enough to learn from the downvote. I'm relatively reluctant to upvote nodes by those with high XP (I know they can post "good" nodes quite a bit, so I want to see something that is "a good node, considering who wrote it") or that have recently posted a ton.

        I upvote nodes that have too low of a rep when I think I understand the reason for the low rep and that I don't agree with that reason (for example, if a node dares to say something negative about "perl" but is accurate). In a "discussion" I will only upvote the very best of the thread while in "code" threads I may upvote the entire thread because I find that "discussion"s get higher reps than "code" threads (if that changes, then so will my voting).

        So I'm left to assume that footpad does a sort of mindless, feel-good upvoting only and doesn't take much of anything complex into consideration {duck}. If I had more choices in voting besides -, +, 0, then I might not need to use downvoting as often in order to satisfy my desire to have my votes make sense to me.

        I do make an effort to not downvote in a way that is likely to result in an "Ack!" message nor in a node with a negative reputation, because I don't particularly like either of those except in extreme cases. But, in the current environment of 98% upvotes, I do downvote quite a bit. Just because I vote this way doesn't mean I want everyone to vote this way (if everyone else did vote this way, I certainly wouldn't anymore!).

                - tye (but my friends call me "Tye")

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://83206]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (13)
As of 2014-10-31 17:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (221 votes), past polls