Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Huge Newsgroups: comp.security.misc,comp.internet.services.google,comp.misc,alt.privacy Subject: Re: Wow, fancy that. Web ad giant Google to block ad-blockers in Chrome. For safety, apparently Date: 27 Jan 2019 11:09:56 GMT Organization: Piglet's Pickles & Preserves Lines: 26 Message-ID: References: Reply-To: usenet@huge.org.uk X-Trace: individual.net F8EGQiWP9KG3VJfItdYk0gjyZG0pR8jNJJq9dIbT2KYykQSwxr Cancel-Lock: sha1:RidGMaDOYR418+YJCdBVPJELmS4= X-No-Archive: Yes X-Clacks-Overhead: GNU Terry Pratchett User-Agent: slrn/1.0.3 (Linux) Xref: csiph.com comp.security.misc:1403 comp.internet.services.google:881 comp.misc:17353 alt.privacy:23128 On 2019-01-26, Rich wrote: > In comp.misc Juergen Nieveler wrote: >> On 26.01.2019 05:56, !!Credit wrote: >>> Google engineers have proposed changes to the open-source Chromium >>> browser that will break content-blocking extensions, including ad >>> blockers. >> >> It will also break data-stealing malware extensions though - which is >> the point of the change > > The solution there, however, is not to remove the API, but to add a > "grant only" permissions system such that the end user has to grant an > extension the right to use the API. > > Those installing uMatrix or uBlockOrigin will naturally want to "allow" > both to access the API. But if some other extension, that does not > need such access, asks to be granted, then the user has the choice of > denying such access. And of course that works *so* well in all the other cases when something pops up. [User clicks 'Yes' without reading or understanding.] -- Today is Boomtime, the 27th day of Chaos in the YOLD 3185 ~ Stercus accidit ~