unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Gathering data on user preferences
Date: Tue, 7 Sep 2021 10:11:43 +0200	[thread overview]
Message-ID: <20210907081143.GD4097@tuxteam.de> (raw)
In-Reply-To: <87czpklsng.fsf@gmail.com>

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

On Tue, Sep 07, 2021 at 05:54:09PM +1000, Tim Cross wrote:

[...]

> I was thinking of only getting data on 'non-sensitive' variables

Of course, I didn't assume otherwise. What I was aiming at is that
classifying /which/ variables can be considered 'non-sensitive' is
already some non-negligible work, that's all (and leaving the
decision to each single user doesn't seem fair).

>                                                                and
> only aggregate data would be available (i.e. make sure it is not
> possible to say person x submitted values a, b and c).

Of course. Correlations between values might be of interest.

> [...] The possible downside is that this would be
> open to 'gaming' the system, but I'm not sure we need to worry about
> that too much - there is little reward in doing so.

This is why I pointed to Debian's popcon: they just live with that,
and that doesn't seem to be a problem.

> The system would definitely be 'opt in' and the user would be shown
> exactly what is going to be sent (and provided with the ability to
> remove anything they are not comfortable with). 

Also, see popcon.

As a small nit: why JSON and not S-expressions? We're lispies, after
all ;-)

But the latter are just details. I guess who gets to implement gets
to choose. That might be an incentive ;-P

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-09-07  8:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  3:22 Gathering data on user preferences Tim Cross
2021-09-07  4:25 ` Howard Melman
2021-09-07  6:28   ` Eli Zaretskii
2021-09-07 13:22     ` Howard Melman
2021-09-08 13:37       ` Philip Kaludercic
2021-09-07  6:42 ` tomas
2021-09-07  7:54   ` Tim Cross
2021-09-07  8:11     ` tomas [this message]
2021-09-07  9:09       ` Tim Cross
2021-09-07 12:32         ` Arthur Miller
2021-09-07 13:48           ` Tim Cross
2021-09-07 14:52             ` Arthur Miller
2021-09-07 16:53               ` Tim Cross
2021-09-07 18:46                 ` Arthur Miller
2021-09-07 23:14                   ` Tim Cross
2021-09-08  7:52   ` Philip Kaludercic
2021-09-08  8:14     ` Tim Cross
2021-09-08 10:41       ` Daniel Fleischer
2021-09-08 13:02         ` Tim Cross
2021-09-08 12:52       ` Philip Kaludercic
2021-09-08 13:00         ` Tim Cross

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20210907081143.GD4097@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=theophilusx@gmail.com \
    /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/emacs.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).