(Spoiler: The patients, unfortunately, developed a tolerance for the treatment within a few months.)
1,433 karma · joined January 27, 2011
(Spoiler: The patients, unfortunately, developed a tolerance for the treatment within a few months.)
1. http://www.theverge.com/2014/2/24/5441642/blackphone-silent-...
If you install Disconnect first on Firefox then install other filtering add-ons (ABP et al.), you should get faster overall performance. The reason is Disconnect filters faster, so requests that Disconnect blocks won't have to be processed by your other add-ons. All other requests will still be processed by them.
Disconnect also does some fancy visualizations, if you're into that sort of thing: http://youtu.be/Lvem1Z66C7Q?t=40s.
Yes! You now know how Disconnect works - Disconnect's filter list is based on weekly crawl data that identifies what the most prevalent third parties on the web are.
> `static-serve.appspot.com` is no different than `ajax.googleapis.com` (you didn't list this one, why?)
You think that URL might belong to Google, which I already called an exception 2x?
> I will note that you completely disregarded the other results which are even more embarrassing to explain (like `simplereach.cc`: "SimpleReach tracks every social action on each piece of published content to deliver detailed insights and clear metrics around social behavior.")
I examined and debunked the entirety of the first example on your page, so I'm not inclined to waste any more time on your so-called "science".
The first thing I tried when I wrote Disconnect was to block every third-party domain. Within an hour, I realized that I broke the whole web. So I built a crawler to identify and categorize the most prevalent third-party services instead. The domains you list under Disconnect would all be categorized as content by our crawler - resources that most people would consider pages broken without and that Disconnect doesn't block by default.
> And how exactly is it trickery if users have to opt-in to the program and they're told what the program does?
Ghostery seems to rely on vague messaging (last I looked, they don't actually say anywhere in their extension that they sell the data you share to ad co's and data brokers) and UX "optimization" (what quesera dubbed the "reconfigure-on-update dance", for example) to get less attentive users to leave blocking off and to send data - as the numbers show.
* Disconnect has more than a million active users and Ghostery has more than two million.
* Disconnect is also as public as ABP: https://github.com/disconnectme/disconnect.
* Chrome, Safari, and Opera give precedence to the newest extension - if that extension blocks a request, older extensions don't see the request.
* Firefox gives precedence to the oldest add-on.
> So you offer a very useful product, for free, and make money off of the people who fail to configure it so that it performs the only service they would ever purposely download it for.
I gave some numbers above that show, in practice, just how many users are in one of these unexpected configurations:
> Ghostery's game seems to be tricking users into sending their data to Evidon. Going off the company's own numbers, something like 45% of Ghostery users send Evidon data (by comparison, only 2% of Firefox users share data through Telemetry).
The unencrypted list is at https://github.com/disconnectme/disconnect/blob/b27abbf033c6....
And formatted as JSON at https://disconnect.me/services-plaintext.json.
The encrypted list is also trivial to decrypt with the SJCL code in https://github.com/disconnectme/disconnect/blob/master/firef....
#2 first: Code to block everything marked as content with one click was either just checked in or is about to be.
For #1: Disconnect groups tracking requests by company. If you want to see all the Google services that Disconnect filters, you could look through the filter list (services are grouped by category and company here, so start at lines 33, 1,882, and 2,326): https://github.com/disconnectme/disconnect/blob/b27abbf033c6....
> Given the results, I am quite surprise you would say "look to be first parties serving content for the page".
I believe every single domain name you listed (except the Google and Twitter domains, like I said) is a domain owned by or a CDN used by the Guardian or hosts an app run by the Guardian - prove me wrong:
> facebook-web-clients.appspot.com
> guardian-notifications.appspot.com
> related-info-hrd.appspot.com
> static-serve.appspot.com
> cdnjs.cloudflare.com
> discussion.guardianapis.com
> s.ophan.co.uk
I work on Disconnect. I don't understand why any hacker would still put Ghostery on their machine:
* Ghostery is run by former ad execs (7/9ths of their executive team): http://www.evidon.com/our-team
* They make their money (I've heard tens of millions of dollars per year) selling user data to ad co's and data brokers: http://www.evidon.com/#block-views-from_our_partners-block
Our extension (https://addons.opera.com/en/extensions/details/disconnect/) uses the minified versions of seven libraries, which are about half the size of the unminified versions. Why not give users a better experience by shaving a few seconds off the install time?
These seem like nice, trustworthy sources.
We'll just go ahead and let these advertisers spy on you instead.
(I'm one of the devs.)
1. Unlike that other "privacy" cough extension, Disconnect doesn't send any data (user or otherwise) to Disconnect servers. In other words, Disconnect doesn't output user data that can be intercepted by a MITM attack. Disconnect does grab a config file on startup (https://disconnect.me/help#syncing), but unlike in the Amazon case, the file is both transferred over HTTPS and encrypted (with the Stanford Javascript Crypto Library). Also unlike in the Amazon case, the file has a limited functional scope (which third-party sites to block) so is less susceptible to being rewritten in an abusive way.
2. One of our other Chrome extensions, Collusion for Chrome, will actually show you requests that are coming from other extensions. The more technical approach, which isn't that hard and I'd like to see more people try, is to run a packet sniffer (recommended: http://www.wireshark.org/) or proxy server (recommended: http://www.charlesproxy.com/).