Hi, >Bugzilla implements that kind of authentication to avoid reports from >faked people that do not intend to provide feedback later.
Which is what you want, for a good voting system. You want users, who took the time to search through the active database, to cast their vote, so developers get some idea of the impact of the bug. Registration is a 2-step (do + confirm) boundery that takes away a lot of the potential voters, for reasons ranging from lack of anti-paranoia medication to time constraints and Jolt overdose. > > Floods can be easily detected, and bugs which outstand tremendously can > > be investigated. > >The problem to avoid here are not exactly floods, but the occasional >user that in the hope of having his reports addressed with greater >priority would submit say like 12 votes. How would you tell if those >votes would be from the same user or not? You wouldn't and an IP/cookie based session, would take care of most of that. If somebody actually takes to the time to use multiple IP addresses, and browsers to cast a not too suspiscious amount of votes over a lenghtly period of time, let's just reward this frustration, before the poor guy jumps off some building. No matter what procedural importance you award to the voting tool, it will be <em>one of the</em> factors, which stimulates a (group of) developers to work on a bug. Met vriendelijke groeten / With kind regards, IDG.nl Melvyn Sopacua Webmaster <greeting season="newyear"> XML-error: undefined entity "peace" at line 1. </greeting> -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
