Approval voting

by
in pipedot on (#3G3)
This week's poll is an example of the Approval voting method. Note that the items are checkboxes instead of the traditional single choice radio button. Please check all the features that you would prefer to see on this site sooner-rather-than-later. I plan on adding all of these features (except the NSA option - that one is a joke!) over the next few weeks. This poll will give me some feedback on which features are the most popular. For example, if nobody really cares about the Achievement system, I'll know to not spend too much time on it.

Approval Voting is Under-Rated (Score: 5, Insightful)

by prospectacle@pipedot.org on 2014-03-16 07:22 (#KH)

Good work on choosing approval voting!

Single-vote (first past the post) methods are terrible methods of translating voter will into meaningful results. They discourage most people from voting and most candidates from running, and produce divisive results (see american presidential elections). If most people dislike a particular candidate, it can still win, because the vote against it may be split between the other options, since people can only express their first preference, and nothing else.

Preferential (ranked) voting systems can be ok, but it gets complicated when you decide how to count the preferences. If you use instant-runoff (eliminate the least popular candidate if there is no majority, then re-distribute the second-preferences from those votes. Repeat until someone has a majority) is divisive, because most people who didn't vote for whoever ends up winning, do not get their preferences counted at all. This is because their first-preference option doesn't get eliminated before a majority is reached by another candidate.

There are some decent preferential systems (e.g. borda count, kemeny-young), but they all suffer from arrow's impossibility theorem (which shows that they're all flawed in some key aspects).

Approval voting is simple to use, simple to count, and tends to produce consensus results.

This site doesn't appear to have a whole team of volunteers like SoylentNews (which I also like), so progress is slower, but I very much like and admire the effort. Consider me sold.
Post Comment

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/get/main/post.php:58) in /var/pipedot/lib/tools/tools.php on line 1540

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/get/main/post.php:58) in /var/pipedot/lib/tools/tools.php on line 1549

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/get/main/post.php:58) in /var/pipedot/include/common.php on line 80

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/get/main/post.php:58) in /var/pipedot/include/common.php on line 82
Fatal Error - sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.216.171] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null] - Pipedot
Fatal Error
sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.216.171] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null]
Subject
Comment