Voting settings

fv-voting-security-and-frequency

Voting type

  • Like (+1)
    Users can vote in linear mode (each vote increase total votes to 1)
  • Rate
    Users can set rating of photo (for example from 0 to 10) and photo will have 2 totals: total votes and avg rating (for example 10 votes and 7.5 rating).

Frequency of voting

How many votes user can can in contest during specified period (6 hours, 12 hours, 24 hours, day [00-24], all contest).

If set 0 – user can vote once for each photo.

Note: user cannot give more than one vote on the same photo.

Example: if voting period is 6 hours and user can cast max 5 votes and user voted for photo 123, he can’t vote again for this photo 123 at next 6 hours (other 4 votes he can cast for other photos).

Contest security type

IP + cookies + evercookie

Check:  voter IP and evercookie is recorded in the votes table. So if the voter uses a shared IP (like at university, company etc.) or tries voting again from the same browser, they might not be able to vote.
Effectiveness: Not extremely effective, but simple for users.

 cookies+evercookie

Check: borwser cookies (with changing borwser or using private tabs user can vote unlimited times [can be fixed just with using “Social authorization” or “Authorized user” Additional security]).
Effectiveness: very bad (wihtout “Additional security” like “Social login” or “Authorized user”), but allows votes from shared IPs – like at university, company etc.

Additional security

 reCaptcha (reCaptcha key required)

Check: like above but user must match the reCaptcha every time, when vote button is clicked (or if saving reCaptcha session is enabled, session is kept for 30 minutes).
Effectiveness: enough effective with IP checking, but not so comfortable for users and creates more server load (for every vote your site sends a reCaptcha request to Google).

 Subscribe form

Details: when user makes their first vote, they will have to fill a subscribe form with name & email fields; after the form is submitted the data saves to user session and voting can start.
Check: is user already have “Subscribe session”. If yes- can vote, if no – will be shown “Subscribe” modal (if already subscribed – user can enter the same details as before and if Name & Email equals, voting will be allowed).
Effectiveness: Not very effective, but simple for users.
Example: https://yadi.sk/i/TGz1dvJ6wbdHt

 Facebook Share (required FB app ID)

Details: when vote is clicked, opens a Facebook sharing popup window with the current photo and the vote will be registered when they click Share.
Notes: user must have a Facebook account.
Effectiveness: equals selected “Contest security type” (as any additional security check are not happens)
Usage details: rarely used, but can be useful if voting frequency is once per all contest.

 Social login

Details:

  1. Voter clicks “Vote”
  2. A popup with allowed social networks shows up – https://yadi.sk/i/PRSGu6TsmD2Ta
  3. User clicks on the network of their choice and allows access to their profile (First & last name & sometimes email)
  4. The data is sent to server and saved in session
  5. Vote is registered

Check: same as in Default + unique social user ID.
Notes: this does not create any account for the user, all data stored in PHP session.
Second login with the same account: in second login with the same social account Permission request window don’t shows.
Facebook note: by default, external service is used for authorization but when you set up Facebook app ID in settings, then self-hosted Facebook login will be used.
Effectiveness: good.

 Authorized user

Check: browser cookies and user ID.
Requirements: user must be logged in on the website else they can’t vote and will see a message like “You must be logged in to vote!”.
Usage details: useful if you want to motivate user registration on the site or of the most part of voters are already site members.
Effectiveness: pretty good (users can create many accounts to cheat on the votes though).


Last update 29/04/2017