A few month ago , Google announced changes were derive to improve privacy , surety , and operation with regard to Chrome extensions . In particular , one change did n’t sit well withad blocker developer , who claimed Google was looking to fall their efficacy . At the time , at least one company threatened to pursue file an antitrust charge .
Yesterday , Google hit back with ablogthat basically pronounce , “ Nuh uh . We ’re not try out to kill ad blocker , we just want to make them secure . ” At the core of the issue is the Web Request API . Google announced it was replacing some parts of that particular API with what it calls the Declarative Net Request API . In Google ’s Holy Writ , the change means an telephone extension “ does not need admission to all a drug user ’s sensitive data in lodge to block depicted object . ” It goes on to explicate the current Web petition API requires users to grant permission for Chrome to pass along all information in a web postulation , and that can include individual data such as electronic mail and pic . However , the society claims the new API will leave filename extension to block content without requiring users to give access to individual data .
“ There ’s been a lot of disarray and misconception around both the motive and implications of this change , including venture that these changes were designed to keep or weaken ad blocker , ” Google write in aseparate blogdetailing the deviation between the two genus Apis . “ This is absolutely not the goal . In fact , this variety is mean to give developers a way to create safer and more performant advertising blockers . ”
Photo: Mark Lennihan (AP Images)
https://gizmodo.com/googles-plan-to-limit-ad-blocker-performance-on-chrome-1831987583
There are some numbers to back up Google ’s claim . The company says that while many unspoiled actor , like advert blockers , utilize the WWW Request API , it ’s also been abused—42 percent of malicious elongation have apparently used the web Request API since January 2018 , according to Google .
To Google ’s credit , it ’s since play with international developer on some the issues . Google ended its blog parry that Declarative final Request is “ still very much in design and development ” and that it welcome feedback from the community . Since its proposal in January , it now plan to provoke the number of rules extensions that are used to name content from 30,000 to 150,000 .
Still , developers are n’t buying it . In astatementto Wired , Ghostery President Jeremy Tillman said , “ I think they ’ve been trying to give the impression that they ’re working with the developer community , when in fact they ’re somewhat entrenched with what they desire to do . The newfangled API is not in itself a bad thing , but it becomes a uncollectible thing when it ’s the only alternative because it lacks the tractableness that the vane Requests API provides . ”
Ultimately , it boils down to whether you believe Google is n’t trying to slowly mash the life out of ad blocking agent and make its own edition . Google makes a big chunk of moolah off its ad business , so cynically speaking , it does n’t have a Brobdingnagian incentive to make thing easygoing for third - company ad blockers . Google has n’t said when Manifest V3 — the name for all the coming changes , including Declarative Net Request , will be unrecorded . It ’s more than likely Google and third - company advert blocker will come to some sort of work solution by then — but how effective it is for end users will count on whose interlingual rendition of the account you trust more .
ChromiumGoogle
Daily Newsletter
Get the best technical school , science , and culture newsworthiness in your inbox daily .
intelligence from the future , delivered to your present .
You May Also Like
