The potential business benefits to Google from this move are hard to ignore. far too insignificant to have any noticeable impact on the user experience. This found that median decision time per-request is actually in the sub-millisecond region: i.e. One study, published on, analysed the performance of some of the most popular ad-blocking extensions, including uBlock Origin, Adblock Plus and Ghostery. As uBlock Origin author Raymond Hill pointed out, if users are experiencing performance lag, it’s much more likely to be down to pages bloated with trackers than the presence of content-blocking extensions. These arguments have been greeted with some scepticism. With declarativeNetRequest, the extension lets the browser make the decision itself, which (theoretically at least) results in a faster connection. Currently, when a content filtering extension uses the webRequest API, Chrome basically refers the network connection request to the extension and waits for its decision on whether that connection should be allowed or blocked. The company has been especially keen to stress the likely impact of the change on browser performance. Google states that its changes are always driven by the motivation of increasing the security, privacy and performance of Chrome extensions.Īccording to Google software engineer, Devlin Cronin, “It is not, nor has it ever been, our goal to prevent or break content blocking”. All other users will have to rely on declarativeNetRequest as the primary content blocking API. Now it seems that if you’re a paying enterprise Chrome user, you will still be able to rely on the content-blocking capabilities of webRequest. The argument is that fewer rules would mean a much less comprehensive blocking capability.įast forward to the end of May and there was some partial backtracking on the part of Google. The trouble is that most ad blockers filter content by relying on vast, crowdsourced blacklisting rulesets, which tend to require way more than the declarativeNetRequest 30,000 rule limit. Under declarativeNetRequest, Chrome will basically decide whether to block content based on a ruleset limited to 30,000 individual rules. One change (announced in January) caused particular consternation among developers: for content blocking, Google now wants extensions to use a different API, declarativeNetRequest. Last year, Google started hinting at some of the changes that were in the pipeline as part of its upcoming revised rules for the extensions platform (Manifest V3). ads, pop-up videos and unsafe sites) before this content even reaches the browser. This allows users to filter out and block specified types of content (e.g. Under it, content-blocking is handled by Chrome’s webRequest API. The current platform for Chrome extensions (Manifest V2) has been in place since 2012. To be included on the Chrome Extensions platform, apps must be built and deployed in accordance with Google’s specifications. small software programs designed to enable users to customise their browsing experience. Add a header to begin generating the table of contents Chrome Ad Blocker Restrictions: What is set to change?Īd blocking applications are extensions: i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |