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