Thu Apr 18 22:45:07 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 2023-06-01

HANGOUT

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

Key: Value:

Key: Value:

MESSAGE
DATE 2023-06-13
FROM From: "Free Software Foundation"
SUBJECT Subject: [Hangout - NYLXS] FTC's solicitation for public comments: Make your
From hangout-bounces-at-nylxs.com Thu Jun 15 11:39:07 2023
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 576B116408A;
Thu, 15 Jun 2023 11:39:07 -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 2D3E1164077; Thu, 15 Jun 2023 11:39:02 -0400 (EDT)
Resent-From: Ruben Safir
Resent-Date: Thu, 15 Jun 2023 11:39:02 -0400
Resent-Message-ID: <20230615153902.GA8879-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 47DD8164067
for ; Tue, 13 Jun 2023 14:38:11 -0400 (EDT)
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=nYUxopARAxlzRwYUfCfySnbCRUksTBJ9ZOJa4MyKlPc=; b=brZA7Z22Mkxqnt
c6o4WXD/pTPdUWMEOdXhoFJXB3Ezp23bQ9KPfxue7v9pOZUhJFdslHJe8+nnEnZeJ2FlhCdkZgWgj
aaUvo0Ef4ZcMxJDsfr3Gh73fGQGScxgt92XagJiBaKfrDstamdwY5Fd+/wedcnShQ1a3FNAV10U75
E+ZCsdFa4ivmSnvQeCGrmdyxeudQZWUnKfxD6wSAYGTUnUJBjSNLzQGIU5bsMXKbzD605XaBirDLx
Kd8Y/YDs/SZQHnIwoSY41PjN69XLn4EvK5+qdn09PRlgt6tBbYqmYIHk0FOnZNU86SQfHPdnikH3F
bl+MNZcBx6fS7Hm8pn+Q==;
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 1q98u9-00DZnM-06
for ruben-at-mrbrklyn.com; Tue, 13 Jun 2023 14:38:09 -0400
Received: from localhost ([::1] helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.90_1)
(envelope-from )
id 1q98u8-0005Ln-N9
for ruben-at-mrbrklyn.com; Tue, 13 Jun 2023 14:38:08 -0400
MIME-Version: 1.0
From: "Free Software Foundation"
job_id: 166988
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.166988.82578751.c8b6ef09251a6cf8-at-fsf.org
Date: Tue, 13 Jun 2023 14:38:08 -0400
Message-Id:
Subject: [Hangout - NYLXS] FTC's solicitation for public comments: Make your
voice heard
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: Free Software Foundation
Content-Type: multipart/mixed; boundary="===============0467759940=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============0467759940==
Content-Type: multipart/alternative;
boundary="=_c8849f58bfbe9bafdbb8373e1285ed35"

--=_c8849f58bfbe9bafdbb8373e1285ed35
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,

[The Federal Trade Commission (FTC)][1] wields considerable influence
over technology. Now, they are [soliciting public comments][2] on the
business practices of so-called "[cloud computing][3]" providers. In a
recent announcement, the FTC said that its staff are seeking to better
understand the impact of [the growing reliance on [cloud
computing][3]], the broader competitive dynamics in [cloud
computing][3], its implications for artificial intelligence, and
potential security risks in the use of [the] [cloud][3]."

Since it isn't every day that the FTC solicits public comments on
subjects in which the free software community is so well-versed, let's
take this opportunity to submit comments that support digital
sovereignty. The hope is to persuade policy makers to make software
freedom and privacy a central part of any future considerations made
in the areas of storage, computation, and services. Such comments will
be made part of the public record, so any participation promises to
have a lasting impact.

[1]: https://www.ftc.gov/
[2]: https://www.ftc.gov/news-events/news/press-releases/2023/05/ftc-host-virtual-panel-discussion-cloud-computing-extends-comment-deadline
[3]: https://www.gnu.org/philosophy/words-to-avoid.html#CloudComputing

## Take Action

Write about it! Help influence decision makers and docket commentors
by writing on the subject. As for your text, we have prepared the
following points for consideration:

