From: Philip Kaludercic <philipk@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: rms@gnu.org, yoni@rabkins.net, emacs-devel@gnu.org
Subject: Re: Distribution statistics for ELPA and EMMS
Date: Tue, 19 Sep 2023 16:38:08 +0000 [thread overview]
Message-ID: <87o7hy9kzz.fsf@posteo.net> (raw)
In-Reply-To: <4da4d2f6-2197-3727-674e-034c353207c5@alphapapa.net> (Adam Porter's message of "Tue, 19 Sep 2023 09:49:41 -0500")
Adam Porter <adam@alphapapa.net> writes:
> [I just noticed this message from a few months ago.]
>
> On 7/16/23 21:25, Richard Stallman wrote:
>> [[[ To any NSA and FBI agents reading my email: please consider ]]]
>> [[[ whether defending the US Constitution against all enemies, ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>> We could have two options for downloading, one which is "for a real
>> user" and one which is "for periodic testing".
>> The only difference would be that the former increments the user
>> download count and the latter does not.
>
> I like this idea, but it seems like it would be hard to enforce. It
> could even go the other way, i.e. have Emacs send a query string or
> header when installing a package manually, which could be logged and
> used to filter the download logs later. But even that might be harder
> than it seems, e.g. if I call a command like:
>
> emacs --eval "(package-install FOO)"
>
> ...to non-interactively install a package into a local directory for
> testing, how far, and in how many places, would some kind of flag need
> to be propagated to end up in the server's logs?
There is an inherent unreliability in these kinds of statistics that has
to be accepted. The question is therefore are issues like these
significant or would they skew the results. This has to be considered
under a false-positive and a false-negative approach, depending on what
we want to measure. If it is all about dopamine-boosting, I think a
false-positive approach would be better ;^)
next prev parent reply other threads:[~2023-09-19 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 20:54 Distribution statistics for ELPA and EMMS Yoni Rabkin
2023-07-13 23:16 ` Eduardo Ochs
2023-07-14 7:03 ` Philip Kaludercic
2023-07-14 14:02 ` Yoni Rabkin
2023-07-14 19:45 ` Adam Porter
2023-07-17 2:25 ` Richard Stallman
2023-09-19 14:49 ` Adam Porter
2023-09-19 16:38 ` Philip Kaludercic [this message]
2023-09-19 19:00 ` Akib Azmain Turja
2023-09-19 19:13 ` Emanuel Berg
2023-09-19 19:42 ` Yoni Rabkin
2023-09-19 22:06 ` Philip Kaludercic
2023-09-07 16:46 ` Stefan Kangas
2023-09-07 17:10 ` Yoni Rabkin
2023-09-07 21:35 ` Akib Azmain Turja
2023-09-07 22:07 ` Stefan Kangas
2023-09-07 23:09 ` Lynn Winebarger
2023-09-08 7:51 ` Philip Kaludercic
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=87o7hy9kzz.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=yoni@rabkins.net \
/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).