I think the monastery use an IP based system,
but it's not foolproof and you will block all the people behind the same router
(in the case of lan doing NAT behind a router )
after the first vote...

Forget cookies or UserAgent or referers...(too easy to delete/fake IMHO)

A possible way could be to have a challenge with one part computed by the client (java class?)
with client hardware's info as part of the computation to ensure uniqueness
I've never went into this although, I was just wondering...

UPDATE : To step away from theory, and give more details :

• Don't forget to store somewhere those who have already voted
• A challenge to prevent replay attacks
• using client hardware's info (MAC address,CPU ID in some case,DMPI/BIOS info...) for uniqueness
• Java class for client side (and WEAK obfuscation)

"Only Bad Coders Code Badly In Perl" (OBC2BIP)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.