W3C home > Mailing lists > Public > public-privacy@w3.org > July to September 2015

RE: [privacybadgerchrome] tagsrvcs.com (#431)

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Wed, 15 Jul 2015 12:15:15 +0100
To: "'EFForg/privacybadgerchrome'" <reply+00404222a2952b06047c84df139a25ebc50acdc6596742d592cf0000000111bd2a9892a16>
Cc: "'public-privacy \(W3C mailing list\)'" <public-privacy@w3.org>
Message-ID: <081501d0beef$86ae3790$940aa6b0$@baycloud.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for your fast response Dan. The previous code has illuminated important privacy risks with this otherwise useful API.

Mike



From: dakami [mailto:notifications@github.com]
Sent: 14 July 2015 20:53
To: EFForg/privacybadgerchrome
Cc: michael-oneill
Subject: Re: [privacybadgerchrome] tagsrvcs.com (#431)

Indeed, I killed the STUN queries.

- --Dan

On Tue, Jul 14, 2015 at 12:19 PM, michael-oneill <notifications@github.com>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Jacob,
>
> That was quick.
>
> As of about an hour ago there are no longer STUN accesses from nytimes.com,
> washingtonpst.com, ft.com and cnbc.com. In case it is a geolocation
> specific thing what are you seeing? I am in UK
>
> Mike
>
> From: Jacob Soo [mailto:notifications@github.com]
> Sent: 13 July 2015 15:55
> To: EFForg/privacybadgerchrome
> Cc: michael-oneill
> Subject: Re: [privacybadgerchrome] tagsrvcs.com (#431)
>
> Seems like mostly American website(s) are using that.
> http://www.vanityfair.com/ and http://www.wired.com/ are using the
> same3rd party tracking code.
> Apparently Eric Lawrence found an interesting thing if the content is
> blocked in IE.
>
> http://textslashplain.com/2015/06/22/content-blocking-unintended-consequences/
> —
> Reply to this email directly or view it on GitHub./
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using gpg4o v3.4.103.5490 - http://www.gpg4o.com/
> Charset: utf-8
>
> iQEcBAEBAgAGBQJVpWCpAAoJEHMxUy4uXm2JNVUIANavZ8w24KpLpKAP1Aopacw7
> mQnDyaFuCN/zzZWBPxLuDa0mV8x9b463QiLBc59hqFBtsCuhUhTJ0btxpVaDcf9g
> 1i5mRv2HMWoIsdGjVJX16+3KlE2vv+PQ+jSMIhVVcMYXqiQ7KdmDBVb8CBhStOPy
> MOjTbMyZx2WGK3DSvj77X74NkKv+1uR54Y3bMPX+yc3ztX5cb/deqorUbyt3b7/U
> KfW1QgwsTvjMdooaq/QFHwAW9XGUOXA1GcFuufZL1AmfCFAUiq8sF2O7VAce+Wem
> 7jS2HB8Ym0h7G9+9XrZDfRSSBHDQaPnT5tG2m1jZfvD3q8WjH5sAXZqpx5noOZc=
> =J6Ct
> -----END PGP SIGNATURE-----
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/EFForg/privacybadgerchrome/issues/431#issuecomment-121346937>
> .
>

—
Reply to this email directly or view it on GitHub./
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using gpg4o v3.4.103.5490 - http://www.gpg4o.com/
Charset: utf-8

iQEcBAEBAgAGBQJVpkDCAAoJEHMxUy4uXm2J1JsH/j9J77JybByee4jPLZySdlTN
OIlqUU+V95XrzSShXtuLL682oF0xTYdY2n56lMMQw4LQ66FXIdjE10Ptj9yE8XUU
pVdhDpSPub2O68azb9KgJGwWCHqbQRTBc+Gc6J+bCgjVq3HNPnTvaAzQXRFwm/rf
HrTgCKFfjFcKdbWyRBJomA93qouQyr3y7BMXclzOt4rJXRNcoDHMy/Mpef12PLtU
ToIy3BPB9Wgnz8SDeJxGcsqiPkj4JydaF8ik7hYcMjxamBC13YIfQxuJsz2bzSwz
GIFKOl2jHCcwAzkP+De3Z5VYblHmi4LnDqnwkUd7mIOQodQ9xwzhsysf/qlr1sE=
=j59j
-----END PGP SIGNATURE-----



image002.jpg
(image/jpeg attachment: image002.jpg)

Received on Wednesday, 15 July 2015 11:15:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 July 2015 11:15:50 UTC