Re:Deconstructing Google’s excuses on tracking protection
by dan-robertson on Friday August 23, 2019 @07:08PM
(#20783660)
I agree that there are good reasons to want something less declarative but I claim that only allowing declarative rules is a reasonable bona fide choice from a security or privacy perspective. In particular if there were no question of motives, I think there would be far fewer complaints about this system being implemented. Indeed Apple’s system for mobile url filtering works like this and though some people complained about the lack of expressivity I didn’t see any complaints that it was some kind of conspiracy to sell ads.
[ Parent
| on HN ]
Re:Deconstructing Google’s excuses on tracking protection
by tsimionescu on Saturday August 24, 2019 @01:57AM
(#20785516)
You keep missing the fact that there is no security/privacy advantage to what Google did, since the API for an extension to see every URL being accessed and use it in arbitrary ways still exists. They only removed the part where the extension could block that request from happening.
Re:Deconstructing Google’s excuses on tracking protection
by SpicyLemonZest on Saturday August 24, 2019 @01:15PM
(#20788361)
Selective request blocking has huge security implications. In many ways it's a similar attack surface to arbitrarily rewriting the content. (Imagine making some charges to your credit card, then blocking the request that lists card charges on your bank's website.)