unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Leo Famulari <leo@famulari.name>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Free software telemetry and the Guix System
Date: Sat, 15 May 2021 12:01:05 +0200	[thread overview]
Message-ID: <20210515100105.GA5410@LionPure> (raw)
In-Reply-To: <YJ7jCQBwlTd3mfKl@jasmine.lan>

Hi all,

On +2021-05-14 16:52:25 -0400, Leo Famulari wrote:
> On Fri, May 14, 2021 at 06:55:34PM +0000, Cook, Malcolm wrote:
> > > If these claims are true, then I think this is quite satisfactory for
> > > our purposes. I wouldn't even object to enabling the telemetry code via
> > > the CMake build-time option, as long as it's "opt-in", i.e. that each
> > > user must explicitly enable it, and only after being made aware of the
> > > consequences of doing so.
> > > 
> > > What do you think?
> > 
> > My 2 cents:  I think the Audacity model is exemplary and your interpretation is spot on.  I personally want the option of enabling such telemetry, as it may well serve my needs and may also give the developer valuable usage and/or crash info which is the least I can provide in return for such a great FOSS app as Audacity.
> 
> +1
> 

My 2 cents:  :)

I like options, but I would feel more secure if it were implemented in a separate,
dynamically linked when opted-in,
    some-implementation.so
which I could get the kernel to prevent access to, e.g. by
    # chmod 400 some-implementation.so

-- 
Regards,
Bengt Richter


  reply	other threads:[~2021-05-15 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 20:03 Free software telemetry and the Guix System Bone Baboon
2021-05-14 18:12 ` Mark H Weaver
2021-05-14 18:55   ` Cook, Malcolm
2021-05-14 20:52     ` Leo Famulari
2021-05-15 10:01       ` Bengt Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-15  7:48 mjbecze

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=20210515100105.GA5410@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).