Once upon a time, when I was a young turk, I would assiduously download every last doodad that my employer created as soon as it shipped – or often long before, happily reaching for the pile of floppy disks as I rebuilt my computer for the umpteenth time following the latest toxic combination of untested software.
Age (and a need to still be able to work on my computer) has slowed me down. So I passed over IE8 beta 1, preferring to read about others’ experiences of the new “standards mode” that is the default rendering mode for the new browser.
But last week, only hours after its public availability, I downloaded and installed IE8 beta 2. Why? Because it contains a raft of new features for protecting user privacy. I’ve blogged previously about the eternal tension between user privacy on the web, and the measurement and tracking that is so essential to many websites’ business models. Put simply, if users’ behavior could not be measured online, a lot of online businesses would go out of business.
So how does IE8 contribute to the debate? Well, there are a number of minor features to protect users, and one major one. The minor ones include a nice feature in the address bar to highlight the actual domain of the site you’re looking at:
This makes it much easier to spot phishing attacks, since many phishing sites try to confuse users by including familiar looking domains as subdomains of the real site, e.g.:
Another nice feature, related to phishing, is the “Smartsite Filter”. This allows the user to check the current website against a known list of bad sites.It’s essentially a UI into the automatic phishing filter that was built into IE7 – but it allows users to report sites as well as check them, adding a Cloudmark-like element of user contribution to the process of spotting evil sites.
The other small enhancement worth noting is that the “browsing history deletion” feature has become smarter – you can elect to delete the cookies etc. for all sites except those in your favorites list. This is a step forward, but it still mystifies me that IE has no easy way for browsing the cookies (and their content) on your computer, and selectively deleting them (as Firefox has had since v2, it pains me to say).
InPrivate Browsing & Blocking
The big new security/privacy feature in IE8 is called InPrivate Browsing (others have dubbed it “porn mode“, but I am above such lewdness). InPrivate Browsing allows the user to browse without storing any cookies or browsing history, or locally cached files. It’s good for when you’re borrowing someone else’s computer, or if you share a computer and don’t want the other people who use the computer to know what you’ve been up to (now you are starting to understand where the “porn mode” nickname comes from).
The naming of the InPrivate functionality is somewhat confusing. Once you turn on InPrivate Browsing (either from the Safety menu or using Ctrl+Shift+P), something called InPrivate Blocking is also activated. InPrivate Blocking prevents your browser from sending requests for third-party content that it thinks are principally for the purpose of tracking your behavior. The big difference here is that this isn’t just blocking third-party cookies – it’s third-party content. That’s tracking pixels, third-party JS calls, and yes, ads.
InPrivate Blocking will block third-party requests if one of the two following conditions have been met:
- The request URL has been made in a third-party context on more than 10 other domains
- You have specifically added the request URL through an InPrivate Blocking Subscription
To understand the first condition, take a look at the screenshot below, which is the dialog that comes up if you select InPrivate Blocking from the Safety menu when InPrivate Browsing is active:
You’ll notice that there are some third-party request URLs that come up, well, a lot. googleadsyndication.com is the domain that Google AdSense ads are served from; and you will doubtless know what comes from google-analytics.com. In the dialog above, the four URLs across these two sites have each been requested at least 20 times in a third-party context, and I’ve only been using IE8 for a few days. With the default settings (“Automatically block”), these URLs are blocked when I am in InPrivate mode.
The other way of adding a URL to the blocked list is to subscribe to an InPrivate Blocking list. This is an RSS or Atom feed of URLs that IE8 should block in InPrivate mode. I have created a subscription list which blocks third-party requests to analytics.live.com – the domain for adCenter Analytics’s tracking JS and pixel. You can try it out by clicking here.
The power of the feed-based approach to InPrivate Blocking is that privacy advocacy sites can post a single link to a feed XML file which users subscribe to; if that file changes, the users’ blocking lists change. So you can expect to find “click here to block ALL tracking pixels and ads” links on such sites in the not-too-distant future. You can take a look at your InPrivate Subscriptions through the Manage Add-ons option in the Tools menu:
“Aargh! This sucks!”/”Great!” [Delete as applicable]
Whether news of this functionality sends a shiver down your spine or warms the cockles of your heart depends on whether your business depends on online advertising or web analytics. Popular third-party analytics systems like Google Analytics, or third-party ad servers like Atlas Enterprise will lose data on users who enable InPrivate Browsing; and even a less popular service that might not normally be blocked automatically could end up on common “Opt-out” feeds and have its tracking blocked, especially if had a poor reputation for privacy.
I must admit that when I first read of this functionality, I was – ahem – a little apprehensive, for the reasons above. And in truth, only time will tell what proportion of users are engaging InPrivate browsing (although, given the nature of the functionality, we’ll not be gathering this data). But my gut feel is that, whilst this capability is a welcome addition to the privacy and security arsenal of Internet Explorer, actual take-up of the feature will be low. It n
eeds to be invoked explicitly, of course, and the blocking of persistent cookies means that some desirable features of websites (such as being able to remember you from visit to visit) will be disabled. So I imagine it will be used sparingly by the vast majority of users.
Even so, this feature could easily add another 1 – 2% to the existing disparity between different measurement systems (such as an in-house web analytics system and a third-party ad server). Though there are techniques that vendors could use to work around the automatic blocking – the best example being the use of CNAME DNS entries to make the third-party tracking URLs look like first-party URLs – these techniques will add complexity to the implementation of such systems; so it might be easier for us all to live with a little less certainty.
If you’d like to read more about the new features in IE8, there’s a ton of stuff over at the IE blog. And, with my Microsoft hat firmly on my head, I should say that the IE team has done an outstanding job with this beta, which is performing really well for me, and rendering most sites flawlessly, with just a few slight layout differences cropping up here and there. Well done, guys.