Inside Safari 3.2's Anti-Phishing Feature 135
MacWorld is running a piece from MacJournals.com's for-pay publication detailing how the Safari browser's anti-phishing works. The article takes Apple to task for not thinking enough of its users to bother telling them when Safari sends data off to a third party on their behalf. For it seems that Safari uses the same Google-based anti-phishing technology that Firefox has incorporated since version 2.0, but, unlike Mozilla, tells its users nothing about it. "Even when phrased as friendly to Apple as we can manage, the fact remains that after installing Safari 3.2, your computer is by default downloading lots of information from Google and sending information related to sites you visit back to Google — without telling you, without Apple disclosing the methods, and without any privacy statement from Apple."
Haven't upgraded... (Score:1, Interesting)
Re:It's Not About Who Sees What (Score:2, Interesting)
Re:I don't "love" a company (Score:3, Interesting)
Webkit's really not Cocoa, but I guess it's not politically correct to say that it's Carbon. :)
Integration with OS X is a lot easier for Cocoa applications, of course. It's harder if you're using code not written in Objective C, as Safari and Camino both do (Webkit and Gecko), but it's certainly possible... as both Safari and Camino demonstrate.
Safari and Camino use the keychain for passwords. Firefox doesn't.
Safari and Camino use the OS X proxy settings. Firefox doesn't.
Safari and Camino integrate with Services fully. Firefox doesn't.
Safari and Camino are well integrated with OS X. Firefox isn't.