Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

IRV has a non-complicate-to-explain problem: you can screw up the ballot and invalidate your vote.

> Unlike many single-winner methods, instant-runoff cannot accept equal rankings, and must discard ballots with multiple first-preferred remaining alternatives: such ballots would be equivalent to casting multiple ballots in a plurality election

With all-the hubbub on the last election about vote validity, and hanging chads before that, the last thing we need is screw-up-able ballots.

IMHO we should not even consider any methods in which you can violate invariants on a paper ballot. That rules out FPTP, IRV, and any others where the user with pen-and-paper can enter an invalid state.

Err, I guess that rules out 321, which is my new favorite. Simple fix: just count multi Bad/Ok/Good entries toward that total. In the first round, you only look at "good" scores, ignoring ok/bad. Then in the bad round, same thing. This ensures a) you can't produce a bad ballot b) ballot counts stay orthogonal for each category c) multi-entries kinda average out.

E2: well I guess you can manage to screw up ANY style of paper ballot and violate some invariant. I guess it matters the difficulty of screwing it up and whether it's recoverable.



I think 321 lets you have as many good/bad/ok candidates as you like. The thing it doesn't allow is marking a candidate as, say, both good and bad at the same time. (I'm not an expert though, I just heard about 321 yesterday, and my source of knowledge is the most plausible-looking google search result.)

I agree that a likelihood of higher-than-normal percentage of spoiled ballots is a potential problem with IRV, at least with mail-in or in-person paper ballots. Voting machines shouldn't have a problem with it.

Approval is about as simple as it gets. In order to spoil the ballot you'd have to do something pretty strange like tear the ballot in half. Or with mail-in ballots, the usual things like not signing the envelope (assuming that's required in your state) or mailing it too late to arrive on time.

I don't see ballot spoiling as necessarily a show-stopper for using RCV on its own, but there are other compelling reasons not to use it (such as failing monotonicity).


It's easy enough to have a scanner reject an invalid ballot and force you to fill out a new one. At least in NYC where I vote, you feed it into the scanner yourself.

And you've always been able to produce invalid ballots, like voting for two candidates when you're only allowed to pick one.

You're describing a UX problem which has UX solutions. It's not even remotely a justification for selecting a democratic procedure to express the will of the people.


Another benefit of Approval Voting ballots is you basically cannot spoil them. You can't rate/rank the same candidate more than once, and marking multiple candidates is valid.


> You're describing a UX problem which has UX solutions. It's not even remotely a justification for selecting a democratic procedure to express the will of the people.

Agreed but that's far from my only gripe with FPTP and IRV.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: