Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sites may use a combination of the following to try and identify flooding or abuse of a form such as an online poll. No method is completely infallible; in fact, most are trivial to fool.</p> <p>Identifying the same person:</p> <ul> <li>Setting a cookie (such as a session cookie)</li> <li>Comparing the IP address</li> <li>A hueristic approach having a cookie, and comparing part of the IP address (a /24 subnet) and/or user-agent as a backup when there's no cookie.</li> </ul> <p>Preventing other types of abuse:</p> <ul> <li>Flood control: don't allow more than a certain number of votes per minute from a certain IP subset, or from everyone.</li> <li>Spam detection: try to detect bots by signature (eg malformed user-agent or accepts header, etc)</li> </ul> <p>Making the user jump through hoops:</p> <ul> <li>CAPTCHA/robot detection</li> <li>Making the user confirm their vote by email</li> <li>Making the user register, provide a unique email address, confirm the email address</li> </ul> <p>For every measure there's an equal and opposite counter-measure. For example, an abuser might ignore cookies, vary his user-agent or use an anonymiser service that varies his IP address for every request. He might sign up using multiple accounts with throw-away email addresses, and there are even ways to try and defeat CAPTCHA (eg. replay the CAPTCHA for users on another site).</p> <p>Note that to someone who is determined to disrupt, an evercookie doesn't do much more for you than a cookie. They wouldn't affect a bot, for example.</p> <p>I personally do not like to use the barriers that make users jump through hoops. Hopefully I've demonstrated that even if you require registration you are not guarding against abusers all that much more than you would with a good flood control algorithm, since it's trivial to get multiple throwaway email addresses.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload