Archive for January, 2011

File Under: Browsers, Identity, Security
Jan
25
2011

Chrome Add-on Kills Tracking Cookies

By

Not to be outdone by Mozilla, Google has released a new add-on for its Chrome web browser that allows users to opt-out of online advertising tracking. While Mozilla’s privacy tool is still just a proposal, and involves a new HTTP header, Google’s add-on uses the more practical, cookie-based approach and works today.

The Keep My Opt-Outs add-on works like a very persistant cookie, but this one is working in your favor. The add-on uses Chrome’s internal cookie APIs to set the opt-out flag for each advertising network that participates in the opt-out program created by the ad industry. Not only is it easier than setting those cookies yourself, the add-on ensures that, even if you clear the rest of your cookies, the opt-out cookies remain intact.

While it works, Google’s approach is something of a hack. The add-on intercepts and rewrites cookies, which is not exactly an ideal solution. Still, if you’re a Chrome user and you’ve been looking for a way to stop advertising cookies today, the Keep My Opt-Outs add-on has you covered.

Keep My Opt-Outs also makes a viable alternative to ad-blockers, particularly for those concerned that ad-blocking add-ons are denying their favorite sites much needed revenue. Provided you don’t mind a few advertisements here and there, using the new add-on in conjunction with some smart cookie settings, you can support your favorite sites without forfeiting your privacy. And for those that do use ad blockers, keep in mind that just because the ad is not shown, doesn’t always mean it can’t set cookies.

In the long term, Mozilla’s header-based approach to stopping cookie-based tracking is a better solution, and we expect, if the idea catches on, Chrome and other browsers will support it as well. For those who want something that works today, Google’s new add-on fits the bill.

Footprints photo by Vinoth Chandar/Flickr/CC

See Also:

Tags: ,
File Under: Browsers, Identity, Security
Jan
24
2011

Mozilla Plans ‘Do-Not-Track’ Privacy Tools for Firefox

By

Mozilla wants to create a new HTTP header that will allow Firefox and other browsers to shut off web tracking tools like cookies. The new header would offer a universal way to tell websites that a user wishes to opt-out of third party, advertising-based tracking.

Behavioral advertising, as such tracking is known, is becoming increasingly common on the web. Advertisers use cookies to follow you around the web, tracking which sites you visit, what you buy and even, in the case of mobile browsers, where you go. The U.S. Federal Trade Commission has already outlined a Do Not Track mechanism (PDF link), which would work much like the FTC’s Do Not Call list, offering a way to opt-out of online tracking.

The proposed do-not-track HTTP header is one of several ways Mozilla plans to implement the FTC’s suggestions. While the header idea has been around for a while — the Do Not Track Firefox add-on from the Stanford Law School is one example — currently most online opt-out schemes use cookies to set user preferences. Mozilla believes “the header-based approach has the potential to be better for the web in the long run because it is a clearer and more universal opt-out mechanism than cookies or blacklists.”

While the new header is just a proposal at the moment, Mozilla already has some code ready and is considering adding the feature to future versions of Firefox. The current plan is to create a new preferences option that would allow you to opt-out from tracking. Check the box in the preferences and Firefox will start sending the do-not-track header each time you request a new page.

Interestingly, the header Mozilla proposes is not the same as the “X-Do-Not-Track” proposal, which is already implemented in Firefox add-ons NoScript and Adblock Plus. For more details on how Mozilla’s new HTTP header will work, see Mozilla developer Sid Stamm’s blog post.

Like Mozilla’s proposed privacy icons, the problem with the new header is getting third-party ad sites to obey it. Mozilla calls it a “chicken and egg” problem and hopes to jumpstart the idea by including the header in future releases of Firefox. At that point it would be up to third party websites to support the header and, as Mozilla puts it, “honor people’s privacy choices.”

See Also:

Tags: , ,
File Under: HTML, HTML5, Web Standards
Jan
21
2011

Meet HTML, The Spec Formerly Known as HTML5

By

It won’t be an unpronounceable symbol, but HTML5 is getting a Prince-style name change. From here on out HTML5 will simply be HTML — according to the WHATWG anyway.

Just a day after the W3C unveiled its new HTML5 logo, the Web Hypertext Application Technology Working Group (WHATWG) has announced that it will drop the term “HTML5,” stop the versioning of HTML altogether and instead treat the evolving specification as a “living standard.”

While eliminating the version number from HTML has been part of the WHATWG’s plan from the beginning, the timing of the change is clearly related to the W3C’s attempt to embrace the term “HTML5.” The W3C recently showed off a new HTML5 logo, but the accompanying FAQ used the term HTML5 to cover everything from the actual spec to only tangentially related tools like CSS 3, WOFF and SVG. Many developers saw the W3C’s nebulous use of the term HTML5 as a sign that the term had become, like “AJAX,” just another marketing buzzword.

The W3C has since rewritten its FAQ to clarify and more sharply define just what HTML5 is and is not, but before that happened Ian Hickson, the WHATWG’s editor, announced that the WHATWG was renaming its spec to just HTML. Hickson says the WHATWG was “going to change the name last year but ended up deciding to wait a bit since people still used the term ‘HTML5′ a lot.”

