Fri Apr 26 15:14:12 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2020-07-01

HANGOUT

2024-04-26 | 2024-03-26 | 2024-02-26 | 2024-01-26 | 2023-12-26 | 2023-11-26 | 2023-10-26 | 2023-09-26 | 2023-08-26 | 2023-07-26 | 2023-06-26 | 2023-05-26 | 2023-04-26 | 2023-03-26 | 2023-02-26 | 2023-01-26 | 2022-12-26 | 2022-11-26 | 2022-10-26 | 2022-09-26 | 2022-08-26 | 2022-07-26 | 2022-06-26 | 2022-05-26 | 2022-04-26 | 2022-03-26 | 2022-02-26 | 2022-01-26 | 2021-12-26 | 2021-11-26 | 2021-10-26 | 2021-09-26 | 2021-08-26 | 2021-07-26 | 2021-06-26 | 2021-05-26 | 2021-04-26 | 2021-03-26 | 2021-02-26 | 2021-01-26 | 2020-12-26 | 2020-11-26 | 2020-10-26 | 2020-09-26 | 2020-08-26 | 2020-07-26 | 2020-06-26 | 2020-05-26 | 2020-04-26 | 2020-03-26 | 2020-02-26 | 2020-01-26 | 2019-12-26 | 2019-11-26 | 2019-10-26 | 2019-09-26 | 2019-08-26 | 2019-07-26 | 2019-06-26 | 2019-05-26 | 2019-04-26 | 2019-03-26 | 2019-02-26 | 2019-01-26 | 2018-12-26 | 2018-11-26 | 2018-10-26 | 2018-09-26 | 2018-08-26 | 2018-07-26 | 2018-06-26 | 2018-05-26 | 2018-04-26 | 2018-03-26 | 2018-02-26 | 2018-01-26 | 2017-12-26 | 2017-11-26 | 2017-10-26 | 2017-09-26 | 2017-08-26 | 2017-07-26 | 2017-06-26 | 2017-05-26 | 2017-04-26 | 2017-03-26 | 2017-02-26 | 2017-01-26 | 2016-12-26 | 2016-11-26 | 2016-10-26 | 2016-09-26 | 2016-08-26 | 2016-07-26 | 2016-06-26 | 2016-05-26 | 2016-04-26 | 2016-03-26 | 2016-02-26 | 2016-01-26 | 2015-12-26 | 2015-11-26 | 2015-10-26 | 2015-09-26 | 2015-08-26 | 2015-07-26 | 2015-06-26 | 2015-05-26 | 2015-04-26 | 2015-03-26 | 2015-02-26 | 2015-01-26 | 2014-12-26 | 2014-11-26 | 2014-10-26 | 2014-09-26 | 2014-08-26 | 2014-07-26 | 2014-06-26 | 2014-05-26 | 2014-04-26 | 2014-03-26 | 2014-02-26 | 2014-01-26 | 2013-12-26 | 2013-11-26 | 2013-10-26 | 2013-09-26 | 2013-08-26 | 2013-07-26 | 2013-06-26 | 2013-05-26 | 2013-04-26 | 2013-03-26 | 2013-02-26 | 2013-01-26 | 2012-12-26 | 2012-11-26 | 2012-10-26 | 2012-09-26 | 2012-08-26 | 2012-07-26 | 2012-06-26 | 2012-05-26 | 2012-04-26 | 2012-03-26 | 2012-02-26 | 2012-01-26 | 2011-12-26 | 2011-11-26 | 2011-10-26 | 2011-09-26 | 2011-08-26 | 2011-07-26 | 2011-06-26 | 2011-05-26 | 2011-04-26 | 2011-03-26 | 2011-02-26 | 2011-01-26 | 2010-12-26 | 2010-11-26 | 2010-10-26 | 2010-09-26 | 2010-08-26 | 2010-07-26 | 2010-06-26 | 2010-05-26 | 2010-04-26 | 2010-03-26 | 2010-02-26 | 2010-01-26 | 2009-12-26 | 2009-11-26 | 2009-10-26 | 2009-09-26 | 2009-08-26 | 2009-07-26 | 2009-06-26 | 2009-05-26 | 2009-04-26 | 2009-03-26 | 2009-02-26 | 2009-01-26 | 2008-12-26 | 2008-11-26 | 2008-10-26 | 2008-09-26 | 2008-08-26 | 2008-07-26 | 2008-06-26 | 2008-05-26 | 2008-04-26 | 2008-03-26 | 2008-02-26 | 2008-01-26 | 2007-12-26 | 2007-11-26 | 2007-10-26 | 2007-09-26 | 2007-08-26 | 2007-07-26 | 2007-06-26 | 2007-05-26 | 2007-04-26 | 2007-03-26 | 2007-02-26 | 2007-01-26 | 2006-12-26 | 2006-11-26 | 2006-10-26 | 2006-09-26 | 2006-08-26 | 2006-07-26 | 2006-06-26 | 2006-05-26 | 2006-04-26 | 2006-03-26 | 2006-02-26 | 2006-01-26 | 2005-12-26 | 2005-11-26 | 2005-10-26 | 2005-09-26 | 2005-08-26 | 2005-07-26 | 2005-06-26 | 2005-05-26 | 2005-04-26 | 2005-03-26 | 2005-02-26 | 2005-01-26 | 2004-12-26 | 2004-11-26 | 2004-10-26 | 2004-09-26 | 2004-08-26 | 2004-07-26 | 2004-06-26 | 2004-05-26 | 2004-04-26 | 2004-03-26 | 2004-02-26 | 2004-01-26 | 2003-12-26 | 2003-11-26 | 2003-10-26 | 2003-09-26 | 2003-08-26 | 2003-07-26 | 2003-06-26 | 2003-05-26 | 2003-04-26 | 2003-03-26 | 2003-02-26 | 2003-01-26 | 2002-12-26 | 2002-11-26 | 2002-10-26 | 2002-09-26 | 2002-08-26 | 2002-07-26 | 2002-06-26 | 2002-05-26 | 2002-04-26 | 2002-03-26 | 2002-02-26 | 2002-01-26 | 2001-12-26 | 2001-11-26 | 2001-10-26 | 2001-09-26 | 2001-08-26 | 2001-07-26 | 2001-06-26 | 2001-05-26 | 2001-04-26 | 2001-03-26 | 2001-02-26 | 2001-01-26 | 2000-12-26 | 2000-11-26 | 2000-10-26 | 2000-09-26 | 2000-08-26 | 2000-07-26 | 2000-06-26 | 2000-05-26 | 2000-04-26 | 2000-03-26 | 2000-02-26 | 2000-01-26 | 1999-12-26

Key: Value:

Key: Value:

