unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Why Mozilla Firefox is nonfree? (was: Vanilla Firefox recipe?)
Date: Wed, 27 May 2020 08:16:47 +0300	[thread overview]
Message-ID: <eer63qkg.dag@gnui.org> (raw)
In-Reply-To: <87367nydku.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Mon, 25 May 2020 16:17:05 -0400")

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]

Christopher Lemmer Webber <cwebber@dustycloud.org> wrote:
> I'm not sure it's really accurate to categorize asking for a vanilla copy of firefox, which might not comply with the FSDG, as nonfree software.  The primary issue with Firefox that makes it qualify as "nonfree" is that the add-ons tool brings you to something that might guide a user towards nonfree software right?

Nope.  Firefox, as distributed by Mozilla, is simply not a free software.  Just reread the agreement with Mozilla [0] you are supposed to abide.  You are _not_ free even to redistribute _exact_ copies of it, let aside distributing modified ones:

| You may distribute unaltered copies of Mozilla Firefox and other Mozilla software from Mozilla.org without express permission from Mozilla as long as you comply with the following rules:
|
|    — You may not charge for the software. That means:
|        · Distribution may not be subject to any fee.
|        · Distribution may not be tied to purchasing a product or service.

There are many other points there, that alone enough to render it nonfree.  My favourite one:

|   — When distributing you must distribute the most recent version of Firefox and other Mozilla software.

[0] https://www.mozilla.org/en-US/foundation/trademarks/distribution-policy/

> Thus I think this isn't exactly correct framing, since firefox itself isn't nonfree?

As you see, it is.  You could build something very similar to Firefox from sources, of course, but it would not be Mozilla Firefox.  No much difference from Google Chrome in that regard.

But there is one difference, that is to credit of Google and that I would not underestimate — the free counterpart of their browser has a canonical name — Chromium.  While Mozillaʼs browser is anonymous and, unless are fine with adverting nonfree software, cannot be referred in any concise way; hence the whole zoo of rebrands: Icecat, Iceweasel, Fennec (F-Droid), Abrowser (Trisquel)...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2020-05-27  9:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 19:10 Vanilla Firefox recipe? Christopher Lemmer Webber
2020-05-11 20:31 ` Guillaume Le Vaillant
2020-05-12 19:23   ` Efraim Flashner
2020-05-24 13:54     ` Adonay Felipe Nogueira via
2020-05-25 20:17       ` Christopher Lemmer Webber
2020-05-26 20:27         ` Ludovic Courtès
2020-05-27  5:16         ` Dmitry Alexandrov [this message]
2020-05-27 17:31           ` Why Mozilla Firefox is nonfree? (was: Vanilla Firefox recipe?) Adonay Felipe Nogueira via
2020-05-28  5:11             ` X-Content-Filtered-By: Mailman/MimeDel 2.1.23 Dmitry Alexandrov
2020-05-27 14:26         ` Vanilla Firefox recipe? Tobias Geerinckx-Rice
2020-05-25 20:44       ` Tobias Geerinckx-Rice

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=eer63qkg.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@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.
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).