Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
It appears that the most common route taken is to pick an author and just systematically vote for (or against) every one of their nodes. So I think it appropriate and useful to reduce the number of votes one can cast if one is only casting them toward a single author. The tough part for me is how to (mildly) discourage casting most of your votes for a single author while not unduely causing frustration when one reasonably runs into several nodes by one author that all deserve an up-vote.

I see a certain 'danger' (probably a word with too many negative connotations for the exitable, but...) in such an implementation, and perhaps you have already considered them...

One of my "voting behaviours" is to sometimes seek out (via Super Search some area of interest, say, charting and graphing, and work my way back through those threads with promising authors/titles. As I do so, I very often find old nodes/entire threads still worthy of an upvote. And so I find myself sometimes casting many votes on a given topic.

Now, the 'danger' I perceive here is that, possibly, because of my choice of topic, it may appear (to an algorithm, anyway) that I am casting a disproportionate number of votes for a given author... Say, our very wise zentara may receive a "showering" of upvotes simply because he seems to hold the corner on the market for Tk and Gtk2 knowledge.

So, my question is, might node age and also node topic (perhaps using keywording) influence the determination of whether or not a disproportionate number of votes is going to one author?

HTH,

planetscape

In reply to Re: History now influences voting by planetscape
in thread History now influences voting by tye

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (2)
    As of 2014-10-22 03:28 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      For retirement, I am banking on:










      Results (112 votes), past polls