Cheating in polls

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Log in
2. Go to topic with poll
3. In browser open new tab with same topic
4. Vote in first tab
5. Vote in second tab

What is the expected output? What do you see instead?
Should give a vote and show results and in second tab should give error. 
Using this cheat you can vote forever and you can see the results only 
when logged out or using other account.

What version of the product are you using? On what operating system?
Revision 10

Please provide any additional information below.
Old bug from XMB

Original issue reported on code.google.com by martii...@gmail.com on 19 Feb 2010 at 7:27

[GoogleCodeExporter]

Original comment by vande...@gmail.com on 20 Feb 2010 at 3:53

• Changed state: Accepted
• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Original comment by vande...@gmail.com on 20 Feb 2010 at 3:54

• Added labels: Component-Logic, Usability

[GoogleCodeExporter]

Original comment by vande...@gmail.com on 7 Apr 2010 at 11:09

• Added labels: Milestone-Sprint2

[GoogleCodeExporter]

The problem with this defect is that a voting history would have to be 
maintained. XMB 1.8 did it using a field 
within the thread / post, but that would max out at around 200 voters, no 
matter what. 

I could put in a vote history into the user's member record. This would allow 
us to keep the most recent 200 or 
so votes. That would significantly hamper vote rigging. However, it still 
doesn't prevent mass signups and voting 
from each new account. 

Original comment by vande...@gmail.com on 11 Apr 2010 at 1:22

[GoogleCodeExporter]

Moved to Milestone 3

Original comment by vande...@gmail.com on 4 May 2010 at 2:09

• Added labels: Milestone-Sprint3
• Removed labels: Milestone-Sprint2

[GoogleCodeExporter]

This is just too hard to fix, and honestly, if you figure it out, you deserve 
to cheat :)

Original comment by vande...@gmail.com on 15 Dec 2011 at 1:48

• Changed state: WontFix