Google explains how and why Safari privacy settings were circumvented: In response, Google says the WSJ report is off-base when it comes to what Google is doing with its advertising cookies on these devices. Google says it was using a known bit of Safari functionality to provide features that were only enabled when users signed into Google using their browser. Google used this functionality to provide personalized ads and the ability to +1 items for signed-in Google users. Google then pins the problem on Safari; the statement says the browser…

> Podjarny said Blaze would be “more than willing” to create a new report if Apple decides to apply the Web performance optimization to the embedded Web browser. via [macworld.com](http://www.macworld.com/article/158628/2011/03/apple_blaze_browsing.html#lsrc.rss_main)How about you test the ACTUAL Safari browser, rather than ask Apple to change its embedded browser, Blaze? You know, if you perform a study, and it gets revealed that your methods are getting erroneous data, it’s usually then up to the administrator of…

> The one thing you can immediately influence is whether your users are able to easily read your articles. If they are not, then perhaps Safari Reader is not the problem, but merely a symptom of your *actual* problem. > > If people don’t feel the need to use Safari Reader anymore, everybody wins. Don’t fight Safari Reader. Instead, make it obsolete. via [ignorethecode.net](http://ignorethecode.net/blog/2010/06/10/safari_reader/)I absolutely agree. I talked about this a while ago, when Ars Technica went on a rant…