This is great, but unfortunately, until Apple ups its browser security game, Safari is a non-starter. On macOS, switching from any other browser to Chrome is in the top 3 things you can do to materially improve your security in ways that actually matter in the real world.
Apple adds a tracker blocker to desktop Safari
41–50 of 301 posts
Re: Apple adds a tracker blocker to desktop Safari
#42Re: Apple adds a tracker blocker to desktop Safari
#43The big question to me is whether it's enabled by default, and whether it blocks requests to Google Analytics. If so, that's an interesting shot across the bow.
This is actually really concerning to me. If they blocked Google Analytics, it would severely damage that data. It'd be bad news for site owners who just want to quantify their traffic.
Re: Apple adds a tracker blocker to desktop Safari
#44This is great, but unfortunately, until Apple ups its browser security game, Safari is a non-starter. On macOS, switching from any other browser to Chrome is in the top 3 things you can do to materially improve your security in ways that actually matter in the real world.
Can you give specific examples why Chrome is significantly better than other browsers, including Firefox, Opera? Chrome is a non starter for me because of its resource usage and battery hunger. One specific area where Safari is better than Chrome is in private browsing mode. In Safari, each tab is completely separate, and the cookies aren't shared (as far as I can tell) whereas in Chrome, it's only separate as a whol…
Re: Apple adds a tracker blocker to desktop Safari
#45The big question to me is whether it's enabled by default, and whether it blocks requests to Google Analytics. If so, that's an interesting shot across the bow.
Re: Apple adds a tracker blocker to desktop Safari
#46This is great, but unfortunately, until Apple ups its browser security game, Safari is a non-starter. On macOS, switching from any other browser to Chrome is in the top 3 things you can do to materially improve your security in ways that actually matter in the real world.
I am curious to know why you say this considering Safari is just as sandboxed as Chrome?
Re: Apple adds a tracker blocker to desktop Safari
#47Thumbs up for Apple distinguishing themselves by their pro-privacy stance, as opposed to MS, who don't have anything to win by Win10's excessive "telemetry" IMHO.
Re: Apple adds a tracker blocker to desktop Safari
#48This is great, but unfortunately, until Apple ups its browser security game, Safari is a non-starter. On macOS, switching from any other browser to Chrome is in the top 3 things you can do to materially improve your security in ways that actually matter in the real world.
Chrome may be relatively decent at preventing a webpage from compromising your OS, but in the modern era, a compromised browser is as bad or worse anyways, since that's where most of your sensitive activity goes.
While many HN readers will know to avoid the perils of this crud, I don't feel Chrome can be recommended over IE6 to the wider Internet while this remains so commonplace. Safe use of Chrome requires constant vigilance.
In light of Chrome's issues, I feel like a claim that switching to Chrome is important for security to require an exceptional evidence of vulnerability in the other browser.
Re: Apple adds a tracker blocker to desktop Safari
#49It's unclear to me how these "trackers" work? How do they track you, is it cookies, or what?
A decent overview: https://panopticlick.eff.org/about Test your browser: https://panopticlick.eff.org/
I found this one rather interesting, it was the most unique of the ones listed:
HTTP_ACCEPT Headers
One in several thousand have the same headers as me. But the headers themselves are quite a small little string, I'm surprised it is that unique.
Re: Apple adds a tracker blocker to desktop Safari
#50Earlier quoted context omitted.
> Does this mean browser fingerprint is somehow scrambled before it is sent to the tracker instead of blocking? It might be homogenized instead of scrambled. Every iOS device could be given (barring IP etc.) the same fingerprint.
I don't think that's even theoretically possible. How do you block JS font enumeration without crippling the browser font API?