LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: lkcl <luke.leighton@gmail.com>
Cc: "Discussão do LibrePlanet" <libreplanet-discuss@libreplanet.org>,
	libreplanet-discuss-request@libreplanet.org
Subject: Re: Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects
Date: Tue, 17 May 2022 23:17:49 +0900	[thread overview]
Message-ID: <B7CA500B-2D9F-4B93-9C2B-9EF91E0B5EFC@yasuaki.com> (raw)
In-Reply-To: <CAPweEDxg-ETeX1gE2k10xjtZGZMojtt0QMH7Pd62iDA-HJOxDw@mail.gmail.com>

Sorry I have point this out...  you see, your comments are adding examples of how proprietary systems can be harmful...  But this in no way changes the nature of contradiction (using Emacs and Guix as convenient subjects for comparison) I have been mentioning, the main part of my question.

-Yasu

PS
* I think the pros and cons of using proprietary systems are well understood, perhaps, especially amongst the subscribers of this mailing list.

* It is worthy of mentioning as well, that the security argument may not be so convincing.  If there is a nasty security bug in the hardware and the immediate fix comes from the manufacturer in a proprietary BLOB?

> On May 17, 2022, at 22:48, lkcl <luke.leighton@gmail.com> wrote:
> 
> On Tue, May 17, 2022 at 1:51 PM Yasuaki Kudo <yasu@yasuaki.com> wrote:
> 
>> - Guix runs on Linux, the unabridged with all the proprietary bits and pieces for the video card, wifi and all.  The same comment as above... does not apply?  Because if it runs on unmodified Linux and people choose to do so, it hurts the project of promoting Free Software!
> 
> the exclusion of proprietary WIFI drivers does not make any sense until you
> see these:
> 
> * https://securityaffairs.co/wordpress/84142/breaking-news/broadcom-wifi-driver-flaws.html
> * https://thehackernews.com/2017/04/broadcom-wifi-hack.html
> * https://www.forbes.com/sites/gordonkelly/2021/09/18/apple-iphone-warning-security-wifi-ssid-new-iphone-hack/
> 
> which exposed LITERALLY BILLIONS of people to drive-by exploits
> 
> in that context, how is placing the exact same proprietary drivers onto
> a system *in any way* helping to promote Ethical Software principles?
> 
> it's the total opposite, isn't it? it's directly exposing users to
> harm, isn't it?
> 
> not only that, but it also risks the actual developers from being hit with
> a Class Action Lawsuit precisely because they exposed users to harm,
> isn't it?
> 
> debian makes the compromise that they put all the "nonfree" parts
> into a special repository "nonfree".  you have to *actively* choose
> whether to use that.
> 
> ubuntu says "yeah f*** that, we're just gonna expose users to harm
> because it's convenient"
> 
> GNU says "ultimately, if the user really wants to use nonfree parts
> that's entirely their choice, but we're not going to help them in any
> way to do so".
> 
> you *can* take an entirely Libre system and make it non-Libre.
> it's software, after all.  you have that choice.
> 
> l.

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2022-05-17 14:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.83.1652716864.26523.libreplanet-discuss@libreplanet.org>
2022-05-16 17:49 ` Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects lkcl
2022-05-17  0:59   ` Yasuaki Kudo
2022-05-17  9:53     ` lkcl
2022-05-17 10:38       ` Yasuaki Kudo
2022-05-17 12:05         ` lkcl
2022-05-17 12:51           ` Yasuaki Kudo
2022-05-17 13:48             ` lkcl
2022-05-17 14:17               ` Yasuaki Kudo [this message]
2022-05-17 14:40             ` Greg Farough
2022-05-17 15:38               ` Andrew Yu via libreplanet-discuss
2022-05-18  0:55                 ` Yasuaki Kudo
2022-05-17 17:14             ` Jean Louis
2022-05-17 13:48         ` Jean Louis
2022-05-15  2:25 Yasuaki Kudo
2022-05-15 17:11 ` andrew via libreplanet-discuss
2022-05-16  9:10   ` Yasuaki Kudo
2022-05-16 11:08     ` andrew via libreplanet-discuss
2022-05-16 11:55       ` Yasuaki Kudo
2022-05-17  6:51     ` Jean Louis
2022-05-17  6:57       ` andrew via libreplanet-discuss
2022-05-17  8:12       ` Yasuaki Kudo
2022-05-17  8:48         ` andrew via libreplanet-discuss
2022-05-17 13:35         ` Jean Louis
2022-05-17 14:02           ` Yasuaki Kudo
2022-05-18  3:12     ` Alexandre Oliva
2022-05-17  6:39 ` Jean Louis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B7CA500B-2D9F-4B93-9C2B-9EF91E0B5EFC@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=libreplanet-discuss-request@libreplanet.org \
    --cc=libreplanet-discuss@libreplanet.org \
    --cc=luke.leighton@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).