[LINK] web: The cookie is dead. Here's how Facebook, Google, and Apple are tracking you ...

[Stephen Loosley]

Ric writes,

> The announcement of the death of cookies is very premature ..


Yes, agreed Ric. Although an interesting and otherwise informative article (thanks Jan), in referring mainly to mobile phone net access, the author does seem rather carried away regarding his predicted death of cookies.

Cookies are indeed very much alive and well. 

On this point, can I strongly recommend that Linkers have a close look regards installing the EFF Organization browser add-on, the  "Privacy Badger". It's free, and amazing.

https://www.eff.org/privacybadger

In my experience, this add-on is absolutely GREAT. No problems at all, and it just blocks all cookies if you want.

For example, it tells you that the Sydney Morning Herald wants to set 24 cookies, with around half a dozen being 'tracking' cookies which it blocks. Well, bugger that. I set the Badger to block EVERY cookie. And so it does, with zero problems. If this setting sometimes (very occasionally) interrupts the functionality of any particular website, in five seconds one can simply just reduce some of the Badger blocking strengths (from red to yellow or green for a few of the cookies) and then everything works perfectly again. Otherwise the Badger locks this computer down extremely tight. Nothing via the browser utilization/session is allowed to be saved and to track browser use. My computer must look like a brand new machine browsing for the first time, because of the Badger, my flash/java settings and doing frequent/daily windows 'disk cleanups'.  For example ...

What is Privacy Badger?

Privacy Badger is a browser add-on that stops advertisers and other third-party trackers from secretly tracking where you go and what pages you look at on the web.  If an advertiser seems to be tracking you across multiple websites without your permission, Privacy Badger automatically blocks that advertiser from loading any more content in your browser.  To the advertiser, it's like you suddenly disappeared.

How is Privacy Badger different to Disconnect, Adblock Plus, Ghostery, and other blocking extensions?Privacy Badger was born out of our desire to be able to recommend a single extension that would automatically analyze and block any tracker or ad that violated the principle of user consent; which could function well without any settings, knowledge or configuration by the user; which is produced by an organization that is unambiguously working for its users rather than for advertisers; and which uses algorithmic methods to decide what is and isn't tracking.

Although we like Disconnect, Adblock Plus, Ghostery and similar products (in fact Privacy Badger is based on the ABP code!), none of them are exactly what we were looking for. In our testing, all of them required some custom configuration to block non-consensual trackers. Several of these extensions have business models that we weren't entirely comfortable with. And EFF hopes that by developing rigorous algorithmic and policy methods for detecting and preventing non-consensual tracking, we'll produce a codebase that could in fact be adopted by those other extensions, or by mainstream browsers, to give users maximal control over who does and doesn't get to know what they do online.

How does Privacy Badger work?

