in reply to Blank votes, and total vote count display.

"Introduce a possibility to show how many votes were cast on a specific node."

That I agree with. But only after I have voted myself, or if I'm the author. It would make sense to know the interest a node has created. A node with +4 looks as if noone cared (well almost), when in reality the node may have been given 100 minus votes and 104 plus votes. I.e. a lot of interest. This would be very informative if nothing else so for the author of the node. "I wrote a node and people cared (or not)"

I'm not part of the Monastery developers, but I would be surpriced if this information is stored in the database. I guess that only the net 'reputation' is stored. Which would make it impossible to show the 'activity' on historical data.

Everything went worng, just as foreseen.

  • Comment on Re: Blank votes, and total vote count display.

Replies are listed 'Best First'.
Re: Re: Blank votes, and total vote count display.
by ignatz (Vicar) on Apr 11, 2002 at 14:12 UTC
    Agreed. For me the volatility of a node is just as interesting as its rep. I would love to know how many people voted -- on something that somebody wrote. 
    ()-()
 \"/
  `                                                   `
[reply]
Re: Re: Blank votes, and total vote count display.
by demerphq (Chancellor) on Apr 10, 2002 at 18:00 UTC
    No, every vote cast is recorded. That way duplicate voting and or vote rigging is prevented.

    I like the idea of showing the total votes though.

    Yves / DeMerphq
    ---
    Writing a good benchmark isnt as easy as it might look.

[reply]

      I understand how this will avoid dupes, but how can it help to avoid vote rigging?

      Everything went worng, just as foreseen.

[reply]
Re: Re: Blank votes, and total vote count display.
by Dog and Pony (Priest) on Apr 10, 2002 at 15:54 UTC
    Well, I can only guess too. :)

    But the DB keeps track on which nodes I have voted on in one way or the other, so it shouldn't be impossible. The question is, is it stored on the node who has voted - easy and cheap query to count who has voted, or is it stored on the user where the votes have been cast - not as cheap a query (I wouldn't think at least). This query would need to be cheap, since it is potentially executed lots of times per rendered page.

    Of course, another approach would be to add a field to the DB now, and start with this system from now on. If people want it. :)

    You have moved into a dark place.
    It is pitch black. You are likely to be eaten by a grue.
[reply]

In Section Perl Monks Discussion