Hickson then makes a not-so-subtle jab at the W3C, saying HTML5 “is now basically being used to mean anything Web-standards-related, so it’s time to move on!”

The W3C has long had a tenuous relationship with the WHATWG. Technically the W3C is the standards body charged with publishing the HTML spec. The WHATWG — a consortium of browser makers — grew out of the W3C’s neglect of HTML and its misguided decision to pursue XHTML 2. Now that both groups are working on the same spec, in theory, their goals are the same. In practice, however, the two groups often butt heads. In other words, just because the WHATWG has decided to abandon the term HTML5, don’t expect it to disappear overnight.

The W3C will continue to work toward “snapshots” that reflect stable milestones of the ever-changing WHATWG version of the spec. For now at least, that means the term HTML5 will be alive and well at the W3C, as the group works through its standard practice of issuing working drafts, holding last calls on changes and finally publishing the spec as a “recommendation.”

Since browser makers have long been well ahead of the W3C when it comes to implementing the latest and greatest parts of the HTML5 spec, they will likely focus on the WHATWG’s HTML spec, which will, like Google’s Chrome browser, follow a “rolling release” schedule.

No doubt the media and marketers will continue to use HTML5 as a buzzword that means far more than just the spec, but even that’s not always a bad thing. There’s no doubt that Apple, Google, the New York Times and everyone else who’s used HTML5 as an analog for the New Shiny has helped HTML5 — and all the other tools it’s come to stand for — gain momentum. As web developer Jeff Croft puts it, “sometimes we just need a word to rally behind.”

While not everyone understands the nuances of what’s HTML5, what’s CSS 3 and what’s just JavaScript, that doesn’t change the fact that everyone is excited about building a better web and that is exactly what HTML(5) is designed to do.

See Also:

Tags: ,
File Under: Browsers
Jan
21
2011

Chrome 10 ‘Obliterates’ Your Browsing History

By

Version 10 of Google’s Chrome web browser has entered the dev channel, available to those who enjoy living on the edge. This release features an update to the V8 engine that powers Chrome’s speedy JavaScript, a more refined preferences dialog and print and save options for any PDF files you view in Chrome.

If you’re already subscribed to the dev release channel you should be automatically updated. If you’d like to take the dev channel for a spin, Google has instructions on how to switch Chrome channels.

Of course the dev channel releases often have bugs and Chrome 10 is no exception. Commenters on the Google Chrome blog report that Google Sync no longer works with this release. If that happens to you, you might try disabling any startup flags you might have been using with previous releases, which reportedly solves the problem.

Along with the update to the JavaScript engine, this release features a number of bug fixes (particularly on the Mac platform) and some welcome refinements to the new tabbed preferences dialog. In addition to a better looking UI, the new settings page now has a search box to quickly find the preference setting you’re looking for.

Chrome 10 also features an updated message for the “clear browsing data” option on the preferences page. Instead of just deleting your browsing history and other items, you can now “obliterate the following items from the beginning of time.” We doubt that bit of linguistic whimsy will make it all the way to the stable release of Chrome 10, but it’s certainly more entertaining than the old “clear browsing data” message.

Provided Google sticks with its six week update schedule, Chrome 10 should arrive as a stable release in April 2011.

See Also:

Tags: , , ,
File Under: Browsers, Web Basics
Jan
19
2011

Firefox 4 Ditches the RSS Button, Here’s how to get it Back

By

That dark spot no one clicks? Yes, that's the RSS button

Firefox 4 is nearly complete. The next version of the venerable web browser introduces dozens of new features — everything from built-in bookmark syncing to hardware acceleration — but it also removes a few noteworthy features as well.

The now-departed status bar — which has been replaced by the add-ons bar — isn’t the only thing that’s been relegated to dustbin in Firefox 4. The familiar RSS icon in the URL bar is gone as well.

RSS has a long, complicated history and, despite its usefulness to the web at large, it just never caught on with mainstream users. RSS may power much of the web behind the scenes, but from a user’s point of view it remains an awkward tool with a terrible user interface. As Firefox developer Leslie Orchard points out, clicking the old Firefox RSS button would give you “a plainly-styled version of what you were probably already looking at on a site.” Of course, if you knew what you were doing, you could quickly either create a live bookmark or add the RSS feed to a feed reader. But for the uninitiated, the UI was confusing enough that Orchard says “some people would think they broke the page when the button was clicked on accident.”

According to Mozilla’s user study the RSS icon was clicked by a scant 3 percent of users. The only thing more neglected is the scroll left button, which is only present on very wide websites. With no one using the button, Firefox designers decided to remove it from the increasingly cluttered URL bar.

Cue the outrage and pleading for its return.

But just because the RSS button has lost its former position in the toolbar doesn’t mean you can’t easily subscribe to RSS feeds in Firefox 4. There’s a new menu option under the Bookmarks menu that will offer to “Subscribe to this page” and you can also add a subscribe button to your toolbar if you like. Just head to the customize option under the View menu and you’ll see a new toolbar button for RSS feed. Drag that button to the toolbar and you’ve restored the RSS button.

Given that seemingly no one used to original button, removing it hardly seems a bad thing, especially when it’s easy to get it back.

See Also:

Tags: ,
« OLDER POSTS