Re:Google to restrict modern ad blocking Chrome extensions t...
by shawnz on Thursday May 30, 2019 @04:50AM
(#20049460)
It's not for privacy, the people who were saying that are either mistaken or intentionally lying. It's clear to see because the observational capabilities of the API aren't being removed -- only the blocking capabilities. So the privacy issue is still there. Supposedly, this change is just for performance.
Re:Google to restrict modern ad blocking Chrome extensions t...
by SquareWheel on Thursday May 30, 2019 @08:46AM
(#20050560)
>It's not for privacy, the people who were saying that are either mistaken or intentionally lying.
They're not lying. This was listed as one of the reasons by Google.
>The declarativeNetRequest API provides better privacy to users because extensions can't actually read the network requests made on the user's behalf.
https://developer.chrome.com/extensions/declarativeNetReques...
Re:Google to restrict modern ad blocking Chrome extensions t...
by shawnz on Thursday May 30, 2019 @09:27AM
(#20050889)
What I mean is the fact that they are deprecating the blocking API. That wasn't an action taken for privacy's sake. Otherwise, why wouldn't they deprecate the observational API too?
Re:Google to restrict modern ad blocking Chrome extensions t...
by SquareWheel on Thursday May 30, 2019 @10:14AM
(#20051317)
I don't know. It's a very fair question.
Re:Google to restrict modern ad blocking Chrome extensions t...
by cortesoft on Thursday May 30, 2019 @06:06AM
(#20049744)
Oh really? Damn
Re:Google to restrict modern ad blocking Chrome extensions t...
by Rebelgecko on Thursday May 30, 2019 @01:26AM
(#20048643)
Does it actually prevent that though? Is there no other mechanism that lets extensions know the URL of the current page?
The new way has the extension give a list of patterns to block to chrome, and from there it will block any request that matches.
The stated reason is that this is for privacy, to prevent extensions from being able to gather data about every request a browser makes. Currently, a malicious extension could send every url a user visits to some central collection server. The new way prevents that.
Is the trade off worth it? I personally think no, but I do think many people don't realize that as blockers have the capability to collect every url you visit if they wanted.