Wouldn't this expose you to tracking by Facebook and Twitter? I would think people are more interested in blocking third-party tracking than first-party.
Thanks for the detailed explanation either way!
No advertiser or site looking to cash in on ads would abuse that.
The same goes for the SuperCookie; everyone knows the technology exists, but it's only the rotten apples in the industry ruining it for everyone else by actually making use of it. I got asked whether we would support this a few times, but it was always asked by the most shadiest of our customers, and a simple "we want to listen to the visitor's intent" sufficed.
The only real risk I see for online privacy is that this sort of stuff will happen en-masse and there will be a powerful lobby to illegalize this behaviour.
I wonder if a solution would be to tie third party cookies to the parent page. So that by default a Facebook cookie on a Guardian page could only be retrieved when the user is on the Guardian website. You could then have options within ther browser to explicitly allow cross domain cookies if the user wants (and send the actual Facebook domain cookie).
We actually took that approach to be compliant with the EU's cookie law; if a visitor rejected third party cookies, we fell back to first party cookies.
I had collated this so far to mostly un-break the site -- for viewing at least:
www.theguardian.com guardianapps.co.uk * noop
www.theguardian.com guim.co.uk * noop
www.theguardian.com theguardian.tv * noop
Whenever I un-break myself a site, I add the proper rules in there: https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-de...There were 16 3rd-party root domains I found were not needed [1]. Probably fonts.googleapis.com would make the site looks better, but it's up to users whether they want to let Google know they have been visiting what article on the Guardian.
[1] adnxs.com criteo.com doubleclick.net fonts.googleapis.com google.com googleadservices.com googlesyndication.com googletagservices.com gstatic.com imrworldwide.com krxd.net mathtag.com moatads.com ophan.co.uk outbrain.com revsci.net scorecardresearch.com
Sounds like RFC 3514, only negated.
hits.theguardian.com points to our Omniture implementation, which is the main tracking suite used for macro-level reporting (like when we say we have X unique monthly browsers, or whatever). So if you want to be invisible to that, leave it blocked.
ophan.theguardian.com points to our own analytics tool, Ophan, which does things like tracks whether you "read" the article. It's for journalists to work out if people like their stuff. All the views of the data are aggregated, but if an analyst really wanted to they could go write some SQL to look at the behavior of individual cookies. So if you want to be invisible to that, leave it blocked. A quick Google [0] will turn up lots more about Ophan and how it works.
Our only calls out to Facebook and Twitter are to retrieve share counts for the current URL (besides articles with embedded tweets, for now). These are probably relatively safe to unblock, but if that information doesn't interest you they're equally safe to block.
api.nextgen.guardianapps.co.uk is handling most Guardian stuff that gets ajaxed onto the page, like suggestions for what to read next. It's pretty harmless and required for a bunch of functionality. All the guim stuff is obviously just static assets.
It would be cute if there was some way of us hinting to the plugin which domains were needed to not break the site, though likely impractical in the real world.
[0] https://www.google.co.uk/search?q=ophan%20guardian