3 ms·
Is the Chrome team still hellbent on killing ad-blocking with the half-baked Manifest changes that will render uBlock useless? How much longer will ad-blocking
by 0xy 6y ago
Is the Chrome team still hellbent on killing ad-blocking with the half-baked Manifest changes that will render uBlock useless? How much longer will ad-blocking be supported?
- vbezhenar 6y agoThere’s dedicated API to support url blocking. Some uBlock features might be unavailable, but most features can be implemented with new API.
- wtallis 6y agoFeatures beyond mere URL blocking are what made uBlock popular in the first place.
- vbezhenar 6y agoWhat features are you talking about?
- wtallis 6y agoWhen uBlock first came onto the scene, its main selling point was that it had vastly better performance than Adblock when using filter sets that had lots of block rules based on CSS selectors rather than just URL regexes. And third-party filterset subscriptions that made heavy use of CSS-based element blocking rules had become quite popular by then. So an API that only provides for URL blocking is missing almost the entire point of uBlock. (I wasn't using any third-party filtersets at the time, so I found uBlock unimpressive and stuck with Adblock Plus for quite a while because I found its UI better for curating my own blocking rules.)
- vbezhenar 6y agoI don’t know how uBlock handles CSS rules, but you can just add your stylesheets or add your JavaScript to the page, it should be enough and as performant as possible. AFAIK there are esoteric features like DNS filtering which is not possible with declarative API. But I’m not sure if it’s used widely, I never saw it.
- 0xy 6y agoThey killed intelligent features like CNAME ad bypass detection, which effectively kills ad-blocking. So no, if there's an easy bypass of ad-blocking that's absolutely false.