4 ms·
They are not trying to kill advertisements. They want to replace API to provide better performance. That's about it. ad blocking extensions won't disappear. May
by vbezhenar 7y ago
They are not trying to kill advertisements. They want to replace API to provide better performance. That's about it. ad blocking extensions won't disappear. May be some will, and new extensions emerge.
- blep-arsh 7y agoIncidentally these new declarative rulesets are useless against some very simple tricks. I know people who are working full time on defeating ad blockers and the new Manifest v3 seems to have made their lives so much easier.
- blibble 7y agothis change is intended to move control over the blocking process from the extension author to Google once they're in total control of how the blockers can operate: I doubt they'll be responsive to what the developers of the blocking extensions want...
- pritambaral 7y ago> They want to replace API to provide better performance. The replacement API is incompatible with what it is replacing. The supposed gain in performance is not without loss in ability to block ads. > ad blocking extensions won't disappear. May be some will, and new extensions emerge. Some kinds of ad-blocking is simply impossible in the new API, without replacement or workaround. No extension can implement those methods.
- tragicpapercut 7y agoThey are killing the functionality that has supported robust adblocking for a long, long time. Any extensions that replace the current model will be less effective.
- megous 7y agoThey didn't need to replace the current API, adding a new API would have sufficed. If it was truly better, the major addons would have transitioned it voluntarily. No need to force it.
- kiwicopple 7y agoIf performance was the criteria by which they made decisions then they would probably bake ad-blocking directly into chrome, since ads/tracking is one of the leading reasons for poor performance
- bildung 7y agoBy that reasoning Microsoft didn't prevent others from writing .doc-compatible word processors either - they just defined the format as basically a memory dump of Word :) This is how a company implements measures that could be a legal problem: By formally making a technical decision and having the actual goal as a by-product of that decision.
- p_l 7y ago> By that reasoning Microsoft didn't prevent others from writing .doc-compatible word processors either - they just defined the format as basically a memory dump of Word :) It's funny because for years MS kept officially supported, feature complete, portable format for use in interchange, while DOC being shared was kinda unintended consequence that just wasn't fought against. The very requirements of the original DOC spec required it to be a memory dump.
- JohnFen 7y ago> They are not trying to kill advertisements. They want to replace API to provide better performance. So they say. I see literally no reason to believe that claim, though.