Thu Nov 21 23:15:33 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 2022-12-01

HANGOUT

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

Key: Value:

Key: Value:

MESSAGE
DATE 2022-12-23
FROM From: "Miriam Bastian"
SUBJECT Subject: [Hangout - NYLXS] Sharing is at the core of the free software
From hangout-bounces-at-nylxs.com Wed Dec 28 16:13:35 2022
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 9279F164066;
Wed, 28 Dec 2022 16:13:31 -0500 (EST)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id D4846164063; Wed, 28 Dec 2022 16:13:25 -0500 (EST)
Resent-From: Ruben Safir
Resent-Date: Wed, 28 Dec 2022 16:13:25 -0500
Resent-Message-ID: <20221228211325.GA1514-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])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mrbrklyn.com (Postfix) with ESMTPS id DFF2616406F
for ; Fri, 23 Dec 2022 18:59:45 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org;
s=mailout0p-fsf-org; h=Date:To:Subject:From:MIME-Version:in-reply-to:
references; bh=pSoczDJu86Q4dhCGvXea/VVee/j4yDuyFkN3wfP5Rgg=; b=XbjqNeMBeeyEvv
G6uoee0Ddp51im3BEOaZ1R/BuZX1bFoU883KLmcbgndPgNu+hEuShWHVjZcMB2I05M4oaTIpkAR5W
stxwmNcmzrU2+QHb6XRY82h3lDgt/Y6T84g9a2l+7g0hdtNZyv46fRuqMWP9wutS2tpEc5O1v9i6/
zHs58XV1ZKVaoUkKrpOpxyJRSO3mNGAo+DzOJSmddyKIOQhBVX6ChvjV7YgqA4OXaubsajRTHLN1w
xskLHLVi5gQDdgGHh+rPB8pO4EYY+YIZw114wbyJ91JX2vOzqaIhVSxBCgQFl+gIEqc96Qn/xOOtX
ebe1gfnuoMydVSt6jdhA==;
Received: from crmserver2p.fsf.org ([2001:470:142:5::223])
by mailout0p.fsf.org with esmtps (TLS1.2) tls
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93)
(envelope-from )
id 1p8rx2-006oVP-PN
for ruben-at-mrbrklyn.com; Fri, 23 Dec 2022 18:59:44 -0500
Received: from localhost ([::1] helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.90_1)
(envelope-from )
id 1p8rx2-0001dl-Iw
for ruben-at-mrbrklyn.com; Fri, 23 Dec 2022 18:59:44 -0500
MIME-Version: 1.0
From: "Miriam Bastian"
job_id: 166412
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.166412.79959427.fa7886765afe8d39-at-fsf.org
Date: Fri, 23 Dec 2022 18:59:44 -0500
Message-Id:
Subject: [Hangout - NYLXS] Sharing is at the core of the free software
community
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: Miriam Bastian
Content-Type: multipart/mixed; boundary="===============0057406314=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============0057406314==
Content-Type: multipart/alternative;
boundary="=_cc9ff27cc3d70e7c7027f0d649c92254"

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

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

*Read and share online: *


Dear Ruben Safir,

Sharing is what makes a strong community. It has always impressed me to see how
people in the free software community share their time, ideas, achievements,
knowledge, and software with others. This sharing community is what attracted
me in the first place to the free software movement: I wanted to know what it
is that people spend so much time and joint effort on and why. What I found
convinced me and won me over to free software.

I started to climb the [freedom ladder][1] in 2014. Having profited
from software like [KeePassXC][2], [Calibre][3], [LibreOffice][4],
[F-Droid][5], [Zotero][6], [VLC media player][7], [Privacy Badger][8],
and [TeXstudio][9] for more than seven years, I wanted to give back to
the free software community. When the Free Software Foundation (FSF)
was looking for a program manager, I considered this to be the perfect
opportunity to utilize my organizational, managerial, and
interpersonal skills, and I am immensely grateful that I now have
the privilege to contribute to the free software movement as the FSF's
program manager.

[1]: https://www.fsf.org/campaigns/campaigns-summaries#ladder
[2]: https://directory.fsf.org/wiki/KeePassXC
[3]: https://directory.fsf.org/wiki/Calibre
[4]: https://directory.fsf.org/wiki/LibreOffice
[5]: https://directory.fsf.org/wiki/F-Droid
[6]: https://directory.fsf.org/wiki/Zotero_client
[7]: https://directory.fsf.org/wiki/VLC_media_player
[8]: https://directory.fsf.org/wiki/Privacy_Badger
[9]: https://directory.fsf.org/wiki/TeXstudio

