Looks like Chrome is “improving the user experience again. theregister.co.uk/2019/01/22/goo
Conversation
I don’t just mind that Google does user-unfriendly crap with their monopoly browser. What I really hate is the Orwellian doublespeak about how this is really all to make things better for their users.
5
32
134
Replying to
The alternative is that any extension can steal all your cookies and manipulate any content on every page you visit. Unfortunately that's how any API with the capability of the webRequest API must work, because that's how manipulating the HTTP stack works.
4
3
7
What about the iOS approach? Blocker hands over what has to be blocked: Safari executes it. No information leakage towards plugins.
1
1
That's exactly the proposal for the declarative API. It currently isn't good enough but it's only a proposal that's still some way away from shipping in even the experimental channels. It needs to support using far more rules along with a lot more flexibility to be a replacement.
1
They want to move to a model where the content filtering engine is provided by the browser and extensions provide the filters, as a step towards removing the API exposing all web content to extensions. They're clear that the old API is staying around for the near future though.
As long as they implement a good content filtering engine, it can become a viable way to implement nearly all the ad-blocking extensions. It will be faster and more reliable too, since there's no failure case where the extension times out or crashes and the content isn't removed.
1
It's a request for comments about it and they've received a bunch of feedback on what needs to be better. I don't think ad-blocking extensions are going to be in trouble. The point of requesting feedback was determining in what ways it's going to be too limited for common uses.
1
Show replies