5 ms·
Yes, this is what I said above: “Surely the problem isn’t making changes to a page, but instead having access to the full page content and being able to send it
by orf 2y ago
Yes, this is what I said above: “Surely the problem isn’t making changes to a page, but instead having access to the full page content and being able to send it somewhere else.”
“Send it somewhere else” being the important part.
The interface Chrome went with was a declarative list of filters that Chrome will use to perform the actual filtering, but the declarative interface isn’t great and wasn’t well received.
My point is: there is an interface that is non-declarative and sandboxed, whilst allowing Chrome to perform the actual filtering.
- rcxdude 2y agoYeah, but you can't do both, that's the point! If you can directly change the website content, the website itself runs in a sufficiently non-sandboxed environment to allow the data to be sent somewhere else. You can only get around this by making a more limited blocking process (which may not need to be as limited as chrome has gone with, but still, not being able to e.g. substitute in shims for ad networks will reduce the effectiveness of your adblocker. It certainly makes anti-ad-blocking have the significant advantage).