unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Tomas Nordin <tomasn@posteo.net>
Cc: help-gnu-emacs@gnu.org, emacs-w3m@namazu.org,
	Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: [emacs-w3m:13607] Re: Browser Fingerprinting
Date: Sat, 18 Apr 2020 21:26:42 -0400	[thread overview]
Message-ID: <20200419012642.lebvc5pofa23ppug@E15-2016.optimum.net> (raw)
In-Reply-To: <87blnpnlur.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>

On 2020-04-18 12:12, Tomas Nordin wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
> > That leaves us with the matter of the HTTP_ACCEPT Headers.
> > ...
>
> Different browsers (mis)use this header string differently [1]. The
> string lists mime types in a certain order with some optional ratings
> for each. If an un-common browser has this string different from common
> browsers it adds uniqueness.
>
> [1] https://www.newmediacampaigns.com/blog/browser-rest-http-accept-headers

Good to know, Thanks. If you have any test or comparison data of
how w3m/emacs-w3m actually operates versus common browsers, please share.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



  reply	other threads:[~2020-04-19  1:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15  5:44 Browser Fingerprinting Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-15 19:19 ` Tomas Nordin
2020-04-17  1:51   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17  7:46     ` Tomas Nordin
2020-04-17  2:55   ` [emacs-w3m:13608] " Boruch Baum
2020-04-17  3:33     ` [emacs-w3m:13609] " Emanuel Berg
2020-04-17  8:15     ` [emacs-w3m:13607] " Tomas Nordin
2020-04-17  8:57       ` [emacs-w3m:13611] " Boruch Baum
2020-04-17  9:35         ` [emacs-w3m:13607] " tomas
2020-04-17 19:17           ` Vladimir Sedach
2020-04-17 21:08             ` Vladimir Sedach
2020-04-18  1:46               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17 21:50           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-18  6:56             ` tomas
2020-04-18 10:12         ` Tomas Nordin
2020-04-19  1:26           ` Boruch Baum [this message]
2020-04-19  3:16           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-17  8:17     ` tomas
2020-04-17 19:31     ` Vladimir Sedach
2020-04-19  1:21       ` Boruch Baum

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=20200419012642.lebvc5pofa23ppug@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=emacs-w3m@namazu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    --cc=tomasn@posteo.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.
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).