all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, guix-devel@gnu.org
Subject: Re: Telemetry on by default kitty
Date: Sat, 12 Jun 2021 22:03:15 -0400	[thread overview]
Message-ID: <877diy7c7w.fsf@disroot.org> (raw)
In-Reply-To: <83e3ea6de4daa14a81c826d9200941719abe2f82.camel@student.tugraz.at>

Leo Prikler writes:
> Am Samstag, den 12.06.2021, 23:44 +0200 schrieb Tobias Geerinckx-Rice:
>> Bone Baboon 写道:
>> > Should the patch be to remove the kitty package?
>> 
>> No.  The telemetry.

While I appreciate the invitation to write a patch for kitty's telemetry
I am not going to write that patch.  My rational is explained below.

> If I read terminals.scm, we already disable the telemetry in kitty:
>
>> (invoke "python3" "setup.py" "linux-package"
>>         ;; Do not phone home.
>>         "--update-check-interval=0"
>
> @Bone: Did you notice any other telemetry during your further code
> review (or are you still in the process of reviewing the code)?  If
> not, please try to cross-check Guix sources to see whether we already
> disable telemetry, so as to not cause unwarranted panic :)

It appears problematic to patch kitty's telemetry for several reasons.

kitt's lead developer did not explaining kitty's telemetry when asked
for further information.  It is not clear if kitty performs other kinds
of telemetry as well.  It would seem that the only way to make sure that
all undesirable telemetry is removed would be a full review of kitty's
source code.

kitty's lead developer thinks that the telemetry in kitty is
acceptable.  So there would need to be an ongoing review of commits to
the kitty source code to ensure that undesirable telemetry is not added
in the future.

I have never been a kitty user and seeing the position kitty's lead
developer holds on telemetry I will not be a kitty user in the future.
I will not be reviewing the kitty source code or future commits to the
kitty source code.


  parent reply	other threads:[~2021-06-13  2:05 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877diy7c7w.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.