Disconnect: a browser extension that blocks third-party tracking in real time

The extension basically blocks cookies and requests made by third parties as the page loads, but it's unique in that it actually shows you how many are blocked, in real time and also prevents "personalization" tracking by search engines. You can choose to unblock certain collectors by clicking the Disconnect badge at any time. It's not an adblock, it just blocks third-party data-collection, and though the list of blocked companies is relatively short right now, Kennish plans to add more over time.
While the effects of the extension will be mostly transparent, users might notice that certain sites (ahem, TechCrunch and Mashable) will load much faster. Facebook and Digg widgets will not be able to send any information about you or your system back to company servers, either. Another use for Disconnect is to sanitize your own footprint from Google Search. When active, your searches will be completely sterile and depersonalized, but you can still use your regular Google services like Gmail without issues. Users who like their searches personalized simply need to unblock Google in the Disconnect badge while on the Search page.
A note to international readers: At this point, the search depersonalization function only works for Google.com, so .co.uk and .de users will have to wait a bit longer if this is what they're looking for.
Unfortunately, things like bookmarklets don't get off so easy. While the extension doesn't affect my being logged into Gmail,
The extension is currently only available for Chrome-based browsers, but versions for Safari and Firefox are both expected soon. The really funny part about all this is that Kennish made it a point to mention Rockmelt alongside Chrome on the extension's homepage. Maybe it's just me, but there's something inherently ironic about installing an extension called Disconnect on a "social browser."













Comments
14
Subscribe to commentsJoshDec 13th 2010 8:57PM
how similar is this to the FF ext. Ghostery?
Matthew RogersDec 13th 2010 9:04PM
@Josh From my understanding it's quite similar in some ways (blocking third-party data-collection) while different in that it doesn't do search depersonalization. It's also a much bigger extension, so as far as I know, it technically does _more_ than Disconnect, but it isn't meant to be used as a simple 'once-on' sort of tool.
JoshDec 13th 2010 9:24PM
@Matthew Rogers gotcha, thanks.
Dan McQuadeDec 13th 2010 11:05PM
Interesting
BugMeNotDec 14th 2010 12:15AM
Matt, do you think if we use Ghostery or something like this, that we still should tick Chrome's "block all third party cookies without exception" option? I ask this because of late, I've noticed that this not only might be redundant, but might also cripple a lot of sites' functionality. And also Chrome isn't really that flexible with 3rd party cookies at all.
Matthew RogersDec 14th 2010 12:25AM
@BugMeNot I've made it a point never to use the "block all third-party cookies" option because it does tend to break so many sites, but I know plenty of other people who do use the function and survive just fine online... I guess it comes down to whether or not you yourself think that it's overkill :)
Personally, I like the method of using extensions where necessary/available, tools like adblock and proxify/glimmerblocker, and just allowing the browser itself to accept cookies as they come. The only catch is that it's obviously less secure to browse that way, but I tend to steer clear of potential dangers. Maybe it would be different on a shared system, in which case I might think twice about leaving the option unticked (since wouldn't be in complete control over which sites my system is being exposed).
It's a bit like the option in Chrome that stops any and all plug-in media from playing until you click on it -- it's a good tool to have built into the browser, but I still prefer to just use Flashblock and keep things a bit looser than they could be.
EuroSceptiCDec 14th 2010 12:20AM
Seems nice Extension but but doesn't blocking counters. Only few Third-Parties collectors. So, compared to Ghostery, it lacks extended blocking list. If the list will get bigger, I'll use it. For example, in Failblog this extension blocking 3 Third-Parties and Ghostery 6...
I hope...
BugMeNotDec 14th 2010 12:46AM
@Matthew Rogers
Good answer. I have a similar view, with the exception that as soon as I learned that they implemented "click to play", I added it immediately. I usually don't try to have redundant extensions myself, but often Chrome is the one that is playing catch-up so by the time they add a certain requested feature, it makes pre-installed extensions feel obsolete. I do however make it a point to keep them installed if they have more functionality than Chrome's, but with resource blocking (like cookies), which is currently hamstrung, I just wasn't sure if that criterium still applied.
Matthew RogersDec 14th 2010 1:01AM
@BugMeNot Yep, I guess it's really just a matter of time for all of these sorts of things. It'll be interesting to see how this particular extension shapes up over the next couple of months, and then we'll really know if it's up to task or not :)
Jigsaw hcDec 14th 2010 2:35AM
I'll have to check this out just to see how much I'm being tracked.
Brian KennishDec 14th 2010 3:48PM
@Matthew Excellent, comprehensive post.
I actually hadn’t heard about the Google Reader bookmarklet being busted — a couple people reported they couldn’t get to Bookmarks, which I patched last night. The bookmarklet thing is trickier but probably fixable. I filed a bug at http://code.google.com/p/byoogle/issues/detail?id=33.
Matthew RogersDec 14th 2010 9:36PM
@Brian Kennish Haha, now see, I was thinking that the Reader bookmarklet was what had already been addressed :) Oh well, either way, it's been accounted for now!
Thanks for getting back to us with that info, Brian!
Brian KennishDec 17th 2010 12:54PM
@Matthew The Google Reader bookmarklet is securely allowed now! All other third-party google.com and yahoo.com resources are too. You just need at least v2.1.0, which I pushed yesterday. (If you have the extension installed, you should’ve already been autoupdated. If you don’t, installing will do the trick.)
I’m releasing a new version every day till I work my way through the issues users have, very helpfully, told me about so far. I expect to be done by Monday.
PS, how the heck do I add a picture to my comments?
Matthew RogersDec 17th 2010 4:04PM
@Brian Kennish Awesome! I'll update the post right now :)
As for pictures in comments, the whole system is still wonky, as we're barely finishing the new redesign... so I'm at a loss for now.