MESSAGE
DATE 2020-07-15
FROM From: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?=
SUBJECT Subject: [Hangout - NYLXS] Don't let proprietary digital voting disrupt
From hangout-bounces-at-nylxs.com Wed Jul 15 17:47:31 2020
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id 75256163FB3;
Wed, 15 Jul 2020 17:47:31 -0400 (EDT)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id 4C2A0163FAD; Wed, 15 Jul 2020 17:47:29 -0400 (EDT)
Resent-From: Ruben Safir
Resent-Date: Wed, 15 Jul 2020 17:47:29 -0400
Resent-Message-ID: <20200715214729.GA339-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from mailout0p.fsf.org (mailout0p.fsf.org [209.51.188.184])
by mrbrklyn.com (Postfix) with ESMTP id 69E7F163FA0
for ; Wed, 15 Jul 2020 16:58:34 -0400 (EDT)
Received: from crmserver2p.fsf.org ([2001:470:142:5::223]:58786)
by mailout0p.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.90_1)
(envelope-from )
id 1jvoTx-0007GL-9f
for ruben-at-mrbrklyn.com; Wed, 15 Jul 2020 16:58:25 -0400
Received: from localhost ([::1]:60024 helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.90_1)
(envelope-from )
id 1jvoTn-0003FA-JO
for ruben-at-mrbrklyn.com; Wed, 15 Jul 2020 16:58:15 -0400
MIME-Version: 1.0
From: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?=
job_id: 161433
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.161433.56308113.8fa5b06af7f69f82-at-fsf.org
Date: Wed, 15 Jul 2020 16:58:15 -0400
Message-Id:
Subject: [Hangout - NYLXS] Don't let proprietary digital voting disrupt
democracy
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.30rc1
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,

List-Archive:
List-Post:
List-Help:
List-Subscribe: ,

Reply-To: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?=
Content-Type: multipart/mixed; boundary="===============0361151139=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============0361151139==
Content-Type: multipart/alternative;
boundary="=_b4073b9b828682e213fa8e8110055bec"

--=_b4073b9b828682e213fa8e8110055bec
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read and share online: *


*Please consider adding to your address book, which will
ensure that our messages reach you and not your spam box.*


Dear Ruben Safir,

Here at the Free Software Foundation (FSF), we fight for the freedom
of all software users. We believe that everyone has the right to
[understand and study][1] the systems that they use, and that not
being able to exercise this right is a violation of our freedom. This
applies to our personal software usage, but becomes even more
important in processes of democracy. It is particularly relevant for
the upcoming November 2020 elections in the United States.

[1]: https://www.gnu.org/philosophy/free-sw.html

A free country has the responsibility to make sure all of its
citizens can be heard, and that voting processes are transparent
and fair. So what happens if people are still self-isolating in
November, in order to try and prevent a [second wave of the novel
coronavirus][2]? As more of our life processes have gone online
due to the pandemic, we have seen [debates][3] rise over a call
for mail-in voting. This discussion seems to be clearing a path
for a [renewed interest][4] in online voting software as a remote
alternative to in-person voting. This is cause for grave concern.

[2]: https://www.businessinsider.com/fauci-second-coronavirus-wave-is-not-inevitable-in-the-fall-2020-5
[3]: https://www.cnn.com/2020/04/21/politics/mail-in-voting-partisan-divide/index.html
[4]: https://www.politico.com/news/2020/06/08/online-voting-304013

I am arguing in this post that it is essential that software used in
any part of the voting process be published free software. It is
unacceptable for such an important democratic system to be placed in
the hands of any for-profit, proprietary software corporation that
controls the source code, data management, reporting, updates, and
testing. No good can come from requiring a court order to be permitted
to study the source code of voting software in order to confirm the
process is fair and democratic. But additionally, I might surprise the
reader by laying out arguments to say that despite supporting the wish
to increase access and ease for all eligible voters, the only truly
free, ethical, and democratic voting system is actually a system that
steers clear from using software.

Technology can assist in the non-fundamental parts of the voting
process, like speeding up simple on-site calculations or verification
processes, in which case transparency is absolutely vital, and the
systems used must therefore be free software. Source code should be
provided freely for anyone to test the application, submit
modifications that can be adopted to improve the software, and make
recommendations, long before it has any opportunity to muddle with
results. But digital systems have no place in the key parts of the
voting system, including voter registration, casting a vote, and
tallying results. The experts agree on this, and I will explain why in
more detail below. Even when the source code is available, although we
can compel transparency and reproducibility, we still [risk
unacceptable vulnerabilities][5].

[5]: https://www.technewsworld.com/story/Next-US-Elections-Open-Source-vs-Commercial-Software-84794.html

The examples below demonstrate some of the pitfalls of using
proprietary software in the voting process, and why the peddlers
of proprietary software cannot be trusted with crucial democratic
processes.

### Tallying and the Iowa caucus fiasco

In February 2020, during the kickoff of the primary elections to
determine the US presidential candidates, the [Iowa caucus][6]
introduced a [newly developed app][7] designed to help tally votes and
make the results faster and more accurate. It did the opposite.

[6]: https://people.howstuffworks.com/iowa-caucus.htm
[7]: https://www.nytimes.com/2020/02/03/us/politics/iowa-caucus-app.html

The Iowa caucus failed due to [shoddy design and lack of testing][8]
of the app built by [Shadow Inc.][9], a for-profit technology company
that provides "smarter" technological infrastructure for Democratic
party campaigns. The flaws didn't surface until the primaries, because
of its proprietary nature. While the caucus results trickled in over
the days following the primary, debates arose about the accuracy of
its outcome, and voters started [questioning][10] the role that
technology should play in our elections. This fallout successfully
prompted other states to act with caution, and mostly scrap the plans
to use the same app.

[8]: https://www.cnbc.com/2020/02/04/iowa-caucus-app-debacle-is-one-of-the-most-stunning-it-failures-ever.html
[9]: https://abcnews.go.com/Politics/shadow-vendor-iowa-dems-reporting-app/story?id=68754002
[10]: https://www.cityweekly.net/utah/voting-app-blues/Content?oid=14861769

### Online voting applications

Even before the virus broke out, jurisdictions like Delaware, Georgia,
and Philadelphia had already committed to replacing existing systems
with digital voting machines, despite their [unacceptable risks of
interference][11].

[11]: https://www.politico.com/story/2019/03/01/election-vulnerable-voting-machines-1198780

Voatz, Inc. the for-profit company behind the private mobile [voting
app][12] by the same name, developed a pilot program in 2019, claiming
they delivered "secure" digital voting. The trial for the proprietary
app focused on people with disabilities and people residing
overseas. Colorado, Oregon, Utah, Washington, and West Virginia signed
up, but studies found that the app posed [security risks][13] like
leaving votes visible and exposing them to tamperers. Researchers from
the Massachusetts Institute of Technology (MIT) [reviewed the app][14]
and found an alarming number of [vulnerabilities and privacy
issues][15].

[12]: https://www.nytimes.com/2020/02/13/us/politics/voting-smartphone-app.html
[13]: https://www.politico.com/news/2020/05/01/coronavirus-online-voting-229690
[14]: https://internetpolicy.mit.edu/wp-content/uploads/2020/02/SecurityAnalysisOfVoatz_Public.pdf
[15]: https://www.technologyreview.com/f/615195/hackers-can-change-votes-in-an-online-election-app/

Now, in recent primaries, [some states][16] have implemented online
voting using a system called OmniBallot, claiming that it offers safe
remote voting during the virus. Democracy Live, the organization
behind the system used in Delaware, West Virginia, and New Jersey
states that the system is not *really* online voting, because a printed
ballot is still generated when the voter's ballot is downloaded by the
voting committee. But that doesn't account for the fact that the votes
are still cast [electronically and transmitted online][17], which
means they are [still vulnerable to tampering][18]. In fact, OmniBallot
was also reviewed by MIT, and again, the [conclusion][19] was that the
system is unsafe. It proved vulnerable to manipulation, and
additionally has no privacy policy to deal with the voter's sensitive
information.

