Re: Never send user email address in HTTP requests

[Eli Zaretskii <eliz@gnu.org>]

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Sun, 17 Dec 2023 21:05:00 +0700
> Cc: Stefan Kangas <stefankangas@gmail.com>, rms@gnu.org, philipk@posteo.net, 
>  akib@disroot.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca
> 
> On Sun, 17 Dec 2023 at 19:36, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > Sorry, but I disagree.  Emacs should not second-guess the users, and
> > should certainly NOT force them into what we consider to be the secure
> > environment.  It is okay to behave securely by default, but if someone
> > wants to be insecure, for whatever reasons, we should let them have
> > the old, insecure behavior.  Certainly when we first change the
> > default, since there's a possibility that something will break for
> > someone due to this change, and we need to let users have a fire
> > escape in those cases, until we get our act together in the next
> > release.
> 
> The header in question, From, is governed by RFC 9110 § 10.1.2[0], which says:

Thanks, but this isn't relevant to the issue at hand.

> It is good that the default value of ‘url-privacy-level’ is (email),
> preventing the leak by default, but there is no reason to make it
> possible to configure url.el to leak it with every request made from
> Emacs. If you’re running a spider and also just browsing the Web with
> EWW, you probably only want requests from your spider to be attributed
> to you as the spider maintainer.

I remain convinced that we should allow users who actively want that
to make their Emacs behave against any RFCs, when Emacs has been
behaving like that for many years until now.