Re:Web Request and Declarative Net Request: Explaining the i...
by buckminster on Wednesday June 12, 2019 @03:16PM
(#20168263)
It does nothing for privacy because extensions will still be able to see the requests, they just won't be able to block them.
Re:Web Request and Declarative Net Request: Explaining the i...
by dfabulich on Wednesday June 12, 2019 @04:49PM
(#20169159)
No, manifest v3 extensions will only be able to observe requests for specific hosts, with permission from each host.
Re:Web Request and Declarative Net Request: Explaining the i...
by buckminster on Wednesday June 12, 2019 @06:58PM
(#20170211)
This isn't mentioned in the public version of the v3 spec (perhaps I'm looking in the wrong place) or in today's blog post. Do you have a reference?
Re:Web Request and Declarative Net Request: Explaining the i...
by magicalist on Wednesday June 12, 2019 @08:17PM
(#20170712)
One of the other comments has a link to this tweet about it:
> Yes, but network requests won't be observable without permission on the relevant hosts. And host permissions are changing significantly in Mv3 (e.g. they can't be granted as blanket install time permissions).
https://twitter.com/justinschuh/status/1138889508512866304
there's also some stuff in the design doc: https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz...
Which explains the specific hosts part, but only makes vague mention of how extensions that users do want to run on every site will get permission to do so.
Re:Web Request and Declarative Net Request: Explaining the i...
by buckminster on Thursday June 13, 2019 @10:48AM
(#20175398)
Thank you. If Google were trying to be obfuscatory they could hardly do a better job.
Declarative rules engines are better and preserve privacy better. This is Google following Apple's lead and doing the right thing.