When you view a webpage, that page will often be made up of content from many different sources.  (For example, a news webpage might load the actual article from the news company, ads from an ad company, and the comments section from a different company that's been contracted out to provide that service.)  Privacy Badger keeps track of all of this.  If as you browse the web, the same source seems to be tracking your browser across different websites, then Privacy Badger springs into action, telling your browser not to load any more content from that source.  And when your browser stops loading content from a source, that source can no longer track you.  Voila!

At a more technical level, Privacy Badger keeps note of the "third party" domains that embed images, scripts and advertising in the pages you visit. If a third party server appears to be tracking you without permission, by using uniquely identifying cookies to collect a record of the pages you visit across multiple sites, Privacy Badger will automatically disallow content from that third party tracker. In some cases a third-party domain provides some important aspect of a page's functionality, such as embedded maps, images, or fonts. In those cases Privacy Badger will allow connections to the third party but will screen out its tracking cookies.

What is a third party tracker?

When you visit a webpage parts of the page may come from domains and servers other than the one you asked to visit. This is an essential feature of hypertext, but it has also come to be a serious privacy problem. On the modern Web, embedded images and code often use cookies and other methods to track your browsing habits — often to display advertisements. The domains that do this are called "third party trackers", and you can read more about how they work here.

What do the red, yellow and green sliders in the Privacy Badger menu mean?

The colors mean the following:

Green means there's a third party domain, but it hasn't yet been observed tracking you across multiple sites, so it might be unobjectionable. When you first install Privacy Badger every domain will be in this green state but as you browse, domains will quickly be classified as trackers.

Yellow means that the third party domain appears to be trying to track you, but it is on Privacy Badger's cookie-blocking "whitelist" of third party domains that, when analyzed, seemed to be necessary for Web functionality. In that case, Privacy Badger will load content from the domain but will try to screen out third party cookies and supercookies from it.

Red means that content from this third party tracker has been completely disallowed.Privacy Badger analyzes each third party's behavior over time, and picks what it thinks is the right setting for each domain, but you can adjust the sliders if you wish.

Why does Privacy Badger block ads?

Actually, nothing in the Privacy Badger code is specifically written to block ads. Rather, it focuses on disallowing any visible or invisible "third party" scripts or images that appear to be tracking you even though you specifically denied consent by sending a Do Not Track header. It just so happens that most (but not all) of these third party trackers are advertisements. When you see an ad, the ad sees you, and can track you. Privacy Badger is here to stop that.

Why doesn't Privacy Badger block all ads?

Because Privacy Badger is primarily a privacy tool, not an ad blocker. Our aim is not to block ads, but to prevent non-consensual invasions of people's privacy because we believe they are inherently objectionable. We also want to create incentives for advertising companies to do the right thing. Of course, if you really dislike ads, you can also install a traditional ad blocker.

What about tracking by the sites I actively visit, like NYTimes.com or Facebook.com?

The alpha release of Privacy Badger only protects you against tracking by third party sites. In the future we plan to add some privacy protections for "first party" sites that you actually visit.

We are doing things in this order because the most scandalous, intrusive and objectionable form of online tracking is that conducted by companies you've often never heard of and have no relationship with. First and foremost, Privacy Badger is there to enforce Do Not Track against these domains by providing the technical means to restrict access to their tracking scripts and images. The right policy for whether nytimes.com, facebook.com or google.com can track you when you visit that site – and the technical task of preventing it – is more complicated because often (though not always) tracking is interwoven with the features the site offers, and sometimes (though not always) users may understand that the price of an excellent free tool like Google's search engine is measured in privacy, not money.

Does Privacy Badger contain a "black list" of blocked sites?

No, unlike other blocking tools like AdBlock Plus, we have not made decisions about which sites to block, but rather about which behavior is objectionable. Domains will only be blocked or screened if the Privacy Badger code inside your browser actually observes the domain collecting unique identifiers after it was sent a Do Not Track message. Privacy Badger does contain a whitelist of some sites that are known to provide essential third party resources; those sites show up as yellow and have their cookies blocked rather than being blocked entirely. This is a compromise with practicality, and in the long term we hope to phase out the whitelist as these third parties begin to explicitly commit to respecting Do Not Track.

How was the cookie blocking whitelist created?

The initial list of domains that should be cookie blocked rather than blocked entirely was derived from a research project on classifying third party domains as trackers and non-trackers. We will make occasional adjustments to it as necessary. If you find domains that are under- or over-blocked, please file a bug on Github.
Does Privacy Badger prevent fingerprinting?

Currently, Privacy Badger does not prevent browser fingerprinting, of the sort we demonstrated with the Panopticlick project. But we will be adding fingerprinting countermeasures in a future update!

Does Privacy Badger consider every cookie to be a tracking cookie?

No. Privacy Badger analyzes the cookies from each site; unique cookies that contain tracking IDs are disallowed, while "low entropy" cookies that perform other functions are allowed. For instance a cookie like LANG=fr that encodes the user's language preference, or a cookie that preserves a very small amount of information about ads the user has been shown, would be allowed provided that individual or small groups of users' reading habits could not be collected with them. We have a very rough implementation of this; pull requests are welcome.

Does Privacy Badger account for a cookie that was used to track me even if I deleted it?

Yes.  Privacy Badger keeps track of cookies that could be used to track you and where they came from, even if you frequently clear your browser's cookies.  (But note that in Firefox, Privacy Badger will be automatically deactivated when you enter Private Browsing Mode, and reactivated when you return to normal browsing.  The same behavior occurs if you set the "Never Remember History" option.)

Why does Privacy Badger's icon sometimes not show up in Firefox?

Firefox add-ons need special permission to be active when a user is in Private Browsing mode or has chosen "Never remember history" in their privacy settings. Privacy Badger Alpha does not request this permission because its blocking algorithm uses your browsing history to determine what to block. Therefore, if you have one of these privacy settings enabled Privacy Badger will be inactive. (A new version that fixes this will be released soon!)

Will you be supporting any other browsers besides Chrome / Firefox?

In the near future we hope to release Privacy Badger for Opera and Firefox Mobile.  Unfortunately at the moment we cannot support Safari or Internet Explorer, since current versions of those browsers appear to be incompatible with how Privacy Badger works at a technical level.  (With that said, if you have an idea for how to make Privacy Badger work for Safari or IE, please let us know!)

Can I download Privacy Badger outside of the Chrome Web Store?

You can! If you are using an alternative Chromium based browser such as Chromium ports Iron, Comodo Dragon, or Maxthon you can get the latest version of the addon directly from this link: 

https://www.eff.org/files/privacy_badger-chrome.crx

I am an online advertising / tracking company. How do I stop Privacy Badger from blocking me?One way is to stop tracking third party users who have turned on the Do Not Track header (i.e., stop collecting cookies, supercookies or fingerprints from them). That will work for new Privacy Badger installs.

If copies of Privacy Badger have already blocked your domain, you can unblock yourself by promising to respect the Do Not Track header in a way that conforms with the user's privacy policy. You can do that by posting a specific compliant DNT policy to the URL https://example.com/.well-known/dnt-policy.txt, where "example.com" is all of your DNT-compliant domains. Note that the domain must support HTTPS, to protect against tampering by network attackers. The path contains ".well-known" per RFC 5785.

The Privacy Badger alpha release currently checks for this specific verbatim policy document, though in the future Privacy Badger may allow content from sites that post different versions of a compliant DNT Policy, and that there may be ways for users to specify their own acceptable DNT policies if they wish to.

What is the Privacy Badger license? Where is the Privacy Badger source code?

Privacy Badger is GPLv3 code, based on a modified version of the AdBlock Plus engine. You can find the Privacy Badger source trees on Github. There is also a development mailing list. Privacy Badger is governed by EFF's Privacy Policy for Software.

I found a bug! What do I do now?

First, please make sure the bug hasn't already been reported by checking the current bug list for Firefox or for Chrome.  If the bug hasn't yet been reported you can report the bug here for Privacy Badger for Firefox or here for Privacy Badger for Chrome. If you don't have a GitHub account, then you can login using the anonymous one: "cypherpunk"/"cypherpunk".

How can I support Privacy Badger?

Thanks for asking! Individual donations make up about half of EFF's support, which gives us the freedom to work on user-focused projects. If you want to support the development of Privacy Badger and other projects like it, helping build a more secure Internet ecosystem, you can throw us a few dollars here. Thank you.

How does Privacy Badger handle social media widgets?

Social media widgets (such as the Facebook Like button, Twitter Tweet button, or Google +1 button) often track your reading habits. Even if you don't click them, the social media companies often see exactly which pages you're seeing the widget on. As a result, the Privacy Badger alpha release would often block these widgets outright. The Privacy Badger beta includes a new feature imported from the ShareMeNot project which is able to replace the widgets with a stand-in version, so that you can still see and click them. You will not be tracked by these replacements unless you explicitly choose to click them. Privacy Badger currently knows how to replace the following widgets if they are observed tracking you: AddThis, Facebook, Google, LinkedIn, Pinterest, Stumbleupon, and Twitter. (The source code for these replacements is here; pull requests are welcome) Note that Privacy Badger will not replace social media widgets unless it has blocked the associated tracker. If you're seeing real social media widgets, it generally means that Privacy Badger hasn't detected tracking from that variant of the widget, or that the site you're looking at has implemented its own version of the widget. To avoid confusion, the replacement widgets are marked with the Privacy Badger badge next to the button. To interact with a replacement widget, simply click on it. Depending on the widget, Privacy Badger will either send you directly to the appropriate sharing page (for example, to post a tweet) or it will enable and load the real social widget (for example, the Facebook Like button, with personalized information about how many of your friends have "liked" the page). In the second case, you will still need to interact with the real widget to "like" or share the page.