* When considering rules and regulations in technology that stand to
protect people's fundamental civil liberties, it is important to
start from the question, "does this decision improve digital
sovereignty or diminish it?"
* In the case of computing, (e.g. word processing, spreadsheet, and
graphic design programs), the typical options diminish digital
sovereignty because the [computations are being run on another
computer under someone else's control][4], inaccessible to the end
user, who therefore does not have the essential freedoms to share,
modify, and study the computations (i.e. the program). The only real
solution to this is to offer [free "as in freedom"][5] replacements
of those programs, so that end users may maintain control over their
computing.
* In the case of storage, today's typical options diminish digital
sovereignty because many storage providers only provide unencrypted
options for storage. It is imperative that individuals and
businesses who choose third-party storage always have the choice to
encrypt their storage, and the encryption keys must be entirely
within the control of the end user, not the third-party provider.
* In the case of services (such as email, teleconferencing, and
videoconferencing), while the source code that runs services need not
necessarily be made public, end users deserve to be able to access
such services via a free software client. In such cases, it is
imperative that service providers implement a design of
interoperability, so that end users may use the service with any
choice of client.
* Free software allows end users to inspect the software for possible
security flaws, while proprietary software does not. Therefore free
software is the only realistic option for an end user to achieve
verifiable security.

[4]: https://www.gnu.org/philosophy/who-does-that-server-really-serve.html
[5]: https://www.gnu.org/philosophy/free-sw.html

Such responses address the questions being asked by the FTC in the
*Market power and business practices affecting competition* section of
their instructions, while maintaining focus on our free software
advocacy efforts.

Feel free to use any of these suggestions, adapting them to your own
style of writing. The only thing we ask is that you keep the free
software message strong throughout. If you would like to run any ideas
by us before submitting, we are delighted to receive your drafts at
.

### A note about the FTC docket website

*Unfortunately, the FTC's website requires nonfree JavaScript
(reCAPTCHA, specifically) to comment on a document, and the FTC has
declined repeated requests for instructions for how to submit comments
by [paper form][6]. If you're not in the habit of avoiding nonfree
JavaScript for the sake of your freedom, which we recommend, you can
also leave comments on the FTC's website. While you're there, let
know about the injustice of proprietary JavaScript
and encourage them to respect the freedom of their users.*

[6]: https://www.ftc.gov/policy/public-comments

If you would like to join us in reaching out to the FTC to request
comments be accepted in ways that do not require running nonfree
JavaScript, please consider contacting their office by mail and/or
phone:

Federal Trade Commission
600 Pennsylvania Avenue, NW
Washington, DC 20580
Telephone: (202) 326-2222

The deadline to submit is June 21, which is just enough time to
publish something meaningful on the topic in support of free software.

In solidarity,
Free Software Foundation

--
* 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:
* Subscribe to our RSS feeds:
* Join us as an associate member:
* Read our Privacy Policy:

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=166988&qid=82578751&h=c8b6ef09251a6cf8.

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=166988&qid=82578751&h=c8b6ef09251a6cf8.
--=_c8849f58bfbe9bafdbb8373e1285ed35
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/ftcs-solicitation-for-public-comments-make-your-voice-heard





Dear Ruben Safir,



The Federal Trade Commission (FTC) wields considerable influence
over technology. Now, they are soliciting public comments on the
business practices of so-called "cloud computing" providers. In a
recent announcement, the FTC said that its staff are seeking to better
understand the impact of [the growing reliance on cloud
computing
], the broader competitive dynamics in cloud
computing
, its implications for artificial intelligence, and
potential security risks in the use of [the] cloud."



Since it isn't every day that the FTC solicits public comments on
subjects in which the free software community is so well-versed, let's
take this opportunity to submit comments that support digital
sovereignty. The hope is to persuade policy makers to make software
freedom and privacy a central part of any future considerations made
in the areas of storage, computation, and services. Such comments will
be made part of the public record, so any participation promises to
have a lasting impact.



Take Action



Write about it! Help influence decision makers and docket commentors
by writing on the subject. As for your text, we have prepared the
following points for consideration:




  • When considering rules and regulations in technology that stand to
    protect people's fundamental civil liberties, it is important to
    start from the question, "does this decision improve digital
    sovereignty or diminish it?"

  • In the case of computing, (e.g. word processing, spreadsheet, and
    graphic design programs), the typical options diminish digital
    sovereignty because the computations are being run on another
    computer under someone else's control
    , inaccessible to the end
    user, who therefore does not have the essential freedoms to share,
    modify, and study the computations (i.e. the program). The only real
    solution to this is to offer free "as in freedom" replacements
    of those programs, so that end users may maintain control over their
    computing.

  • In the case of storage, today's typical options diminish digital
    sovereignty because many storage providers only provide unencrypted
    options for storage. It is imperative that individuals and
    businesses who choose third-party storage always have the choice to
    encrypt their storage, and the encryption keys must be entirely
    within the control of the end user, not the third-party provider.

  • In the case of services (such as email, teleconferencing, and
    videoconferencing), while the source code that runs services need not
    necessarily be made public, end users deserve to be able to access
    such services via a free software client. In such cases, it is
    imperative that service providers implement a design of
    interoperability, so that end users may use the service with any
    choice of client.

  • Free software allows end users to inspect the software for possible
    security flaws, while proprietary software does not. Therefore free
    software is the only realistic option for an end user to achieve
    verifiable security.




Such responses address the questions being asked by the FTC in the
Market power and business practices affecting competition section of
their instructions, while maintaining focus on our free software
advocacy efforts.



Feel free to use any of these suggestions, adapting them to your own
style of writing. The only thing we ask is that you keep the free
software message strong throughout. If you would like to run any ideas
by us before submitting, we are delighted to receive your drafts at
campaigns@fsf.org.



A note about the FTC docket website



Unfortunately, the FTC's website requires nonfree JavaScript
(reCAPTCHA, specifically) to comment on a document, and the FTC has
declined repeated requests for instructions for how to submit comments
by paper form. If you're not in the habit of avoiding nonfree
JavaScript for the sake of your freedom, which we recommend, you can
also leave comments on the FTC's website. While you're there, let
webmaster@ftc.gov know about the injustice of proprietary JavaScript
and encourage them to respect the freedom of their users.



If you would like to join us in reaching out to the FTC to request
comments be accepted in ways that do not require running nonfree
JavaScript, please consider contacting their office by mail and/or
phone:



Federal Trade Commission

600 Pennsylvania Avenue, NW

Washington, DC 20580

Telephone: (202) 326-2222



The deadline to submit is June 21, which is just enough time to
publish something meaningful on the topic in support of free software.



In solidarity,

Free Software Foundation








--=_c8849f58bfbe9bafdbb8373e1285ed35--

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

--===============0467759940==--

--===============0467759940==
Content-Type: multipart/alternative;
boundary="=_c8849f58bfbe9bafdbb8373e1285ed35"

--=_c8849f58bfbe9bafdbb8373e1285ed35
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,

[The Federal Trade Commission (FTC)][1] wields considerable influence
over technology. Now, they are [soliciting public comments][2] on the
business practices of so-called "[cloud computing][3]" providers. In a
recent announcement, the FTC said that its staff are seeking to better
understand the impact of [the growing reliance on [cloud
computing][3]], the broader competitive dynamics in [cloud
computing][3], its implications for artificial intelligence, and
potential security risks in the use of [the] [cloud][3]."

Since it isn't every day that the FTC solicits public comments on
subjects in which the free software community is so well-versed, let's
take this opportunity to submit comments that support digital
sovereignty. The hope is to persuade policy makers to make software
freedom and privacy a central part of any future considerations made
in the areas of storage, computation, and services. Such comments will
be made part of the public record, so any participation promises to
have a lasting impact.

[1]: https://www.ftc.gov/
[2]: https://www.ftc.gov/news-events/news/press-releases/2023/05/ftc-host-virtual-panel-discussion-cloud-computing-extends-comment-deadline
[3]: https://www.gnu.org/philosophy/words-to-avoid.html#CloudComputing

## Take Action

Write about it! Help influence decision makers and docket commentors
by writing on the subject. As for your text, we have prepared the
following points for consideration:

* When considering rules and regulations in technology that stand to
protect people's fundamental civil liberties, it is important to
start from the question, "does this decision improve digital
sovereignty or diminish it?"
* In the case of computing, (e.g. word processing, spreadsheet, and
graphic design programs), the typical options diminish digital
sovereignty because the [computations are being run on another
computer under someone else's control][4], inaccessible to the end
user, who therefore does not have the essential freedoms to share,
modify, and study the computations (i.e. the program). The only real
solution to this is to offer [free "as in freedom"][5] replacements
of those programs, so that end users may maintain control over their
computing.
* In the case of storage, today's typical options diminish digital
sovereignty because many storage providers only provide unencrypted
options for storage. It is imperative that individuals and
businesses who choose third-party storage always have the choice to
encrypt their storage, and the encryption keys must be entirely
within the control of the end user, not the third-party provider.
* In the case of services (such as email, teleconferencing, and
videoconferencing), while the source code that runs services need not
necessarily be made public, end users deserve to be able to access
such services via a free software client. In such cases, it is
imperative that service providers implement a design of
interoperability, so that end users may use the service with any
choice of client.
* Free software allows end users to inspect the software for possible
security flaws, while proprietary software does not. Therefore free
software is the only realistic option for an end user to achieve
verifiable security.

[4]: https://www.gnu.org/philosophy/who-does-that-server-really-serve.html
[5]: https://www.gnu.org/philosophy/free-sw.html

Such responses address the questions being asked by the FTC in the
*Market power and business practices affecting competition* section of
their instructions, while maintaining focus on our free software
advocacy efforts.

Feel free to use any of these suggestions, adapting them to your own
style of writing. The only thing we ask is that you keep the free
software message strong throughout. If you would like to run any ideas
by us before submitting, we are delighted to receive your drafts at
.

### A note about the FTC docket website

*Unfortunately, the FTC's website requires nonfree JavaScript
(reCAPTCHA, specifically) to comment on a document, and the FTC has
declined repeated requests for instructions for how to submit comments
by [paper form][6]. If you're not in the habit of avoiding nonfree
JavaScript for the sake of your freedom, which we recommend, you can
also leave comments on the FTC's website. While you're there, let
know about the injustice of proprietary JavaScript
and encourage them to respect the freedom of their users.*

[6]: https://www.ftc.gov/policy/public-comments

If you would like to join us in reaching out to the FTC to request
comments be accepted in ways that do not require running nonfree
JavaScript, please consider contacting their office by mail and/or
phone:

Federal Trade Commission
600 Pennsylvania Avenue, NW
Washington, DC 20580
Telephone: (202) 326-2222

The deadline to submit is June 21, which is just enough time to
publish something meaningful on the topic in support of free software.

In solidarity,
Free Software Foundation

--
* 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:
* Subscribe to our RSS feeds:
* Join us as an associate member:
* Read our Privacy Policy:

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=166988&qid=82578751&h=c8b6ef09251a6cf8.

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=166988&qid=82578751&h=c8b6ef09251a6cf8.
--=_c8849f58bfbe9bafdbb8373e1285ed35
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/ftcs-solicitation-for-public-comments-make-your-voice-heard





Dear Ruben Safir,



The Federal Trade Commission (FTC) wields considerable influence
over technology. Now, they are soliciting public comments on the
business practices of so-called "cloud computing" providers. In a
recent announcement, the FTC said that its staff are seeking to better
understand the impact of [the growing reliance on cloud
computing
], the broader competitive dynamics in cloud
computing
, its implications for artificial intelligence, and
potential security risks in the use of [the] cloud."



Since it isn't every day that the FTC solicits public comments on
subjects in which the free software community is so well-versed, let's
take this opportunity to submit comments that support digital
sovereignty. The hope is to persuade policy makers to make software
freedom and privacy a central part of any future considerations made
in the areas of storage, computation, and services. Such comments will
be made part of the public record, so any participation promises to
have a lasting impact.



Take Action



Write about it! Help influence decision makers and docket commentors
by writing on the subject. As for your text, we have prepared the
following points for consideration:




  • When considering rules and regulations in technology that stand to
    protect people's fundamental civil liberties, it is important to
    start from the question, "does this decision improve digital
    sovereignty or diminish it?"

  • In the case of computing, (e.g. word processing, spreadsheet, and
    graphic design programs), the typical options diminish digital
    sovereignty because the computations are being run on another
    computer under someone else's control
    , inaccessible to the end
    user, who therefore does not have the essential freedoms to share,
    modify, and study the computations (i.e. the program). The only real
    solution to this is to offer free "as in freedom" replacements
    of those programs, so that end users may maintain control over their
    computing.

  • In the case of storage, today's typical options diminish digital
    sovereignty because many storage providers only provide unencrypted
    options for storage. It is imperative that individuals and
    businesses who choose third-party storage always have the choice to
    encrypt their storage, and the encryption keys must be entirely
    within the control of the end user, not the third-party provider.

  • In the case of services (such as email, teleconferencing, and
    videoconferencing), while the source code that runs services need not
    necessarily be made public, end users deserve to be able to access
    such services via a free software client. In such cases, it is
    imperative that service providers implement a design of
    interoperability, so that end users may use the service with any
    choice of client.

  • Free software allows end users to inspect the software for possible
    security flaws, while proprietary software does not. Therefore free
    software is the only realistic option for an end user to achieve
    verifiable security.




Such responses address the questions being asked by the FTC in the
Market power and business practices affecting competition section of
their instructions, while maintaining focus on our free software
advocacy efforts.



Feel free to use any of these suggestions, adapting them to your own
style of writing. The only thing we ask is that you keep the free
software message strong throughout. If you would like to run any ideas
by us before submitting, we are delighted to receive your drafts at
campaigns@fsf.org.



A note about the FTC docket website



Unfortunately, the FTC's website requires nonfree JavaScript
(reCAPTCHA, specifically) to comment on a document, and the FTC has
declined repeated requests for instructions for how to submit comments
by paper form. If you're not in the habit of avoiding nonfree
JavaScript for the sake of your freedom, which we recommend, you can
also leave comments on the FTC's website. While you're there, let
webmaster@ftc.gov know about the injustice of proprietary JavaScript
and encourage them to respect the freedom of their users.



If you would like to join us in reaching out to the FTC to request
comments be accepted in ways that do not require running nonfree
JavaScript, please consider contacting their office by mail and/or
phone:



Federal Trade Commission

600 Pennsylvania Avenue, NW

Washington, DC 20580

Telephone: (202) 326-2222



The deadline to submit is June 21, which is just enough time to
publish something meaningful on the topic in support of free software.



In solidarity,

Free Software Foundation








--=_c8849f58bfbe9bafdbb8373e1285ed35--

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

--===============0467759940==--

  1. 2023-06-01 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter -- Issue 182, June 2023
  2. 2023-06-04 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] so much for AI and Wikipedia
  3. 2023-06-06 From: "Professional Career Services" <nj-at-nj.pcsjobs.org> Subject: [Hangout - NYLXS] PCS Postings June 6 2023
  4. 2023-06-12 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #620 - Abandoned modules?
  5. 2023-06-12 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] [SUSPECTED SPAM] Re: [EXTERNAL] Re: From the
  6. 2023-06-13 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] FTC's solicitation for public comments: Make your
  7. 2023-06-16 From: "American Numismatic Society" <membership-at-numismatics.org> Subject: [Hangout - NYLXS] Join us for today's Long Table with Anna
  8. 2023-06-16 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] trusting the Goverment with EVERYTHING - Thanks
  9. 2023-06-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] free classes
  10. 2023-06-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] This is worth a note and a look.
  11. 2023-06-20 From: "Miriam Bastian, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] We have nothing to hide,
  12. 2023-06-21 From: "Miriam Bastian, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Join us for a Kdenlive workshop
  13. 2023-06-22 From: "O'Reilly" <reply-at-et.oreilly.com> Subject: [Hangout - NYLXS] =?utf-8?q?=E2=9A=A1_Flash_sale!_=24299_for_a_y?=
  14. 2023-06-26 From: "Professional Career Services" <nj-at-nj.pcsjobs.org> Subject: [Hangout - NYLXS] Tonight! Software and Web Development Open House
  15. 2023-06-26 From: "Professional Career Services" <nj-at-nj.pcsjobs.org> Subject: [Hangout - NYLXS] Tonight! Software and Web Development Open House
  16. 2023-06-27 From: =?utf-8?Q?Zo=C3=AB_Kooyman=2C_FSF?= <info-at-fsf.org> Subject: [Hangout - NYLXS] Help the FSF's work for free software
  17. 2023-06-27 From: "O'Reilly" <reply-at-et.oreilly.com> Subject: [Hangout - NYLXS] Sale extended!
  18. 2023-06-28 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Drug Abuse at the top of Silicon Valley
  19. 2023-06-28 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Shazzam - fingerprinting
  20. 2023-06-28 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The extroordinary universe from a new perspective
  21. 2023-06-29 From: "Anouk Rozestraten, FSF" <sales-at-fsf.org> Subject: [Hangout - NYLXS] Keep cool with GNU summer swag
  22. 2023-06-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Rise of the RNA machines: Self-amplification in

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