[16]: https://reason.com/2020/06/10/amid-coronavirus-fears-2-states-will-allow-online-voting/
[17]: https://www.politico.com/news/2020/05/01/coronavirus-online-voting-229690
[18]: https://arstechnica.com/tech-policy/2020/06/researchers-say-online-voting-tech-used-in-5-states-is-fatally-flawed/
[19]: https://internetpolicy.mit.edu/wp-content/uploads/2020/06/OmniBallot.pdf

### Vulnerabilities explained

As much as different states want to spend millions of taxpayer
dollars to implement online voting systems to some degree or
another, there simply is no safe way to do so. [*The Observer*
explains][20] that an online system has to take into account too
many factors, from verifying identification to creating a secret
ballot, to voting and getting that vote to the committee, and
then verifying it again on the other end. To make it all secure
is nearly impossible.

[20]: https://observer.com/2020/06/election-security-why-cant-people-vote-online/

Security experts have long been expressing concern as well. After the
2016 US presidential elections, the National Academy of Sciences (NAS)
conducted elaborate research into the future of voting, and published
a report called ["Securing the Vote: Protecting American
Democracy."][21] The preface of this 157-page document states: "We
were constantly reminded in news stories, by congressional hearings,
and through reports from the intelligence community, of the
extraordinary threat from foreign actors using cyber weapons and
social media to manipulate the electorate, and to target our elections
and cast doubt on the integrity of the elections process."

[21]: https://www.nap.edu/read/25120/chapter/1

The report mentions that in 2016, the United States presidential
election was targeted by a foreign government, and voter information
was captured. While the exact consequences of this invasion are still
largely unclear, the fear of surveillance by outside parties and the
meddling with results is obviously justified. The NAS concludes that
the current system is vulnerable to internal and external threats, and
recommends [verifiable paper ballots][22], audits, and clear
distinctions between different elements of the process.

[22]: https://www.bostonglobe.com/2020/02/24/opinion/order-prevent-another-voting-debacle-turn-paper-balloting/

### Paper ballots and analog processes for democracy

Having full transparency and control is the only way in which we can
verify the legitimacy of elections. Transparency is currently best
accomplished by individual paper balloting. We will get the closest to
fair results by working with an analog system.

If we need to do remote voting, [contrary to some claims][23], mail-in
voting is a reliable fallback. [A study by Stanford University][24]
concludes that: "(1) vote-by-mail does not appear to affect either
party’s share of turnout; (2) vote-by-mail does not appear to increase
either party’s vote share; and (3) vote-by-mail modestly increases
overall average turnout rates, in line with previous estimates. All
three conclusions support the conventional wisdom of election
administration experts, and contradict many popular claims in the
media."

[23]: https://www.bostonglobe.com/2020/07/10/nation/fact-check-president-trump-keeps-calling-mail-in-voting-fraudulent-election-officials-advocates-say-otherwise/
[24]: https://siepr.stanford.edu/research/publications/neutral-partisan-effects-vote-mail-evidence-county-level-roll-outs

***

## Here's what you can do to stand up for your voting rights

#### Contact your representative
If you are in the US, please contact your [local representative][25] to
let them know you oppose electronic voting, and in particular
proprietary electronic voting. You can copy or personalize our
sample text:

[25]: https://www.congress.gov/members

> "Dear [Representive],
> I am [Name], and I live in your district.
> I am very concerned about the security and integrity of our
> voting systems, and do not think any computer-based system is
> safe, especially not any proprietary system. I agree with the
> Free Software Foundation article about the dangers of digital
> proprietary voting at , and request the use
> of only paper ballots in upcoming elections. Please oppose any
> move to digital voting systems, and advocate for our right to
> vote analog safely. Thank you."

> [Name], [City/State]

#### Tell your friends about the threat of digital voting on social media!
Use the tags \#NoDigitalVoting and \#UserFreedom on your favorite
[microblogging][26] sites.

[26]: https://www.fsf.org/share

>From voter registration to tallying, all steps in the voting
process could hypothetically be done digitally. But voting is a
highly personal, sensitive, and complicated system, one that
involves some of the most powerful stakeholders imaginable, and
where freedom is at stake. Free software shows us the system and
allows us to improve it. It does not, however, guarantee the
entire process to be unbreakable. Let's steer clear from digital
systems for now, for freedom.


Zoë Kooyman
Program Manager

--
* Follow us on Mastodon at , GNU social at
, Diaspora at ,
and on Twitter at .
* Read about why we use Twitter, but only with caveats at .
* Subscribe to our RSS feeds at .
* Join us as an associate member at .
* Read our Privacy Policy at .

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=161433&qid=56308113&h=8fa5b06af7f69f82.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=161433&qid=56308113&h=8fa5b06af7f69f82.
--=_b4073b9b828682e213fa8e8110055bec
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







Read and share online: https://www.fsf.org/blogs/community/dont-let-proprietary-digital-voting-disrupt-democracy





Please consider adding info@fsf.org to your address book, which will
ensure that our messages reach you and not your spam box.





Dear Ruben Safir,




Democracy



Here at the Free Software Foundation (FSF), we fight for the freedom
of all software users. We believe that everyone has the right to
understand and study the systems that they use, and that not
being able to exercise this right is a violation of our freedom. This
applies to our personal software usage, but becomes even more
important in processes of democracy. It is particularly relevant for
the upcoming November 2020 elections in the United States.



A free country has the responsibility to make sure all of its
citizens can be heard, and that voting processes are transparent
and fair. So what happens if people are still self-isolating in
November, in order to try and prevent a second wave of the novel
coronavirus
? As more of our life processes have gone online
due to the pandemic, we have seen debates rise over a call
for mail-in voting. This discussion seems to be clearing a path
for a renewed interest in online voting software as a remote
alternative to in-person voting. This is cause for grave concern.



I am arguing in this post that it is essential that software used in
any part of the voting process be published free software. It is
unacceptable for such an important democratic system to be placed in
the hands of any for-profit, proprietary software corporation that
controls the source code, data management, reporting, updates, and
testing. No good can come from requiring a court order to be permitted
to study the source code of voting software in order to confirm the
process is fair and democratic. But additionally, I might surprise the
reader by laying out arguments to say that despite supporting the wish
to increase access and ease for all eligible voters, the only truly
free, ethical, and democratic voting system is actually a system that
steers clear from using software.



Technology can assist in the non-fundamental parts of the voting
process, like speeding up simple on-site calculations or verification
processes, in which case transparency is absolutely vital, and the
systems used must therefore be free software. Source code should be
provided freely for anyone to test the application, submit
modifications that can be adopted to improve the software, and make
recommendations, long before it has any opportunity to muddle with
results. But digital systems have no place in the key parts of the
voting system, including voter registration, casting a vote, and
tallying results. The experts agree on this, and I will explain why in
more detail below. Even when the source code is available, although we
can compel transparency and reproducibility, we still risk
unacceptable vulnerabilities
.



The examples below demonstrate some of the pitfalls of using
proprietary software in the voting process, and why the peddlers
of proprietary software cannot be trusted with crucial democratic
processes.



Tallying and the Iowa caucus fiasco



In February 2020, during the kickoff of the primary elections to
determine the US presidential candidates, the Iowa caucus
introduced a newly developed app designed to help tally votes and
make the results faster and more accurate. It did the opposite.



The Iowa caucus failed due to shoddy design and lack of testing
of the app built by Shadow Inc., a for-profit technology company
that provides "smarter" technological infrastructure for Democratic
party campaigns. The flaws didn't surface until the primaries, because
of its proprietary nature. While the caucus results trickled in over
the days following the primary, debates arose about the accuracy of
its outcome, and voters started questioning the role that
technology should play in our elections. This fallout successfully
prompted other states to act with caution, and mostly scrap the plans
to use the same app.



Online voting applications



Even before the virus broke out, jurisdictions like Delaware, Georgia,
and Philadelphia had already committed to replacing existing systems
with digital voting machines, despite their unacceptable risks of
interference
.



Voatz, Inc. the for-profit company behind the private mobile voting
app
by the same name, developed a pilot program in 2019, claiming
they delivered "secure" digital voting. The trial for the proprietary
app focused on people with disabilities and people residing
overseas. Colorado, Oregon, Utah, Washington, and West Virginia signed
up, but studies found that the app posed security risks like
leaving votes visible and exposing them to tamperers. Researchers from
the Massachusetts Institute of Technology (MIT) reviewed the app
and found an alarming number of vulnerabilities and privacy
issues
.



Now, in recent primaries, some states have implemented online
voting using a system called OmniBallot, claiming that it offers safe
remote voting during the virus. Democracy Live, the organization
behind the system used in Delaware, West Virginia, and New Jersey
states that the system is not really online voting, because a printed
ballot is still generated when the voter's ballot is downloaded by the
voting committee. But that doesn't account for the fact that the votes
are still cast electronically and transmitted online, which
means they are still vulnerable to tampering. In fact, OmniBallot
was also reviewed by MIT, and again, the conclusion was that the
system is unsafe. It proved vulnerable to manipulation, and
additionally has no privacy policy to deal with the voter's sensitive
information.



Vulnerabilities explained



As much as different states want to spend millions of taxpayer
dollars to implement online voting systems to some degree or
another, there simply is no safe way to do so. The Observer
explains
that an online system has to take into account too
many factors, from verifying identification to creating a secret
ballot, to voting and getting that vote to the committee, and
then verifying it again on the other end. To make it all secure
is nearly impossible.



Security experts have long been expressing concern as well. After the
2016 US presidential elections, the National Academy of Sciences (NAS)
conducted elaborate research into the future of voting, and published
a report called "Securing the Vote: Protecting American
Democracy."
The preface of this 157-page document states: "We
were constantly reminded in news stories, by congressional hearings,
and through reports from the intelligence community, of the
extraordinary threat from foreign actors using cyber weapons and
social media to manipulate the electorate, and to target our elections
and cast doubt on the integrity of the elections process."



The report mentions that in 2016, the United States presidential
election was targeted by a foreign government, and voter information
was captured. While the exact consequences of this invasion are still
largely unclear, the fear of surveillance by outside parties and the
meddling with results is obviously justified. The NAS concludes that
the current system is vulnerable to internal and external threats, and
recommends verifiable paper ballots, audits, and clear
distinctions between different elements of the process.



Paper ballots and analog processes for democracy



Having full transparency and control is the only way in which we can
verify the legitimacy of elections. Transparency is currently best
accomplished by individual paper balloting. We will get the closest to
fair results by working with an analog system.



If we need to do remote voting, contrary to some claims, mail-in
voting is a reliable fallback. A study by Stanford University
concludes that: "(1) vote-by-mail does not appear to affect either
party’s share of turnout; (2) vote-by-mail does not appear to increase
either party’s vote share; and (3) vote-by-mail modestly increases
overall average turnout rates, in line with previous estimates. All
three conclusions support the conventional wisdom of election
administration experts, and contradict many popular claims in the
media."






Here's what you can do to stand up for your voting rights



Contact your representative



If you are in the US, please contact your local representative to
let them know you oppose electronic voting, and in particular
proprietary electronic voting. You can copy or personalize our
sample text:



"Dear [Representive],
I am [Name], and I live in your district.
I am very concerned about the security and integrity of our
voting systems, and do not think any computer-based system is
safe, especially not any proprietary system. I agree with the
Free Software Foundation article about the dangers of digital
proprietary voting at https://u.fsf.org/voting, and request the use
of only paper ballots in upcoming elections. Please oppose any
move to digital voting systems, and advocate for our right to
vote analog safely. Thank you."



[Name], [City/State]



Tell your friends about the threat of digital voting on social media!



Use the tags #NoDigitalVoting and #UserFreedom on your favorite
microblogging sites.



From voter registration to tallying, all steps in the voting
process could hypothetically be done digitally. But voting is a
highly personal, sensitive, and complicated system, one that
involves some of the most powerful stakeholders imaginable, and
where freedom is at stake. Free software shows us the system and
allows us to improve it. It does not, however, guarantee the
entire process to be unbreakable. Let's steer clear from digital
systems for now, for freedom.



Zoë Kooyman

Program Manager



Illustration Copyright © 2020, Free Software Foundation, Inc., by
Zoë Kooyman, Licensed under Creative Commons Attribution
4.0
International license.







--=_b4073b9b828682e213fa8e8110055bec--

--===============0361151139==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============0361151139==--

--===============0361151139==
Content-Type: multipart/alternative;
boundary="=_b4073b9b828682e213fa8e8110055bec"

--=_b4073b9b828682e213fa8e8110055bec
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read and share online: *


*Please consider adding to your address book, which will
ensure that our messages reach you and not your spam box.*


Dear Ruben Safir,

Here at the Free Software Foundation (FSF), we fight for the freedom
of all software users. We believe that everyone has the right to
[understand and study][1] the systems that they use, and that not
being able to exercise this right is a violation of our freedom. This
applies to our personal software usage, but becomes even more
important in processes of democracy. It is particularly relevant for
the upcoming November 2020 elections in the United States.

[1]: https://www.gnu.org/philosophy/free-sw.html

A free country has the responsibility to make sure all of its
citizens can be heard, and that voting processes are transparent
and fair. So what happens if people are still self-isolating in
November, in order to try and prevent a [second wave of the novel
coronavirus][2]? As more of our life processes have gone online
due to the pandemic, we have seen [debates][3] rise over a call
for mail-in voting. This discussion seems to be clearing a path
for a [renewed interest][4] in online voting software as a remote
alternative to in-person voting. This is cause for grave concern.

[2]: https://www.businessinsider.com/fauci-second-coronavirus-wave-is-not-inevitable-in-the-fall-2020-5
[3]: https://www.cnn.com/2020/04/21/politics/mail-in-voting-partisan-divide/index.html
[4]: https://www.politico.com/news/2020/06/08/online-voting-304013

I am arguing in this post that it is essential that software used in
any part of the voting process be published free software. It is
unacceptable for such an important democratic system to be placed in
the hands of any for-profit, proprietary software corporation that
controls the source code, data management, reporting, updates, and
testing. No good can come from requiring a court order to be permitted
to study the source code of voting software in order to confirm the
process is fair and democratic. But additionally, I might surprise the
reader by laying out arguments to say that despite supporting the wish
to increase access and ease for all eligible voters, the only truly
free, ethical, and democratic voting system is actually a system that
steers clear from using software.

Technology can assist in the non-fundamental parts of the voting
process, like speeding up simple on-site calculations or verification
processes, in which case transparency is absolutely vital, and the
systems used must therefore be free software. Source code should be
provided freely for anyone to test the application, submit
modifications that can be adopted to improve the software, and make
recommendations, long before it has any opportunity to muddle with
results. But digital systems have no place in the key parts of the
voting system, including voter registration, casting a vote, and
tallying results. The experts agree on this, and I will explain why in
more detail below. Even when the source code is available, although we
can compel transparency and reproducibility, we still [risk
unacceptable vulnerabilities][5].

[5]: https://www.technewsworld.com/story/Next-US-Elections-Open-Source-vs-Commercial-Software-84794.html

The examples below demonstrate some of the pitfalls of using
proprietary software in the voting process, and why the peddlers
of proprietary software cannot be trusted with crucial democratic
processes.

### Tallying and the Iowa caucus fiasco

In February 2020, during the kickoff of the primary elections to
determine the US presidential candidates, the [Iowa caucus][6]
introduced a [newly developed app][7] designed to help tally votes and
make the results faster and more accurate. It did the opposite.

[6]: https://people.howstuffworks.com/iowa-caucus.htm
[7]: https://www.nytimes.com/2020/02/03/us/politics/iowa-caucus-app.html

The Iowa caucus failed due to [shoddy design and lack of testing][8]
of the app built by [Shadow Inc.][9], a for-profit technology company
that provides "smarter" technological infrastructure for Democratic
party campaigns. The flaws didn't surface until the primaries, because
of its proprietary nature. While the caucus results trickled in over
the days following the primary, debates arose about the accuracy of
its outcome, and voters started [questioning][10] the role that
technology should play in our elections. This fallout successfully
prompted other states to act with caution, and mostly scrap the plans
to use the same app.

[8]: https://www.cnbc.com/2020/02/04/iowa-caucus-app-debacle-is-one-of-the-most-stunning-it-failures-ever.html
[9]: https://abcnews.go.com/Politics/shadow-vendor-iowa-dems-reporting-app/story?id=68754002
[10]: https://www.cityweekly.net/utah/voting-app-blues/Content?oid=14861769

### Online voting applications

Even before the virus broke out, jurisdictions like Delaware, Georgia,
and Philadelphia had already committed to replacing existing systems
with digital voting machines, despite their [unacceptable risks of
interference][11].

[11]: https://www.politico.com/story/2019/03/01/election-vulnerable-voting-machines-1198780

Voatz, Inc. the for-profit company behind the private mobile [voting
app][12] by the same name, developed a pilot program in 2019, claiming
they delivered "secure" digital voting. The trial for the proprietary
app focused on people with disabilities and people residing
overseas. Colorado, Oregon, Utah, Washington, and West Virginia signed
up, but studies found that the app posed [security risks][13] like
leaving votes visible and exposing them to tamperers. Researchers from
the Massachusetts Institute of Technology (MIT) [reviewed the app][14]
and found an alarming number of [vulnerabilities and privacy
issues][15].

[12]: https://www.nytimes.com/2020/02/13/us/politics/voting-smartphone-app.html
[13]: https://www.politico.com/news/2020/05/01/coronavirus-online-voting-229690
[14]: https://internetpolicy.mit.edu/wp-content/uploads/2020/02/SecurityAnalysisOfVoatz_Public.pdf
[15]: https://www.technologyreview.com/f/615195/hackers-can-change-votes-in-an-online-election-app/

Now, in recent primaries, [some states][16] have implemented online
voting using a system called OmniBallot, claiming that it offers safe
remote voting during the virus. Democracy Live, the organization
behind the system used in Delaware, West Virginia, and New Jersey
states that the system is not *really* online voting, because a printed
ballot is still generated when the voter's ballot is downloaded by the
voting committee. But that doesn't account for the fact that the votes
are still cast [electronically and transmitted online][17], which
means they are [still vulnerable to tampering][18]. In fact, OmniBallot
was also reviewed by MIT, and again, the [conclusion][19] was that the
system is unsafe. It proved vulnerable to manipulation, and
additionally has no privacy policy to deal with the voter's sensitive
information.

[16]: https://reason.com/2020/06/10/amid-coronavirus-fears-2-states-will-allow-online-voting/
[17]: https://www.politico.com/news/2020/05/01/coronavirus-online-voting-229690
[18]: https://arstechnica.com/tech-policy/2020/06/researchers-say-online-voting-tech-used-in-5-states-is-fatally-flawed/
[19]: https://internetpolicy.mit.edu/wp-content/uploads/2020/06/OmniBallot.pdf

### Vulnerabilities explained

As much as different states want to spend millions of taxpayer
dollars to implement online voting systems to some degree or
another, there simply is no safe way to do so. [*The Observer*
explains][20] that an online system has to take into account too
many factors, from verifying identification to creating a secret
ballot, to voting and getting that vote to the committee, and
then verifying it again on the other end. To make it all secure
is nearly impossible.

[20]: https://observer.com/2020/06/election-security-why-cant-people-vote-online/

Security experts have long been expressing concern as well. After the
2016 US presidential elections, the National Academy of Sciences (NAS)
conducted elaborate research into the future of voting, and published
a report called ["Securing the Vote: Protecting American
Democracy."][21] The preface of this 157-page document states: "We
were constantly reminded in news stories, by congressional hearings,
and through reports from the intelligence community, of the
extraordinary threat from foreign actors using cyber weapons and
social media to manipulate the electorate, and to target our elections
and cast doubt on the integrity of the elections process."

[21]: https://www.nap.edu/read/25120/chapter/1

The report mentions that in 2016, the United States presidential
election was targeted by a foreign government, and voter information
was captured. While the exact consequences of this invasion are still
largely unclear, the fear of surveillance by outside parties and the
meddling with results is obviously justified. The NAS concludes that
the current system is vulnerable to internal and external threats, and
recommends [verifiable paper ballots][22], audits, and clear
distinctions between different elements of the process.

[22]: https://www.bostonglobe.com/2020/02/24/opinion/order-prevent-another-voting-debacle-turn-paper-balloting/

### Paper ballots and analog processes for democracy

Having full transparency and control is the only way in which we can
verify the legitimacy of elections. Transparency is currently best
accomplished by individual paper balloting. We will get the closest to
fair results by working with an analog system.

If we need to do remote voting, [contrary to some claims][23], mail-in
voting is a reliable fallback. [A study by Stanford University][24]
concludes that: "(1) vote-by-mail does not appear to affect either
party’s share of turnout; (2) vote-by-mail does not appear to increase
either party’s vote share; and (3) vote-by-mail modestly increases
overall average turnout rates, in line with previous estimates. All
three conclusions support the conventional wisdom of election
administration experts, and contradict many popular claims in the
media."

[23]: https://www.bostonglobe.com/2020/07/10/nation/fact-check-president-trump-keeps-calling-mail-in-voting-fraudulent-election-officials-advocates-say-otherwise/
[24]: https://siepr.stanford.edu/research/publications/neutral-partisan-effects-vote-mail-evidence-county-level-roll-outs

***

## Here's what you can do to stand up for your voting rights

#### Contact your representative
If you are in the US, please contact your [local representative][25] to
let them know you oppose electronic voting, and in particular
proprietary electronic voting. You can copy or personalize our
sample text:

[25]: https://www.congress.gov/members

> "Dear [Representive],
> I am [Name], and I live in your district.
> I am very concerned about the security and integrity of our
> voting systems, and do not think any computer-based system is
> safe, especially not any proprietary system. I agree with the
> Free Software Foundation article about the dangers of digital
> proprietary voting at , and request the use
> of only paper ballots in upcoming elections. Please oppose any
> move to digital voting systems, and advocate for our right to
> vote analog safely. Thank you."

> [Name], [City/State]

#### Tell your friends about the threat of digital voting on social media!
Use the tags \#NoDigitalVoting and \#UserFreedom on your favorite
[microblogging][26] sites.

[26]: https://www.fsf.org/share

>From voter registration to tallying, all steps in the voting
process could hypothetically be done digitally. But voting is a
highly personal, sensitive, and complicated system, one that
involves some of the most powerful stakeholders imaginable, and
where freedom is at stake. Free software shows us the system and
allows us to improve it. It does not, however, guarantee the
entire process to be unbreakable. Let's steer clear from digital
systems for now, for freedom.


Zoë Kooyman
Program Manager

--
* Follow us on Mastodon at , GNU social at
, Diaspora at ,
and on Twitter at .
* Read about why we use Twitter, but only with caveats at .
* Subscribe to our RSS feeds at .
* Join us as an associate member at .
* Read our Privacy Policy at .

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=161433&qid=56308113&h=8fa5b06af7f69f82.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=161433&qid=56308113&h=8fa5b06af7f69f82.
--=_b4073b9b828682e213fa8e8110055bec
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







Read and share online: https://www.fsf.org/blogs/community/dont-let-proprietary-digital-voting-disrupt-democracy





Please consider adding info@fsf.org to your address book, which will
ensure that our messages reach you and not your spam box.





Dear Ruben Safir,




Democracy



Here at the Free Software Foundation (FSF), we fight for the freedom
of all software users. We believe that everyone has the right to
understand and study the systems that they use, and that not
being able to exercise this right is a violation of our freedom. This
applies to our personal software usage, but becomes even more
important in processes of democracy. It is particularly relevant for
the upcoming November 2020 elections in the United States.



A free country has the responsibility to make sure all of its
citizens can be heard, and that voting processes are transparent
and fair. So what happens if people are still self-isolating in
November, in order to try and prevent a second wave of the novel
coronavirus
? As more of our life processes have gone online
due to the pandemic, we have seen debates rise over a call
for mail-in voting. This discussion seems to be clearing a path
for a renewed interest in online voting software as a remote
alternative to in-person voting. This is cause for grave concern.



I am arguing in this post that it is essential that software used in
any part of the voting process be published free software. It is
unacceptable for such an important democratic system to be placed in
the hands of any for-profit, proprietary software corporation that
controls the source code, data management, reporting, updates, and
testing. No good can come from requiring a court order to be permitted
to study the source code of voting software in order to confirm the
process is fair and democratic. But additionally, I might surprise the
reader by laying out arguments to say that despite supporting the wish
to increase access and ease for all eligible voters, the only truly
free, ethical, and democratic voting system is actually a system that
steers clear from using software.



Technology can assist in the non-fundamental parts of the voting
process, like speeding up simple on-site calculations or verification
processes, in which case transparency is absolutely vital, and the
systems used must therefore be free software. Source code should be
provided freely for anyone to test the application, submit
modifications that can be adopted to improve the software, and make
recommendations, long before it has any opportunity to muddle with
results. But digital systems have no place in the key parts of the
voting system, including voter registration, casting a vote, and
tallying results. The experts agree on this, and I will explain why in
more detail below. Even when the source code is available, although we
can compel transparency and reproducibility, we still risk
unacceptable vulnerabilities
.



The examples below demonstrate some of the pitfalls of using
proprietary software in the voting process, and why the peddlers
of proprietary software cannot be trusted with crucial democratic
processes.



Tallying and the Iowa caucus fiasco



In February 2020, during the kickoff of the primary elections to
determine the US presidential candidates, the Iowa caucus
introduced a newly developed app designed to help tally votes and
make the results faster and more accurate. It did the opposite.



The Iowa caucus failed due to shoddy design and lack of testing
of the app built by Shadow Inc., a for-profit technology company
that provides "smarter" technological infrastructure for Democratic
party campaigns. The flaws didn't surface until the primaries, because
of its proprietary nature. While the caucus results trickled in over
the days following the primary, debates arose about the accuracy of
its outcome, and voters started questioning the role that
technology should play in our elections. This fallout successfully
prompted other states to act with caution, and mostly scrap the plans
to use the same app.



Online voting applications



Even before the virus broke out, jurisdictions like Delaware, Georgia,
and Philadelphia had already committed to replacing existing systems
with digital voting machines, despite their unacceptable risks of
interference
.



Voatz, Inc. the for-profit company behind the private mobile voting
app
by the same name, developed a pilot program in 2019, claiming
they delivered "secure" digital voting. The trial for the proprietary
app focused on people with disabilities and people residing
overseas. Colorado, Oregon, Utah, Washington, and West Virginia signed
up, but studies found that the app posed security risks like
leaving votes visible and exposing them to tamperers. Researchers from
the Massachusetts Institute of Technology (MIT) reviewed the app
and found an alarming number of vulnerabilities and privacy
issues
.



Now, in recent primaries, some states have implemented online
voting using a system called OmniBallot, claiming that it offers safe
remote voting during the virus. Democracy Live, the organization
behind the system used in Delaware, West Virginia, and New Jersey
states that the system is not really online voting, because a printed
ballot is still generated when the voter's ballot is downloaded by the
voting committee. But that doesn't account for the fact that the votes
are still cast electronically and transmitted online, which
means they are still vulnerable to tampering. In fact, OmniBallot
was also reviewed by MIT, and again, the conclusion was that the
system is unsafe. It proved vulnerable to manipulation, and
additionally has no privacy policy to deal with the voter's sensitive
information.



Vulnerabilities explained



As much as different states want to spend millions of taxpayer
dollars to implement online voting systems to some degree or
another, there simply is no safe way to do so. The Observer
explains
that an online system has to take into account too
many factors, from verifying identification to creating a secret
ballot, to voting and getting that vote to the committee, and
then verifying it again on the other end. To make it all secure
is nearly impossible.



Security experts have long been expressing concern as well. After the
2016 US presidential elections, the National Academy of Sciences (NAS)
conducted elaborate research into the future of voting, and published
a report called "Securing the Vote: Protecting American
Democracy."
The preface of this 157-page document states: "We
were constantly reminded in news stories, by congressional hearings,
and through reports from the intelligence community, of the
extraordinary threat from foreign actors using cyber weapons and
social media to manipulate the electorate, and to target our elections
and cast doubt on the integrity of the elections process."



The report mentions that in 2016, the United States presidential
election was targeted by a foreign government, and voter information
was captured. While the exact consequences of this invasion are still
largely unclear, the fear of surveillance by outside parties and the
meddling with results is obviously justified. The NAS concludes that
the current system is vulnerable to internal and external threats, and
recommends verifiable paper ballots, audits, and clear
distinctions between different elements of the process.



Paper ballots and analog processes for democracy



Having full transparency and control is the only way in which we can
verify the legitimacy of elections. Transparency is currently best
accomplished by individual paper balloting. We will get the closest to
fair results by working with an analog system.



If we need to do remote voting, contrary to some claims, mail-in
voting is a reliable fallback. A study by Stanford University
concludes that: "(1) vote-by-mail does not appear to affect either
party’s share of turnout; (2) vote-by-mail does not appear to increase
either party’s vote share; and (3) vote-by-mail modestly increases
overall average turnout rates, in line with previous estimates. All
three conclusions support the conventional wisdom of election
administration experts, and contradict many popular claims in the
media."






Here's what you can do to stand up for your voting rights



Contact your representative



If you are in the US, please contact your local representative to
let them know you oppose electronic voting, and in particular
proprietary electronic voting. You can copy or personalize our
sample text:



"Dear [Representive],
I am [Name], and I live in your district.
I am very concerned about the security and integrity of our
voting systems, and do not think any computer-based system is
safe, especially not any proprietary system. I agree with the
Free Software Foundation article about the dangers of digital
proprietary voting at https://u.fsf.org/voting, and request the use
of only paper ballots in upcoming elections. Please oppose any
move to digital voting systems, and advocate for our right to
vote analog safely. Thank you."



[Name], [City/State]



Tell your friends about the threat of digital voting on social media!



Use the tags #NoDigitalVoting and #UserFreedom on your favorite
microblogging sites.



From voter registration to tallying, all steps in the voting
process could hypothetically be done digitally. But voting is a
highly personal, sensitive, and complicated system, one that
involves some of the most powerful stakeholders imaginable, and
where freedom is at stake. Free software shows us the system and
allows us to improve it. It does not, however, guarantee the
entire process to be unbreakable. Let's steer clear from digital
systems for now, for freedom.



Zoë Kooyman

Program Manager



Illustration Copyright © 2020, Free Software Foundation, Inc., by
Zoë Kooyman, Licensed under Creative Commons Attribution
4.0
International license.







--=_b4073b9b828682e213fa8e8110055bec--

--===============0361151139==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============0361151139==--

  1. 2020-07-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Childhood Culture
  2. 2020-07-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Lot s of Protesting and no evidence of COVID
  3. 2020-07-02 From: "American Museum of Natural History" <learn-at-amnh.org> Subject: [Hangout - NYLXS] There Are Only a Few Days Left to Register for
  4. 2020-07-02 From: "Canarsie Courier" <emailsentby-at-icontactmail.com> Subject: [Hangout - NYLXS] Inside This Week's Edition of the Canarsie Courier
  5. 2020-07-02 Rabbinical Seminary of America <info-at-rsa30k.com> Subject: [Hangout - NYLXS] Tonight is the Deadline to win $30,000!
  6. 2020-07-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] nothing to worry about... just keep using the
  7. 2020-07-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Real News Slips Past Us
  8. 2020-07-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] A ray of hope about the Police
  9. 2020-07-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Bars and resturants not reopening... maybe ever..
  10. 2020-07-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] ICU treatment for COVID-19 is still under debate
  11. 2020-07-03 Yusif Suleiman <yusifsuleiman-at-hotmail.com> Subject: [Hangout - NYLXS] [Health] GNU Health test-run in production
  12. 2020-07-04 Edgar Hagenbichler <edgar.hagenbichler-at-hagenbichler.at> Re: [Hangout - NYLXS] [Health] GNU Health test-run in production
  13. 2020-07-06 Yusif Suleiman <yusifsuleiman-at-hotmail.com> Re: [Hangout - NYLXS] [Health] GNU Health test-run in production
  14. 2020-07-06 Javier via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] [s6] system not
  15. 2020-07-06 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Putting the pressure on China
  16. 2020-07-06 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] access to network drive - denies to root?
  17. 2020-07-06 Chris Cromer via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] access to network drive -
  18. 2020-07-07 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [artix-general] access to network drive -
  19. 2020-07-05 Kian Kasad via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] how to create distcc-runit package
  20. 2020-07-07 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [artix-general] access to network drive -
  21. 2020-07-07 Chris Cromer via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] access to network drive -
  22. 2020-07-07 NYOUG <execdir-at-nyoug.org> Subject: [Hangout - NYLXS] Upcoming Events for Oracle Professionals
  23. 2020-07-07 Dudemanguy via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] [s6] system not
  24. 2020-07-07 Dudemanguy via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] how to create distcc-runit
  25. 2020-07-08 From: "[RSS/Feed] nixCraft: Linux Tips, Hacks, Tutorials, Subject: [Hangout - NYLXS] nixCraft Linux / UNIX Newsletter
  26. 2020-07-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] making up news on a slow newws day
  27. 2020-07-08 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Time Off
  28. 2020-07-08 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] No Conflict of Interest there...
  29. 2020-07-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Police Unions - this is off topic
  30. 2020-07-08 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] State Budget Collapse
  31. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Graphitti is BACK.
  32. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Graphitti is BACK.
  33. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Biden switching sides..
  34. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] QUnatifying the impact of COVID-19 coming into
  35. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] Israel's second wave
  36. 2020-07-09 Helene Weinstein <weinsteinh-at-nyassembly.gov> Re: [Hangout - NYLXS] Graphitti is BACK.
  37. 2020-07-09 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] Israel's second wave
  38. 2020-07-09 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] [ Docs ] Israel's second wave
  39. 2020-07-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] huge scup caught tonight
  40. 2020-07-09 Edgar Hagenbichler <edgar.hagenbichler-at-hagenbichler.at> Subject: [Hangout - NYLXS] [Health] Free Webinar "GNU Health for beginners"
  41. 2020-07-09 From: "American Museum of Natural History" <GilderCenter-at-amnh.org> Subject: [Hangout - NYLXS] Gilder Center Project Update
  42. 2020-07-09 Rabbinical Seminary of America <info-at-rsa30k.com> Subject: [Hangout - NYLXS] THE WINNER OF THE $30,000 SWEEPSTAKES IS...
  43. 2020-07-10 From: "American Museum of Natural History" <email-at-amnh.org> Subject: [Hangout - NYLXS] Today! Manhattanhenge is Back!
  44. 2020-07-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Porgy from Water to Oven
  45. 2020-07-11 ronald munjoma <simbiso-at-gmail.com> Re: [Hangout - NYLXS] [Health] Free Webinar "GNU Health for
  46. 2020-07-11 From: "Pharmacy Times Continuing Education - PTCE" <ptce-at-pharmacytimes.org> Subject: [Hangout - NYLXS] COVID-19 Live Free CE Webinar!
  47. 2020-07-12 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Bulding a community
  48. 2020-07-13 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #468 - Is Cor the solution?
  49. 2020-07-13 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [ Docs ] Israel's second wave
  50. 2020-07-13 George Moskowitz MD <yehudazev-at-gmail.com> Subject: [Hangout - NYLXS] Fwd: Rabbi Dr. Sacks and my humble thoughts
  51. 2020-07-13 NCPA eCommunications <ncpa.ecommunications-at-ncpanet.org> Subject: [Hangout - NYLXS] =?utf-8?q?NCPA_urges_Florida_not_to_extend_PBM?=
  52. 2020-07-12 Kian Kasad via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] how to create distcc-runit
  53. 2020-07-11 Chris Cromer via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] Software proposal for the cli
  54. 2020-07-09 Javier via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] [artix-linux][lsb-release]
  55. 2020-07-10 Paolo Giacomel via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] Software proposal for the cli
  56. 2020-07-13 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Fwd: CNN 7/3/20: Twitter and JPMorgan are
  57. 2020-07-13 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] Fwd: CNN 7/3/20: Twitter and JPMorgan are
  58. 2020-07-13 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Fwd: CNN 7/3/20: Twitter and JPMorgan are
  59. 2020-07-13 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Undermining our Government and Economy
  60. 2020-07-13 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] Undermining our Government and
  61. 2020-07-13 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] Undermining our Government and
  62. 2020-07-13 Miss Belmar Princess <missbelmar-at-aol.com> Subject: [Hangout - NYLXS] WEEKEND WRAP UP WITH BLUES, SEA BASS & LING!
  63. 2020-07-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] fix the dictionary
  64. 2020-07-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] COVID-19 and food shortages
  65. 2020-07-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] COVID-19 and food shortages II
  66. 2020-07-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] COVID-19 and food shortagees III
  67. 2020-07-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] COVID-19 and food shortagees IV
  68. 2020-07-14 soledad.esteban <soledad.esteban-at-icp.cat> Subject: [Hangout - NYLXS] [dinosaur] Live Online course: 3D GEOMETRIC
  69. 2020-07-14 soledad.esteban <soledad.esteban-at-icp.cat> Subject: [Hangout - NYLXS] [dinosaur] Live Online course: 3D GEOMETRIC
  70. 2020-07-14 Dudemanguy via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] [s6] system not
  71. 2020-07-14 Javier via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] [s6] system not
  72. 2020-07-13 Dudemanguy via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] [s6] system not
  73. 2020-07-14 From: "John Sullivan, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Your support drives our fight for #UserFreedom
  74. 2020-07-15 IEEE Engineering in Medicine and Biology Society <noreply-at-embs.org> Subject: [Hangout - NYLXS] Changes to the EMB Constitution/Bylaws - Deadline
  75. 2020-07-15 From: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?= <info-at-fsf.org> Subject: [Hangout - NYLXS] Don't let proprietary digital voting disrupt
  76. 2020-07-16 From: "[RSS/Feed] nixCraft: Linux Tips, Hacks, Tutorials, Subject: [Hangout - NYLXS] nixCraft Linux / UNIX Newsletter
  77. 2020-07-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: Re: mv w/mkdir -p of destination
  78. 2020-07-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] paging Fernando
  79. 2020-07-17 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] taunting the cops on broadway
  80. 2020-07-19 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  81. 2020-07-18 friedmanhvj-at-aol.com Subject: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  82. 2020-07-19 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  83. 2020-07-19 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  84. 2020-07-18 Thomas Richard Holtz <tholtz-at-umd.edu> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  85. 2020-07-18 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  86. 2020-07-18 aviva <aviva-at-gmx.us> Subject: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  87. 2020-07-18 aviva <aviva-at-gmx.us> Subject: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  88. 2020-07-20 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #469 - United Perl Mongers
  89. 2020-07-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] time to fire this guy
  90. 2020-07-20 From: "American Museum of Natural History" <email-at-amnh.org> Subject: [Hangout - NYLXS] Online resources to explore with your students
  91. 2020-07-20 ronald munjoma <simbiso-at-gmail.com> Re: [Hangout - NYLXS] [Health] webinar GNUHealth for beginners on
  92. 2020-07-20 Thomas Richard Holtz <tholtz-at-umd.edu> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  93. 2020-07-20 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  94. 2020-07-20 aviva <aviva-at-gmx.us> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  95. 2020-07-20 Anthony <keenir-at-hotmail.com> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  96. 2020-07-20 Mike Habib <biologyinmotion-at-gmail.com> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  97. 2020-07-20 Liz M <egmartin19-at-gmail.com> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  98. 2020-07-20 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [dinosaur] Prehistoric Road Trip, Tiny Teeth,
  99. 2020-07-20 From: "PSSNY" <staff-at-pssny.org> Subject: [Hangout - NYLXS] =?utf-8?q?Urge_Legislature_to_Pass_the_PBM_bil?=
  100. 2020-07-20 Yusif Suleiman <yusifsuleiman-at-hotmail.com> Re: [Hangout - NYLXS] [Health] webinar GNUHealth for beginners on
  101. 2020-07-21 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Pork PreCovid analysis - maybe
  102. 2020-07-21 aviva <aviva-at-gmx.us> Subject: [Hangout - NYLXS] anyone ever deal with the Dinosaur mailing list?
  103. 2020-07-22 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [ Docs ] anyone ever deal with the Dinosaur
  104. 2020-07-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] strange cd behaviorn
  105. 2020-07-22 Luis Falcon <falcon-at-gnuhealth.org> Re: [Hangout - NYLXS] [Health] webinar GNUHealth for beginners on
  106. 2020-07-22 Edgar Hagenbichler <edgar.hagenbichler-at-hagenbichler.at> Subject: [Hangout - NYLXS] [Health] webinar GNUHealth for beginners on Mon 3
  107. 2020-07-23 From: "American Museum of Natural History" <learn-at-amnh.org> Subject: [Hangout - NYLXS] Registration Is Now Open for Our First Fall
  108. 2020-07-23 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] A Message from President Kimberly R. Cline
  109. 2020-07-23 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Informational Message: Certified Pharmacist
  110. 2020-07-27 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #470 - Perl Mentoring
  111. 2020-07-26 The Hebron Fund <info-at-hebronfund.org> Subject: [Hangout - NYLXS] Hero Soldier, Life After Corona VIDEO,
  112. 2020-07-27 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #470 - Perl Mentoring
  113. 2020-07-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Belmar vacation - One Sunday
  114. 2020-07-27 Steffen Land <info-at-apachelounge.com.INVALID> Re: [Hangout - NYLXS] [users-at-httpd] Announcing mod_websocket v0.1.2
  115. 2020-07-28 From: "Dana Morgenstein, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Presenting the expanded Free Software Foundation
  116. 2020-07-28 jerome moliere via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] Newcomer - a couple of questions
  117. 2020-07-28 Christos Nouskas via artix-general <artix-general-at-artixlinux.org> Re: [Hangout - NYLXS] [artix-general] Newcomer - a couple of
  118. 2020-07-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Virus cases in Israel - Do we trust the experts..
  119. 2020-07-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Tish B'av
  120. 2020-07-30 From: "American Museum of Natural History" <learn-at-amnh.org> Subject: [Hangout - NYLXS] Learn More About Our Online Courses for Teachers
  121. 2020-07-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Herman cain died of WUHAN-19
  122. 2020-07-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] fre the mind
  123. 2020-07-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Bounces City and State checks...
  124. 2020-07-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] No end to the medical ethics problems we now
  125. 2020-07-30 Mark Galassi <mark-at-galassi.org> Subject: [Hangout - NYLXS] looking for collaborators for free s/w-based
  126. 2020-07-30 From: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?= <info-at-fsf.org> Subject: [Hangout - NYLXS] Free software in business: Success stories
  127. 2020-07-31 zap via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] I had a suggestion or two,
  128. 2020-07-31 zap via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] I had a suggestion or two,
  129. 2020-07-31 zap via artix-general <artix-general-at-artixlinux.org> Subject: [Hangout - NYLXS] [artix-general] I had a suggestion or two,
  130. 2020-07-13 mayer ilovitz <pmamayeri-at-gmail.com> Re: [Hangout - NYLXS] Fwd: CNN 7/3/20: Twitter and JPMorgan are
  131. 2020-07-13 mayer ilovitz <pmamayeri-at-gmail.com> Subject: [Hangout - NYLXS] Fwd: CNN 7/3/20: Twitter and JPMorgan are

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!