3 ms·
I use NoScript daily and while it requires a bit of interaction the first time you visit a website it really isn't that hard to use. Just allowing the TLD and
by jandrese 11y ago
I use NoScript daily and while it requires a bit of interaction the first time you visit a website it really isn't that hard to use. Just allowing the TLD and any obvious CDNs covers about 95% of all websites. If you do run across some website that is just horribly busted, there's always the "allow all temporarily" button, but I find it is extremely rare that I have to resort to that. And the times that I have I usually discover that it is in fact the website that is broken, not my browser settings.
- myztic 11y agoWe are talking about the general public, yes it is hard to use and incredibly cumbersome for those people. Imagine explaining your grandma how to use it, we are not talking about people browsing HN ;)
- newscracker 11y ago> Just allowing the TLD and any obvious CDNs covers about 95% of all websites. I know about the options NoScript provides, but I see this statement itself as part of the problem. If we just whitelist sites that we use and see (to have them work), we're not really stopping tracking, are we? We're just guarding against unknown sites. Most people visit perhaps 10 major sites on a regular basis everyday, and all the popular ones that people would whitelist use trackers. I'm not denying the benefit of being protected from unknown, obscure and malicious sites that we may land in once in a while and things like XSS protection, but that alone is not enough in this context. What we need is either a trusted block-list for NoScript that's updated periodically, similar to block-lists that exist for ad-blockers, or some other mechanism that can curb the tracking potential of scripts (I don't know the answer for the latter).
- jandrese 11y agoYou obviously don't whitelist google-analytics.com or facebook.net.