BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Govt Source Code Policy
- Subject: [Discuss] Govt Source Code Policy
- From: jc at trillian.mit.edu (jc at trillian.mit.edu)
- Date: Wed, 06 Apr 2016 17:34:55
- In-reply-to: 20160406165112.GL3387@randomstring.org
- References: 20160406165112.GL3387@randomstring.org, <chxy48tkulo.fsf@iceland.freeshell.org> <5702D47C.3010104@gmail.com> <57032657.9080508@mattgillen.net> <57033925.50705@gmail.com> <CANaytcc=X1cB4ov4r7o9upb3qgJ_AT=ArUyrQ0fsL5ZhxN=B+w@mail.gmail.com> <20160406123255.07647776@mydesk.domain.cxm> <20160406163655.GK3387@randomstring.org> <20160406124740.3ce87ed0@mydesk.domain.cxm>
| On Wed, Apr 06, 2016 at 12:47:40PM -0400, Steve Litt wrote: | > On Wed, 6 Apr 2016 12:36:55 -0400 | > Dan Ritter <dsr at randomstring.org> wrote: | > | > > I'm perfectly good with the current method we use in Waltham: you | > > fill out your paper scantron ballot, you put it in the machine | > > yourself, the vote counter increments, and your ballot is saved | > > in the lockbox for recounts or verification. | > > | > > It involves software, but not much. | > > | > > -dsr- | > | > The system you articulate would be even better if it gave the voter a | > receipt showing his/her choices. I like the lockbox for the paper | > ballots. | | Actually, such a receipt is a really bad idea -- it has enabled | vote selling. There are various schemes to enable voters to get | some token from the machine which signifies that they voted and | can handle verification that the vote was counted, but they are | always much more complex and expensive... and prone to rigging. | -dsr- Indeed; when such schemes have been tried, the inevitable result is employers giving their employees a page listing how to vote, with the understanding that if you don't have the proper voting receipt, you shouldn't bother showing up at work at al. -- ------------------------------------------------------ _' O <:#/> John Chambers + <jc at trillian.mit.edu> /#\ <jc1742 at gmail.com> | |
- Follow-Ups:
- [Discuss] Govt Source Code Policy
- From: slitt at troubleshooters.com (Steve Litt)
- [Discuss] Govt Source Code Policy
- References:
- [Discuss] Govt Source Code Policy
- From: smallm at sdf.org (Mike Small)
- [Discuss] Govt Source Code Policy
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Govt Source Code Policy
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] Govt Source Code Policy
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Govt Source Code Policy
- From: greg at freephile.com (Greg Rundlett (freephile))
- [Discuss] Govt Source Code Policy
- From: slitt at troubleshooters.com (Steve Litt)
- [Discuss] Govt Source Code Policy
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] Govt Source Code Policy
- From: slitt at troubleshooters.com (Steve Litt)
- [Discuss] Govt Source Code Policy
- Prev by Date: [Discuss] (Location Change) BLU Desktop GNU/Linux SIG Meeting - Music - Weds, Apr 6, 2016
- Next by Date: [Discuss] Govt Source Code Policy
- Previous by thread: [Discuss] Govt Source Code Policy
- Next by thread: [Discuss] Govt Source Code Policy
- Index(es):