LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: bill-auger <bill-auger@peers.community>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Free software is not trusted software
Date: Wed, 16 Jan 2019 17:57:43 -0500	[thread overview]
Message-ID: <20190116175743.1b0d99c7@parabola> (raw)
In-Reply-To: <c067bfed-570b-9185-4935-305e8d29d0fe@lyberta.net>

On Wed, 16 Jan 2019 14:09:00 +0000 Lyberta wrote:
> https://lyberta.net/articles/tech/free_sw_untrusted.html

i think you are quite mistaken about JUCE - it does indeed contain
a phone "home feature"; which caused a huge fuss within the community,
which lasted for about 2 days, until everyone realized how harmless and
un-intrusive it actually was

that anti-feature is a restriction only on those who opt in for the
free tier of the commercial license; in order to write proprietary
software with JUCE without a licensing fee - so any JUCE-based program
with that feature enable is almost certainly not "free software"

but JUCE may also be taken as GPL, which naturally gives the developer
and all users the option to disable that feature (and any other
undesirable ones) - those features are fully disclosed and simple to
disable with a single #define

  #define JUCER_ENABLE_GPL_MODE 1

doing so, will disable the new anti-features by default in any program
you create with your copy of JUCE, including the one in question here:

  #define JUCE_REPORT_APP_USAGE 0

that is done in the same way and in the same file as where all JUCE
sub-features have been enabled/disabled all along, along with others
such as:

  #define JUCE_USE_FLAC 1
  #define JUCE_USE_OGGVORBIS 1

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

  parent reply	other threads:[~2019-01-16 22:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 14:09 Free software is not trusted software Lyberta
2019-01-16 17:00 ` Todd Weaver
2019-01-16 20:07   ` Caleb Herbert
2019-01-16 22:21     ` bill-auger
2019-01-16 22:57 ` bill-auger [this message]
2019-01-16 23:12   ` Leah Rowe
2019-01-17  1:01     ` bill-auger
2019-01-17 10:52     ` Thomas Harding
2019-02-25 20:44     ` Taiidan
2019-02-26  0:15       ` overthefalls
2019-01-17  3:44 ` J.B. Nicholson
2019-01-19 10:41   ` Nicolás Ortega Froysa
2019-01-19 14:34     ` Julian Daich
2019-01-20 18:01       ` Nicolás Ortega Froysa
2019-01-20 20:36         ` bill-auger
2019-01-20 22:54         ` Julian Daich
2019-01-21  3:02           ` bill-auger
2019-01-22 10:07             ` Nicolás Ortega Froysa
2019-01-23  3:48               ` bill-auger
2019-01-26 21:17             ` Julian Daich
2019-01-26 23:35               ` bill-auger
2019-01-27  1:07                 ` bill-auger
2019-01-27 19:51                   ` Julian Daich
2019-01-28  3:15                     ` bill-auger
2019-01-27 19:40                 ` Julian Daich
2019-02-17  5:34                   ` overthefalls
2019-01-21  8:05         ` Andrew Luke Nesbit
2019-01-21 22:45           ` bill-auger
2019-01-22  9:34             ` Nicolás Ortega Froysa
2019-01-19 22:01     ` bill-auger
2019-01-20 18:06       ` Nicolás Ortega Froysa
2019-01-19 22:37     ` al3xu5 / dotcommon
2019-01-20 17:09       ` Lyberta
2019-01-20 18:16       ` Nicolás Ortega Froysa
2019-01-23 19:51     ` Adonay Felipe Nogueira

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=20190116175743.1b0d99c7@parabola \
    --to=bill-auger@peers.community \
    --cc=libreplanet-discuss@libreplanet.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).