Congratulations, you two have come up with two of the four "solutions" I came up with long ago. One makes things a bit fairer for people behind a firewall with a shared public IP address while doubling the chances for repeated voting for the most typical situations. The other does the best job of reducing repeat voting (but is still trivially worked around and so doesn't improve the current situationn all that much).

So neither is much if any of an over-all net improvement. Hence, I don't see much point in spending resources to implement either.

For the record, describing all five options in terms of how the code would work rather than via an example chronology:

Current method. You can't vote if:

First proposal above (by vcTheGuru). You can't vote if any of the following are true:

Second proposal above (by ikegami). You can't vote if any of the following are true:

The proposal I first seriously considered long ago. You can't vote if any of the following are true:

The second proposal I considered long ago. You can't vote if any of the following are true:

I personally think that the last one is the best of the bunch. But it still doesn't reduce the number of duplicate votes that anyone can cast. It is a bit "fairer" for people sharing a public IP address, but then most people have another public IP address that they don't share (at least not with the same people), especially if they go slightly out of their way. So, when you consider that this is just about rather silly polls and people can still reply to them, it never became a priority to me to thrash the DB design and rewrite the "deal with poll votes" code (which isn't just "one place", FYI).

Oh, vcTheGuru wrote:

Hi, thanks for the reply and considering this seriously.

Well, I hope this reply does show that I had already considered this seriously (if, in fact, only briefly). For the record (just in case you didn't notice), my previous reply was a bit sarcastic. In particular "this is our highest priority" was irony. Other parts contained sarcasm as well but I was sincere in noting that you hadn't demonstrated that you had considered all of the possibilities. And I am glad that you did follow through on that point.

The other part nobody has yet mentioned is voting on previous polls. Something that is also not worth "fixing", IMHO (it isn't, strictly speaking, "broken" and you can't really "fix" it completely either, but there could certainly be improvements made on some fronts but not without trade-offs that are too expensive on other fronts).

- tye        

In reply to Re^4: Could vote multiple times in voting booth (awe) by tye
in thread Could vote multiple times in voting booth by atemon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.