From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: guix-devel@gnu.org
Subject: Re: Meltdown / Spectre
Date: Thu, 11 Jan 2018 19:49:26 -0200 [thread overview]
Message-ID: <87po6ghxqx.fsf@hyperbola.info> (raw)
In-Reply-To: <87bmi0mb6r.fsf@gmail.com> (Katherine Cox-Buday's message of "Thu, 11 Jan 2018 13:45:32 -0600")
With regards to BSD-3-Clause-Clear and BSD-2-Clause-FreeBSD vs. GPL (and
variants), the latest version and "or-later" option of the latter allows
a chance to transfer the freedoms of the software to the end-users' copy
(it's not a perfect ingredient, because it depends on the rights holder
to enforce it but it's the necessary condition) while the former (the
BSD-likes) are too lax (the moment the rights holder decides to do
something, the person already lost the legal mechanisms that would allow
per to influence the derivative project's decision to guarantee that
end-users have their software freedom kept with the copy of the software
they have). Of course, this influence is best exercised with
collaboration for license compliance, and commitment from the
non-compliant to fix the issues. Besides, without the right amount of
regulation market moves faster than sustainability, and the permissive
nature of the first two licenses mentioned make a perfect tool for
opportunistic competitive behavior, in a century and with goods
where/which we can't spend time with Porterism nor with Social
Darwinisms.
As for the attempt to apply the same comparison to the possibility of a
microcode update: I guess it can be considered a matter of where one
wants to go. I see various projects which have some product which is
free/libre software, but have alternative products (from the same
origin) which do the same thing but which aren't free/libre, so for
those origins/projects I consider them a kind of "desperate attempt to
'reach out' to other people", even if it means not following the
free/libre software philosophy. Finally, I tend to not follow these
projects, nor recommend their free/libre products, because I find these
misleading.
2018-01-11T13:45:32-0600 Katherine Cox-Buday wrote:
> I really appreciate the viewpoints expressed here, thank you. It's a
> great reminder that software freedom doesn't exist in a vacuum, and that
> its intent is to do good. It's worth considering what that means in a
> more global context.
>
>
> I've been reading up on the philosophical differences between BSD and
> GNU licenses, and one of the points that's often made is that BSD is the
> freer of the two -- allowing users to do as they please -- but GNU
> expresses the most freedom globally and is therefore more ethical.
>
> It is a fun thought experiment to extrapolate and apply the same logic
> to this situation: what would express the most freedom globally:
> faithfully applying the GPL, or assisting users with securing their
> computing environments.
>
> Please note that I'm advocating any approach; only having a nice
> discussion with like-minded folks.
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
next prev parent reply other threads:[~2018-01-11 21:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 13:20 What do Meltdown and Spectre mean for libreboot x200 user? Alex Vong
2018-01-06 17:23 ` Mark H Weaver
2018-01-06 17:43 ` Meltdown / Spectre Leo Famulari
2018-01-06 20:15 ` Mark H Weaver
2018-01-07 6:38 ` Mark H Weaver
2018-01-07 21:29 ` Mark H Weaver
2018-01-09 21:39 ` Alex Vong
2018-01-10 4:59 ` Leo Famulari
2018-01-16 10:57 ` Ludovic Courtès
2018-01-19 22:06 ` Mark H Weaver
2018-01-20 0:17 ` Leo Famulari
2018-01-21 16:26 ` Mark H Weaver
2018-01-24 14:23 ` Ludovic Courtès
2018-01-24 16:19 ` Mark H Weaver
2018-01-26 22:05 ` Mark H Weaver
2018-01-27 16:12 ` Ludovic Courtès
2018-01-10 15:00 ` ng0
2018-01-08 10:30 ` Ludovic Courtès
2018-01-10 5:27 ` Leo Famulari
2018-01-07 2:44 ` Chris Marusich
2018-01-08 17:22 ` Katherine Cox-Buday
2018-01-08 18:26 ` Marius Bakke
2018-01-08 21:51 ` Tobias Geerinckx-Rice
2018-01-08 22:01 ` Tobias Geerinckx-Rice
2018-01-09 20:13 ` Katherine Cox-Buday
2018-01-09 21:18 ` Tobias Geerinckx-Rice
2018-01-10 5:26 ` Leo Famulari
2018-01-11 19:45 ` Katherine Cox-Buday
2018-01-11 21:49 ` Adonay Felipe Nogueira [this message]
2018-01-10 10:46 ` Tobias Platen
2018-01-10 17:20 ` Leo Famulari
2018-01-10 6:43 ` Christopher Lemmer Webber
2018-01-10 18:41 ` Kei Kebreau
2018-01-16 3:58 ` Chris Marusich
2018-01-17 19:20 ` Gábor Boskovits
2018-01-14 15:11 ` Alex Vong
2018-01-09 23:10 ` Mark H Weaver
2018-01-10 5:04 ` Leo Famulari
2018-01-16 11:10 ` Ludovic Courtès
2018-01-17 2:38 ` Mike Gerwitz
2018-01-17 14:11 ` Ludovic Courtès
2018-01-10 9:36 ` Chris Marusich
2018-01-10 11:49 ` Adonay Felipe Nogueira
2018-01-10 12:35 ` Tobias Platen
2018-01-10 14:04 ` Gábor Boskovits
2018-01-12 0:25 ` Marius Bakke
2018-01-15 8:07 ` Pjotr Prins
2018-01-16 3:08 ` Mike Gerwitz
2018-01-16 10:04 ` Pjotr Prins
2018-01-12 7:39 ` Chris Marusich
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po6ghxqx.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).