My path to the FSF took me through academia. During my doctorate, I spent four
years writing articles and contributing to collaborative volumes which I was
not allowed to share after the publication because the authors, who do the
research and write the text, usually have to assign the distribution rights to
the publishers and for decades [most of the academic publishers have distributed
books in DRM-restricted, proprietary, and incompatible formats][10]. This is
why policies such as the memorandum to ensure ["Free, Immediate, and Equitable
Access to Federally Funded Research"][11] published this year in August by the
White House Office of Science and Technology Policy (OSTP) or projects like
["Developing Institutional Open Access Publishing Models to Advance Scholarly
Communication" (DIAMAS)][12] which in September launched a project to develop
a diamond open access publishing model are long-overdue steps in the right
direction. These initiatives work to ensure that scientific data resulting from
federally funded research and peer reviewed scholarly publications are made
freely available and publicly accessible by default. Academia, as with so many
other fields, cannot exist without collaboration. But how can we collaborate if
we lack the freedom to share the code, the data, the documents, the articles,
and the (e-)books we are working with?

[10]: https://www.theguardian.com/higher-education-network/blog/2013/feb/26/digital-rights-managment-pdf-books
[11]: https://www.whitehouse.gov/wp-content/uploads/2022/08/08-2022-OSTP-Public-Access-Memo.pdf
[12]: https://diamasproject.eu/

Let me give one example from my experience in academia to illustrate this. At
the Department of Ancient History at the University of Zurich, I prepared
inscriptions from the Roman Empire for the Epigraphic Database Clauss / Slaby
(EDCS). Epigraphy is the study of inscriptions and there are hundreds of
epigraphists worldwide, all working to understand and analyze inscriptions from
the Roman Empire who therefore must be able to access images and texts of the
inscriptions. The easiest way to do this is to use an epigraphic database. But
there is not only one epigraphic database, there are plenty of them. In addition
to the EDCS, there are for example the [Epigraphic Database Roma (EDR)][13], the
[Epigraphic Database Heidelberg (EDH)][14], the database [Hispania Epigraphica][15],
and the database of the [Europeana network of Ancient Greek and Latin Epigraphy
(EAGLE)][16]. Most of them contain similar information about the same inscriptions.
So, why duplicate information instead of having one database or linking from one
to the other? Most of the datasets are not shareable, at least not in a compatible
format. It is very difficult to share the database and the software it's running on,
and this makes it close to impossible for different universities to work together
on the same database.

[13]: http://www.edr-edr.it/default/index.php
[14]: https://edh.ub.uni-heidelberg.de/
[15]: http://eda-bea.es/
[16]: https://www.eagle-network.eu/

Whether in the form of databases, books, or articles, the availability
and accessibility of findings is crucial to ensure high quality in
research. Rationales and results of any scientific research can only
be verified by others if scientists share the data they collect and
the code and configurations they used to collect it with others in a format
that everybody can open and process. Other scientists can only
reproduce measurements and thus build upon them if they are shared with
them in freedom.

But against all reason, universities and other research institutions
worldwide use proprietary software like [Matlab][17], the [Microsoft Office
suite][18], or [ArcGIS software][19], to name only a few. These companies
trap documents and data in their software, so that [users can't share them
with people][20] [who don't use the same software][21]. The same companies
claim that their products are made for collaboration. But they are designed
to do the opposite: to exclude people who don't use the product of the same
company. Imagine that people modify and improve a piece of software, adapt
it to their needs, but then, they are not allowed to share the improvements.
To give you an example: my favorite typesetting system, LaTeX, started as a
markup language for science. I could only use it for my PhD thesis in history
because some amazing people [adapted it for the use in the humanities][22]
and then shared their improvements in the form of TeX extensions as
[XeLaTeX][23] and [LuaLaTeX][24], and packages such as [betababel][25] which
for a long time has been the only way to write polytonic Ancient Greek.

[17]: https://www.mathworks.com/academia.html
[18]: https://www.mathworks.com/help/matlab/matlab_prog/share-live-scripts.html
[19]: https://spatial.usc.edu/software/proprietary-software-students/
[20]: https://www.zi.uzh.ch/en/students/software-elearning/microsoft.html
[21]: https://en.wikipedia.org/wiki/Arcgis
[22]: https://journals.openedition.org/lectures/9324
[23]: https://www.overleaf.com/blog/636-guest-blog-post-latex-for-the-humanities
[24]: https://www.ctan.org/pkg/lualatex-doc
[25]: https://www.ctan.org/pkg/betababel

No wonder that science is facing a [reproducibility crisis][26] after,
for decades, having produced books and used software which deny the
reader or user to share it. [DRM][27]-free books and free software are
important steps on the way out of this crisis, because we can only
build upon and advance the work of others if we have the freedom to
share it. The good news is that there is fantastic free software, free
documentation, free programming languages, and free tools that are made
for science and for sharing. Scientist who care about sharing often use
programs like [GNU Guix][28], or [Git][29], [which have reproducibility
and shareability at their core][30]. Code that has been written in [Python][31]
can be shared easily without forcing the receiver to use a proprietary
computing environment like Matlab. In general, every fully free program
grants its user the freedom to not only run and modify the software, but
also to copy and share it. To find software that is granting you these
freedoms, check out the 16796 records in the [Free Software Directory][32].

[26]: https://www.nature.com/articles/533452a
[27]: https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management
[28]: https://directory.fsf.org/wiki/Guix
[29]: https://directory.fsf.org/wiki/Git
[30]: https://www.nature.com/articles/s41597-022-01720-9.pdf
[31]: https://directory.fsf.org/wiki/Python
[32]: https://directory.fsf.org/wiki/Main_Page

It is a shame that mega-corporations are trying to limit a user's freedom
to share; that they not only [prevent interoperability between social media
platforms][40] and [messengers][41] to maintain their monopolies, but also
impose [DRM][27] on books and other media. It is often misunderstood that
sharing has to be noncommercial. Most people are absolutely willing to pay
for a copy of a free (as in freedom) program that has been developed
professionally, or a [DRM-free song, movie or e-book][42] that is shared
with them. Professional development as well as the creation of art requires
much time, sometimes many people, and numerous resources. Paying money
ensures the continuity of it. Many companies and a whole bunch of software
would not exist without the freedom to share. Even proprietary companies
build on free software and profit immensely from it. What I value in the
free software community, however, is the sharing for the sake of sharing;
for values like collaboration, community, solidarity, and participation.

[40]: https://www.eff.org/interoperablefacebook/
[41]: https://www.theverge.com/2022/3/24/22995431/european-union-digital-markets-act-imessage-whatsapp-interoperable
[27]: https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management
[42]: https://www.defectivebydesign.org/guide

In our [year-end fundraiser][44] and during this year's [International
Day Against DRM (IDAD)][45], we've been stressing the importance of
sharing. So much of what we do depends on sharing, studying, and
building upon the works of others. We can only truly foster free
software, free documentation, and free cultural works for users around
the world if we have the ability to share. This is why the freedom to
share is at the core of the FSF's work.

[44]: https://www.fsf.org/appeal
[45]: https://www.defectivebydesign.org/dayagainstdrm

**Can you join the effort to defend the freedom to share as an
[FSF associate member][49]?** You can start for as little as $10 per
month ($5 for students), or $120 per year. With your support, we can
continue to show people how the freedom to share can affect change in
all areas where software touches modern life. Besides that, your
membership gives strength to the *idea* of free software. Plus, your
membership will count towards achieving our fall goal of 455 new
associate members before December 31, and you will be eligible for
this year's snazzy and secure webcam cover when you join as an annual
associate member at $120 or more. You'll also be able to enjoy all the
[member benefits][48], which include merchandise discounts, a 16GB
bootable membership card, and use of our associate member
videoconferencing server.

[49]: https://my.fsf.org/join?mtm_campaign=fall22&mtm_source=campaigns
[48]: https://www.fsf.org/associate/benefits

As the FSF's program manager, I want to stand up for the freedom to share, and
look forward to working with you to do that. Please help spread the
message on [social media networks][50] using the hashtag #FreedomToShare.

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

Yours in freedom,

Miriam Bastian
Program Manager

--
* Follow us on Mastodon at , GNU social at
, PeerTube at , and on Twitter at -at-fsf.
* 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=166412&qid=79959427&h=fa7886765afe8d39.

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=166412&qid=79959427&h=fa7886765afe8d39.
--=_cc9ff27cc3d70e7c7027f0d649c92254
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







 

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



Read and share online: https://www.fsf.org/blogs/community/sharing-is-at-the-core-of-the-free-software-community





Dear Ruben Safir,



Sharing is what makes a strong community. It has always impressed me to see how
people in the free software community share their time, ideas, achievements,
knowledge, and software with others. This sharing community is what attracted
me in the first place to the free software movement: I wanted to know what it
is that people spend so much time and joint effort on and why. What I found
convinced me and won me over to free software.



I started to climb the freedom ladder in 2014. Having profited
from software like KeePassXC, Calibre, LibreOffice,
F-Droid, Zotero, VLC media player, Privacy Badger,
and TeXstudio for more than seven years, I wanted to give back to
the free software community. When the Free Software Foundation (FSF)
was looking for a program manager, I considered this to be the perfect
opportunity to utilize my organizational, managerial, and
interpersonal skills, and I am immensely grateful that I now have
the privilege to contribute to the free software movement as the FSF's
program manager.






Two minds facing each other and sharing concepts as the freedom to run,<BR>modify, study, and share software.




My path to the FSF took me through academia. During my doctorate, I spent four
years writing articles and contributing to collaborative volumes which I was
not allowed to share after the publication because the authors, who do the
research and write the text, usually have to assign the distribution rights to
the publishers and for decades most of the academic publishers have distributed
books in DRM-restricted, proprietary, and incompatible formats
. This is
why policies such as the memorandum to ensure "Free, Immediate, and Equitable
Access to Federally Funded Research"
published this year in August by the
White House Office of Science and Technology Policy (OSTP) or projects like
"Developing Institutional Open Access Publishing Models to Advance Scholarly
Communication" (DIAMAS)
which in September launched a project to develop
a diamond open access publishing model are long-overdue steps in the right
direction. These initiatives work to ensure that scientific data resulting from
federally funded research and peer reviewed scholarly publications are made
freely available and publicly accessible by default. Academia, as with so many
other fields, cannot exist without collaboration. But how can we collaborate if
we lack the freedom to share the code, the data, the documents, the articles,
and the (e-)books we are working with?



Let me give one example from my experience in academia to illustrate this. At
the Department of Ancient History at the University of Zurich, I prepared
inscriptions from the Roman Empire for the Epigraphic Database Clauss / Slaby
(EDCS). Epigraphy is the study of inscriptions and there are hundreds of
epigraphists worldwide, all working to understand and analyze inscriptions from
the Roman Empire who therefore must be able to access images and texts of the
inscriptions. The easiest way to do this is to use an epigraphic database. But
there is not only one epigraphic database, there are plenty of them. In addition
to the EDCS, there are for example the Epigraphic Database Roma (EDR), the
Epigraphic Database Heidelberg (EDH), the database Hispania Epigraphica,
and the database of the Europeana network of Ancient Greek and Latin Epigraphy
(EAGLE)
. Most of them contain similar information about the same inscriptions.
So, why duplicate information instead of having one database or linking from one
to the other? Most of the datasets are not shareable, at least not in a compatible
format. It is very difficult to share the database and the software it's running on,
and this makes it close to impossible for different universities to work together
on the same database.



Whether in the form of databases, books, or articles, the availability
and accessibility of findings is crucial to ensure high quality in
research. Rationales and results of any scientific research can only
be verified by others if scientists share the data they collect and
the code and configurations they used to collect it with others in a format
that everybody can open and process. Other scientists can only
reproduce measurements and thus build upon them if they are shared with
them in freedom.



But against all reason, universities and other research institutions
worldwide use proprietary software like Matlab, the Microsoft Office
suite
, or ArcGIS software, to name only a few. These companies
trap documents and data in their software, so that users can't share them
with people
who don't use the same software. The same companies
claim that their products are made for collaboration. But they are designed
to do the opposite: to exclude people who don't use the product of the same
company. Imagine that people modify and improve a piece of software, adapt
it to their needs, but then, they are not allowed to share the improvements.
To give you an example: my favorite typesetting system, LaTeX, started as a
markup language for science. I could only use it for my PhD thesis in history
because some amazing people adapted it for the use in the humanities
and then shared their improvements in the form of TeX extensions as
XeLaTeX and LuaLaTeX, and packages such as betababel which
for a long time has been the only way to write polytonic Ancient Greek.



No wonder that science is facing a reproducibility crisis after,
for decades, having produced books and used software which deny the
reader or user to share it. DRM-free books and free software are
important steps on the way out of this crisis, because we can only
build upon and advance the work of others if we have the freedom to
share it. The good news is that there is fantastic free software, free
documentation, free programming languages, and free tools that are made
for science and for sharing. Scientist who care about sharing often use
programs like GNU Guix, or Git, which have reproducibility
and shareability at their core
. Code that has been written in Python
can be shared easily without forcing the receiver to use a proprietary
computing environment like Matlab. In general, every fully free program
grants its user the freedom to not only run and modify the software, but
also to copy and share it. To find software that is granting you these
freedoms, check out the 16796 records in the Free Software Directory.



It is a shame that mega-corporations are trying to limit a user's freedom
to share; that they not only prevent interoperability between social media
platforms
and messengers to maintain their monopolies, but also
impose DRM on books and other media. It is often misunderstood that
sharing has to be noncommercial. Most people are absolutely willing to pay
for a copy of a free (as in freedom) program that has been developed
professionally, or a DRM-free song, movie or e-book that is shared
with them. Professional development as well as the creation of art requires
much time, sometimes many people, and numerous resources. Paying money
ensures the continuity of it. Many companies and a whole bunch of software
would not exist without the freedom to share. Even proprietary companies
build on free software and profit immensely from it. What I value in the
free software community, however, is the sharing for the sake of sharing;
for values like collaboration, community, solidarity, and participation.



In our year-end fundraiser and during this year's International
Day Against DRM (IDAD)
, we've been stressing the importance of
sharing. So much of what we do depends on sharing, studying, and
building upon the works of others. We can only truly foster free
software, free documentation, and free cultural works for users around
the world if we have the ability to share. This is why the freedom to
share is at the core of the FSF's work.



Can you join the effort to defend the freedom to share as an
FSF associate member?
You can start for as little as $10 per
month ($5 for students), or $120 per year. With your support, we can
continue to show people how the freedom to share can affect change in
all areas where software touches modern life. Besides that, your
membership gives strength to the idea of free software. Plus, your
membership will count towards achieving our fall goal of 455 new
associate members before December 31, and you will be eligible for
this year's snazzy and secure webcam cover when you join as an annual
associate member at $120 or more. You'll also be able to enjoy all the
member benefits, which include merchandise discounts, a 16GB
bootable membership card, and use of our associate member
videoconferencing server.



As the FSF's program manager, I want to stand up for the freedom to share, and
look forward to working with you to do that. Please help spread the
message on social media networks using the hashtag #FreedomToShare.



Yours in freedom,



Miriam Bastian

Program Manager



Illustration Copyright © 2022, Free Software Foundation, Inc.
Licensed under Creative Commons Attribution 4.0 International
license.








--=_cc9ff27cc3d70e7c7027f0d649c92254--

--===============0057406314==
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

--===============0057406314==--

--===============0057406314==
Content-Type: multipart/alternative;
boundary="=_cc9ff27cc3d70e7c7027f0d649c92254"

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

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

*Read and share online: *


Dear Ruben Safir,

Sharing is what makes a strong community. It has always impressed me to see how
people in the free software community share their time, ideas, achievements,
knowledge, and software with others. This sharing community is what attracted
me in the first place to the free software movement: I wanted to know what it
is that people spend so much time and joint effort on and why. What I found
convinced me and won me over to free software.

I started to climb the [freedom ladder][1] in 2014. Having profited
from software like [KeePassXC][2], [Calibre][3], [LibreOffice][4],
[F-Droid][5], [Zotero][6], [VLC media player][7], [Privacy Badger][8],
and [TeXstudio][9] for more than seven years, I wanted to give back to
the free software community. When the Free Software Foundation (FSF)
was looking for a program manager, I considered this to be the perfect
opportunity to utilize my organizational, managerial, and
interpersonal skills, and I am immensely grateful that I now have
the privilege to contribute to the free software movement as the FSF's
program manager.

[1]: https://www.fsf.org/campaigns/campaigns-summaries#ladder
[2]: https://directory.fsf.org/wiki/KeePassXC
[3]: https://directory.fsf.org/wiki/Calibre
[4]: https://directory.fsf.org/wiki/LibreOffice
[5]: https://directory.fsf.org/wiki/F-Droid
[6]: https://directory.fsf.org/wiki/Zotero_client
[7]: https://directory.fsf.org/wiki/VLC_media_player
[8]: https://directory.fsf.org/wiki/Privacy_Badger
[9]: https://directory.fsf.org/wiki/TeXstudio

My path to the FSF took me through academia. During my doctorate, I spent four
years writing articles and contributing to collaborative volumes which I was
not allowed to share after the publication because the authors, who do the
research and write the text, usually have to assign the distribution rights to
the publishers and for decades [most of the academic publishers have distributed
books in DRM-restricted, proprietary, and incompatible formats][10]. This is
why policies such as the memorandum to ensure ["Free, Immediate, and Equitable
Access to Federally Funded Research"][11] published this year in August by the
White House Office of Science and Technology Policy (OSTP) or projects like
["Developing Institutional Open Access Publishing Models to Advance Scholarly
Communication" (DIAMAS)][12] which in September launched a project to develop
a diamond open access publishing model are long-overdue steps in the right
direction. These initiatives work to ensure that scientific data resulting from
federally funded research and peer reviewed scholarly publications are made
freely available and publicly accessible by default. Academia, as with so many
other fields, cannot exist without collaboration. But how can we collaborate if
we lack the freedom to share the code, the data, the documents, the articles,
and the (e-)books we are working with?

[10]: https://www.theguardian.com/higher-education-network/blog/2013/feb/26/digital-rights-managment-pdf-books
[11]: https://www.whitehouse.gov/wp-content/uploads/2022/08/08-2022-OSTP-Public-Access-Memo.pdf
[12]: https://diamasproject.eu/

Let me give one example from my experience in academia to illustrate this. At
the Department of Ancient History at the University of Zurich, I prepared
inscriptions from the Roman Empire for the Epigraphic Database Clauss / Slaby
(EDCS). Epigraphy is the study of inscriptions and there are hundreds of
epigraphists worldwide, all working to understand and analyze inscriptions from
the Roman Empire who therefore must be able to access images and texts of the
inscriptions. The easiest way to do this is to use an epigraphic database. But
there is not only one epigraphic database, there are plenty of them. In addition
to the EDCS, there are for example the [Epigraphic Database Roma (EDR)][13], the
[Epigraphic Database Heidelberg (EDH)][14], the database [Hispania Epigraphica][15],
and the database of the [Europeana network of Ancient Greek and Latin Epigraphy
(EAGLE)][16]. Most of them contain similar information about the same inscriptions.
So, why duplicate information instead of having one database or linking from one
to the other? Most of the datasets are not shareable, at least not in a compatible
format. It is very difficult to share the database and the software it's running on,
and this makes it close to impossible for different universities to work together
on the same database.

[13]: http://www.edr-edr.it/default/index.php
[14]: https://edh.ub.uni-heidelberg.de/
[15]: http://eda-bea.es/
[16]: https://www.eagle-network.eu/

Whether in the form of databases, books, or articles, the availability
and accessibility of findings is crucial to ensure high quality in
research. Rationales and results of any scientific research can only
be verified by others if scientists share the data they collect and
the code and configurations they used to collect it with others in a format
that everybody can open and process. Other scientists can only
reproduce measurements and thus build upon them if they are shared with
them in freedom.

But against all reason, universities and other research institutions
worldwide use proprietary software like [Matlab][17], the [Microsoft Office
suite][18], or [ArcGIS software][19], to name only a few. These companies
trap documents and data in their software, so that [users can't share them
with people][20] [who don't use the same software][21]. The same companies
claim that their products are made for collaboration. But they are designed
to do the opposite: to exclude people who don't use the product of the same
company. Imagine that people modify and improve a piece of software, adapt
it to their needs, but then, they are not allowed to share the improvements.
To give you an example: my favorite typesetting system, LaTeX, started as a
markup language for science. I could only use it for my PhD thesis in history
because some amazing people [adapted it for the use in the humanities][22]
and then shared their improvements in the form of TeX extensions as
[XeLaTeX][23] and [LuaLaTeX][24], and packages such as [betababel][25] which
for a long time has been the only way to write polytonic Ancient Greek.

[17]: https://www.mathworks.com/academia.html
[18]: https://www.mathworks.com/help/matlab/matlab_prog/share-live-scripts.html
[19]: https://spatial.usc.edu/software/proprietary-software-students/
[20]: https://www.zi.uzh.ch/en/students/software-elearning/microsoft.html
[21]: https://en.wikipedia.org/wiki/Arcgis
[22]: https://journals.openedition.org/lectures/9324
[23]: https://www.overleaf.com/blog/636-guest-blog-post-latex-for-the-humanities
[24]: https://www.ctan.org/pkg/lualatex-doc
[25]: https://www.ctan.org/pkg/betababel

No wonder that science is facing a [reproducibility crisis][26] after,
for decades, having produced books and used software which deny the
reader or user to share it. [DRM][27]-free books and free software are
important steps on the way out of this crisis, because we can only
build upon and advance the work of others if we have the freedom to
share it. The good news is that there is fantastic free software, free
documentation, free programming languages, and free tools that are made
for science and for sharing. Scientist who care about sharing often use
programs like [GNU Guix][28], or [Git][29], [which have reproducibility
and shareability at their core][30]. Code that has been written in [Python][31]
can be shared easily without forcing the receiver to use a proprietary
computing environment like Matlab. In general, every fully free program
grants its user the freedom to not only run and modify the software, but
also to copy and share it. To find software that is granting you these
freedoms, check out the 16796 records in the [Free Software Directory][32].

[26]: https://www.nature.com/articles/533452a
[27]: https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management
[28]: https://directory.fsf.org/wiki/Guix
[29]: https://directory.fsf.org/wiki/Git
[30]: https://www.nature.com/articles/s41597-022-01720-9.pdf
[31]: https://directory.fsf.org/wiki/Python
[32]: https://directory.fsf.org/wiki/Main_Page

It is a shame that mega-corporations are trying to limit a user's freedom
to share; that they not only [prevent interoperability between social media
platforms][40] and [messengers][41] to maintain their monopolies, but also
impose [DRM][27] on books and other media. It is often misunderstood that
sharing has to be noncommercial. Most people are absolutely willing to pay
for a copy of a free (as in freedom) program that has been developed
professionally, or a [DRM-free song, movie or e-book][42] that is shared
with them. Professional development as well as the creation of art requires
much time, sometimes many people, and numerous resources. Paying money
ensures the continuity of it. Many companies and a whole bunch of software
would not exist without the freedom to share. Even proprietary companies
build on free software and profit immensely from it. What I value in the
free software community, however, is the sharing for the sake of sharing;
for values like collaboration, community, solidarity, and participation.

[40]: https://www.eff.org/interoperablefacebook/
[41]: https://www.theverge.com/2022/3/24/22995431/european-union-digital-markets-act-imessage-whatsapp-interoperable
[27]: https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management
[42]: https://www.defectivebydesign.org/guide

In our [year-end fundraiser][44] and during this year's [International
Day Against DRM (IDAD)][45], we've been stressing the importance of
sharing. So much of what we do depends on sharing, studying, and
building upon the works of others. We can only truly foster free
software, free documentation, and free cultural works for users around
the world if we have the ability to share. This is why the freedom to
share is at the core of the FSF's work.

[44]: https://www.fsf.org/appeal
[45]: https://www.defectivebydesign.org/dayagainstdrm

**Can you join the effort to defend the freedom to share as an
[FSF associate member][49]?** You can start for as little as $10 per
month ($5 for students), or $120 per year. With your support, we can
continue to show people how the freedom to share can affect change in
all areas where software touches modern life. Besides that, your
membership gives strength to the *idea* of free software. Plus, your
membership will count towards achieving our fall goal of 455 new
associate members before December 31, and you will be eligible for
this year's snazzy and secure webcam cover when you join as an annual
associate member at $120 or more. You'll also be able to enjoy all the
[member benefits][48], which include merchandise discounts, a 16GB
bootable membership card, and use of our associate member
videoconferencing server.

[49]: https://my.fsf.org/join?mtm_campaign=fall22&mtm_source=campaigns
[48]: https://www.fsf.org/associate/benefits

As the FSF's program manager, I want to stand up for the freedom to share, and
look forward to working with you to do that. Please help spread the
message on [social media networks][50] using the hashtag #FreedomToShare.

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

Yours in freedom,

Miriam Bastian
Program Manager

--
* Follow us on Mastodon at , GNU social at
, PeerTube at , and on Twitter at -at-fsf.
* 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=166412&qid=79959427&h=fa7886765afe8d39.

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=166412&qid=79959427&h=fa7886765afe8d39.
--=_cc9ff27cc3d70e7c7027f0d649c92254
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







 

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



Read and share online: https://www.fsf.org/blogs/community/sharing-is-at-the-core-of-the-free-software-community





Dear Ruben Safir,



Sharing is what makes a strong community. It has always impressed me to see how
people in the free software community share their time, ideas, achievements,
knowledge, and software with others. This sharing community is what attracted
me in the first place to the free software movement: I wanted to know what it
is that people spend so much time and joint effort on and why. What I found
convinced me and won me over to free software.



I started to climb the freedom ladder in 2014. Having profited
from software like KeePassXC, Calibre, LibreOffice,
F-Droid, Zotero, VLC media player, Privacy Badger,
and TeXstudio for more than seven years, I wanted to give back to
the free software community. When the Free Software Foundation (FSF)
was looking for a program manager, I considered this to be the perfect
opportunity to utilize my organizational, managerial, and
interpersonal skills, and I am immensely grateful that I now have
the privilege to contribute to the free software movement as the FSF's
program manager.






Two minds facing each other and sharing concepts as the freedom to run,<BR>modify, study, and share software.




My path to the FSF took me through academia. During my doctorate, I spent four
years writing articles and contributing to collaborative volumes which I was
not allowed to share after the publication because the authors, who do the
research and write the text, usually have to assign the distribution rights to
the publishers and for decades most of the academic publishers have distributed
books in DRM-restricted, proprietary, and incompatible formats
. This is
why policies such as the memorandum to ensure "Free, Immediate, and Equitable
Access to Federally Funded Research"
published this year in August by the
White House Office of Science and Technology Policy (OSTP) or projects like
"Developing Institutional Open Access Publishing Models to Advance Scholarly
Communication" (DIAMAS)
which in September launched a project to develop
a diamond open access publishing model are long-overdue steps in the right
direction. These initiatives work to ensure that scientific data resulting from
federally funded research and peer reviewed scholarly publications are made
freely available and publicly accessible by default. Academia, as with so many
other fields, cannot exist without collaboration. But how can we collaborate if
we lack the freedom to share the code, the data, the documents, the articles,
and the (e-)books we are working with?



Let me give one example from my experience in academia to illustrate this. At
the Department of Ancient History at the University of Zurich, I prepared
inscriptions from the Roman Empire for the Epigraphic Database Clauss / Slaby
(EDCS). Epigraphy is the study of inscriptions and there are hundreds of
epigraphists worldwide, all working to understand and analyze inscriptions from
the Roman Empire who therefore must be able to access images and texts of the
inscriptions. The easiest way to do this is to use an epigraphic database. But
there is not only one epigraphic database, there are plenty of them. In addition
to the EDCS, there are for example the Epigraphic Database Roma (EDR), the
Epigraphic Database Heidelberg (EDH), the database Hispania Epigraphica,
and the database of the Europeana network of Ancient Greek and Latin Epigraphy
(EAGLE)
. Most of them contain similar information about the same inscriptions.
So, why duplicate information instead of having one database or linking from one
to the other? Most of the datasets are not shareable, at least not in a compatible
format. It is very difficult to share the database and the software it's running on,
and this makes it close to impossible for different universities to work together
on the same database.



Whether in the form of databases, books, or articles, the availability
and accessibility of findings is crucial to ensure high quality in
research. Rationales and results of any scientific research can only
be verified by others if scientists share the data they collect and
the code and configurations they used to collect it with others in a format
that everybody can open and process. Other scientists can only
reproduce measurements and thus build upon them if they are shared with
them in freedom.



But against all reason, universities and other research institutions
worldwide use proprietary software like Matlab, the Microsoft Office
suite
, or ArcGIS software, to name only a few. These companies
trap documents and data in their software, so that users can't share them
with people
who don't use the same software. The same companies
claim that their products are made for collaboration. But they are designed
to do the opposite: to exclude people who don't use the product of the same
company. Imagine that people modify and improve a piece of software, adapt
it to their needs, but then, they are not allowed to share the improvements.
To give you an example: my favorite typesetting system, LaTeX, started as a
markup language for science. I could only use it for my PhD thesis in history
because some amazing people adapted it for the use in the humanities
and then shared their improvements in the form of TeX extensions as
XeLaTeX and LuaLaTeX, and packages such as betababel which
for a long time has been the only way to write polytonic Ancient Greek.



No wonder that science is facing a reproducibility crisis after,
for decades, having produced books and used software which deny the
reader or user to share it. DRM-free books and free software are
important steps on the way out of this crisis, because we can only
build upon and advance the work of others if we have the freedom to
share it. The good news is that there is fantastic free software, free
documentation, free programming languages, and free tools that are made
for science and for sharing. Scientist who care about sharing often use
programs like GNU Guix, or Git, which have reproducibility
and shareability at their core
. Code that has been written in Python
can be shared easily without forcing the receiver to use a proprietary
computing environment like Matlab. In general, every fully free program
grants its user the freedom to not only run and modify the software, but
also to copy and share it. To find software that is granting you these
freedoms, check out the 16796 records in the Free Software Directory.



It is a shame that mega-corporations are trying to limit a user's freedom
to share; that they not only prevent interoperability between social media
platforms
and messengers to maintain their monopolies, but also
impose DRM on books and other media. It is often misunderstood that
sharing has to be noncommercial. Most people are absolutely willing to pay
for a copy of a free (as in freedom) program that has been developed
professionally, or a DRM-free song, movie or e-book that is shared
with them. Professional development as well as the creation of art requires
much time, sometimes many people, and numerous resources. Paying money
ensures the continuity of it. Many companies and a whole bunch of software
would not exist without the freedom to share. Even proprietary companies
build on free software and profit immensely from it. What I value in the
free software community, however, is the sharing for the sake of sharing;
for values like collaboration, community, solidarity, and participation.



In our year-end fundraiser and during this year's International
Day Against DRM (IDAD)
, we've been stressing the importance of
sharing. So much of what we do depends on sharing, studying, and
building upon the works of others. We can only truly foster free
software, free documentation, and free cultural works for users around
the world if we have the ability to share. This is why the freedom to
share is at the core of the FSF's work.



Can you join the effort to defend the freedom to share as an
FSF associate member?
You can start for as little as $10 per
month ($5 for students), or $120 per year. With your support, we can
continue to show people how the freedom to share can affect change in
all areas where software touches modern life. Besides that, your
membership gives strength to the idea of free software. Plus, your
membership will count towards achieving our fall goal of 455 new
associate members before December 31, and you will be eligible for
this year's snazzy and secure webcam cover when you join as an annual
associate member at $120 or more. You'll also be able to enjoy all the
member benefits, which include merchandise discounts, a 16GB
bootable membership card, and use of our associate member
videoconferencing server.



As the FSF's program manager, I want to stand up for the freedom to share, and
look forward to working with you to do that. Please help spread the
message on social media networks using the hashtag #FreedomToShare.



Yours in freedom,



Miriam Bastian

Program Manager



Illustration Copyright © 2022, Free Software Foundation, Inc.
Licensed under Creative Commons Attribution 4.0 International
license.








--=_cc9ff27cc3d70e7c7027f0d649c92254--

--===============0057406314==
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

--===============0057406314==--

  1. 2022-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] where it all began..
  2. 2022-12-02 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Faucci's credibility problem...
  3. 2022-12-01 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter -- Issue 176,
  4. 2022-12-03 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The oddity of the Arts, Collectors and providence
  5. 2022-12-03 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Birthright Financial problems and the unspoken
  6. 2022-12-03 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Microcode Hell
  7. 2022-12-04 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Microcode Hell
  8. 2022-12-05 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Change in Iran
  9. 2022-12-05 From: "Medscape Trending Alert" <Medscape_Trending_Alert-at-mail.medscape.com> Subject: [Hangout - NYLXS] FDA Pulls US Authorization for Eli Lilly's COVID
  10. 2022-12-06 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Doubling Down on a Broken Plan - MTA
  11. 2022-12-06 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Doubling Down on a Broken Plan - MTA
  12. 2022-12-06 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Doubling Down on a Broken Plan - MTA
  13. 2022-12-06 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Fall "Bulletin": Fully shareable, fully lovable
  14. 2022-12-07 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The Messiah is here - or so it says on the
  15. 2022-12-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Taiwan Chip Manufactoring in Arizona finding
  16. 2022-12-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Voting shanaigans
  17. 2022-12-09 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] How deep the data tracking problem is today
  18. 2022-12-09 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] boycot fever
  19. 2022-12-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] [Medscape_Trending_Alert-at-mail.medscape.com:
  20. 2022-12-11 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Open Source Military Intelligence
  21. 2022-12-12 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fusion
  22. 2022-12-12 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Don't play with the dangerous Chinese homicidal
  23. 2022-12-13 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Bob is gone
  24. 2022-12-14 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Morning Breakfast conversation
  25. 2022-12-13 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Amin Bandali: Why it's fun to participate in
  26. 2022-12-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] turmoil in education
  27. 2022-12-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] VPN
  28. 2022-12-20 NYOUG <execdir-at-nyoug.org> Subject: [Hangout - NYLXS] Upcoming Events for Oracle Professionals
  29. 2022-12-20 Numismatic Crime Information Center <doug-at-numismaticcrimes.org> Subject: [Hangout - NYLXS] "Numismatic Crimes Escalate During Last
  30. 2022-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Messiah Madess
  31. 2022-12-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Drugs and More drugs and Kickbacks and Scams
  32. 2022-12-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Drug Discounts for all
  33. 2022-12-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] More Good News
  34. 2022-12-21 Jordan from Masa <masainfo-at-join.masaisrael.org> Subject: [Hangout - NYLXS] =?utf-8?b?QmVhY2ggYW5kIFRlYWNoIPCfj5bvuI8r7aC8?=
  35. 2022-12-23 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The Climate costs in NY Law
  36. 2022-12-26 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Mother
  37. 2022-12-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Cost of lockdowns
  38. 2022-12-27 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] IDAD 2022: Celebrating the freedom to share with
  39. 2022-12-23 From: "Miriam Bastian" <info-at-fsf.org> Subject: [Hangout - NYLXS] Sharing is at the core of the free software
  40. 2022-12-28 From: "Medscape CME & Education" <Medscape-at-mail.medscape.org> Subject: [Hangout - NYLXS] =?utf-8?q?What=E2=80=99s_New_in_the_Treatment_?=
  41. 2022-12-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Spying and Data collection for tickets at
  42. 2022-12-29 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Spying and Data collection for tickets at
  43. 2022-12-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Spyware Pegasus hitting the big time
  44. 2022-12-29 sderrick <sderrick-at-optonline.net> Re: [Hangout - NYLXS] [Hangout Need used laptop. To install
  45. 2022-12-29 Ruben Safir <mrbrklyn-at-panix.com> Re: [Hangout - NYLXS] [Hangout Need used laptop. To install
  46. 2022-12-29 Ruben Safir <mrbrklyn-at-panix.com> Re: [Hangout - NYLXS] [Hangout Need used laptop. To install
  47. 2022-12-29 Ruben Safir <mrbrklyn-at-panix.com> Re: [Hangout - NYLXS] [Hangout Need used laptop. To install
  48. 2022-12-30 From: "Geoffrey Knauth, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Your FSF membership will help us build a stronger
  49. 2022-12-31 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Raul - the talking cat
  50. 2022-12-31 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Putting yourself under suspicion for your email
  51. 2022-12-31 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Education and Tech
  52. 2022-12-31 Paul Robert Marino <prmarino1-at-gmail.com> Re: [Hangout - NYLXS] Raul - the talking cat
  53. 2022-12-31 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Raul - the talking cat
  54. 2022-12-31 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Raul - the talking cat
  55. 2022-12-11 Thomas Krichel <krichel-at-openlib.org> Re: [Hangout - NYLXS] Perl veteran interviewed by NY TImes columnist

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