{"id":25749,"date":"2019-06-21T17:38:08","date_gmt":"2019-06-21T21:38:08","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=25749"},"modified":"2025-07-04T16:50:39","modified_gmt":"2025-07-04T20:50:39","slug":"chrome-to-limit-ad-blocking-extensions","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/06\/21\/chrome-to-limit-ad-blocking-extensions\/","title":{"rendered":"Chrome to Limit Ad Blocking Extensions"},"content":{"rendered":"

Kyle Bradshaw<\/a> (via Eva<\/a>):<\/p>\n

\n

Google is essentially saying that Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. This is likely to allow enterprise customers to develop in-house Chrome extensions, not for ad blocking usage.<\/p>\n

For the rest of us, Google hasn’t budged on their changes to content blockers, meaning that ad blockers will need to switch to a less effective, rules-based system, called “declarativeNetRequest.”<\/p>\n<\/blockquote>\n\n

Justin Schuh<\/a> (via Dan Masters<\/a>):<\/p>\n

\n

The sole motivation here is correcting major privacy and security deficiencies in the current system. I know, because I set that focus, and the team reports up through me. And here’s a bit more context on the uBlock assertions.<\/p>\n<\/blockquote>\n\n

Justin Schuh<\/a>:<\/p>\n

Chrome does let sysadmins manage things beyond user-facing settings (without paying anyone anything!). That’s because enterprises have complex needs and admins responsible for assessing security, privacy, and perf tradeoffs that we can’t foist on the average user.<\/p>\n

Then there’s the uBlock Origin arguments. The big problem with webRequest is unfixable privacy and security holes. They ignored that to solely argue perf, but then ignored the biggest perf cost of every webRequest extension stacking a full renderer process, blocking IPC, etc.<\/p><\/blockquote>\n\n

Simeon Vincent<\/a>:<\/p>\n

\n

Each of these groups has their own distinct maximum number of allowed rules. These current placeholder max values are specified in the DNR properties documentation. We are planning to raise these values but we won’t have updated numbers until we can run performance tests to find a good upper bound that will work across all supported devices.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n