unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>,
	Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: Telemetry on by default kitty
Date: Tue, 15 Jun 2021 19:07:25 -0400	[thread overview]
Message-ID: <878s3an2uv.fsf@netris.org> (raw)
In-Reply-To: <YMZWrBExKQSfoWNa@jasmine.lan>

Hi Leo,

Leo Famulari <leo@famulari.name> writes:
> I feel that, ultimately, we already trust most software authors
> implicitly and totally, because we are not auditing their programs.

Agreed.

> So, I am personally happy to enable the telemetry for most software I
> use — especially if it is free software and especially for software
> that deals with the network.

That's your personal decision, and I agree that telemetry functionality
should be permissible in Guix, as long as it's opt-in.

> I don't personally see the point of treating telemetry as a special
> case in terms of trust or consent.

One problem is that telemetry involves trusting more than just the
developer.  Telemetry also reveals information to the user's internet
service provider, the network operators between user and the server, the
company that controls the hardware that the server runs on, and any
intelligence agencies or other hostile actors that have infiltrated
those networks or servers.  Moreover, if the server keeps logs,
governments may coerce the developer into surrendering those logs.

Therefore, when a program generates unsolicited and unexpected network
traffic -- and I certainly do *not* expect a terminal program to
generate network traffic -- it is effectively leaking some of your
private information to all of those other actors.  That, in itself, is
arguably a breach of trust, regardless of the developer's presumably
good intentions.

I understand that many people have given up on protecting their privacy,
or simply don't care.  Kitty's developer seems to be of that mindset.

However, I strongly believe that each Guix user should be given the
opportunity to make that decision for themselves, i.e. that telemetry,
auto-update checks, and more generally unsolicited network traffic
should be disabled until the user has given informed consent.

What do other people think?

      Regards,
        Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.


  parent reply	other threads:[~2021-06-15 23:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12 20:18 Telemetry on by default kitty Bone Baboon
2021-06-12 20:35 ` Tobias Geerinckx-Rice
2021-06-12 21:28   ` Bone Baboon
2021-06-12 21:44     ` Tobias Geerinckx-Rice
2021-06-12 23:12       ` Leo Prikler
2021-06-12 23:14         ` Leo Prikler
2021-06-13  1:32         ` Mark H Weaver
2021-06-13 14:16           ` Tobias Geerinckx-Rice
2021-06-13  2:03         ` Bone Baboon
2021-06-13  9:32           ` Leo Prikler
2021-06-13 17:57             ` Leo Famulari
2021-06-13 18:35               ` Leo Prikler
2021-06-13 19:04                 ` Leo Famulari
2021-06-13 23:54                   ` Ryan Prior
2021-06-14  6:53                     ` Leo Prikler
2021-06-14 21:15                       ` Ludovic Courtès
2021-06-15 17:24                   ` Giovanni Biscuolo
2021-06-15 21:39                     ` Leo Prikler
2021-06-16 16:21                       ` Leo Famulari
2021-06-16 17:32                         ` Mark H Weaver
2021-06-16 17:32                         ` my apoligies (was Re: Telemetry on by default kitty) Giovanni Biscuolo
2021-06-16 18:27                           ` Leo Prikler
2021-06-16 22:54                           ` Leo Famulari
2021-06-20 15:50                     ` Telemetry on by default kitty Ludovic Courtès
2021-06-15 23:07                   ` Mark H Weaver [this message]
2021-06-16  5:28                     ` Jack Hill
2021-07-06 12:52         ` Bone Baboon

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=878s3an2uv.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --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).