4 ms·
I never said it wasn't important, but it is misinformation. Case and point: to answer your question, no, those aren't limitations on DOM-manipulation ad removal
by LordDragonfang 3y ago
I never said it wasn't important, but it is misinformation. Case and point: to answer your question, no, those aren't limitations on DOM-manipulation ad removal; those are limitations on the new declarativeNetRequest API, and they ONLY apply to blocked web requests.
Also, even that part isn't as catastrophic as you'd think; ad blocking, like most things on the internet, roughly follows the 90-10 rule: 90% of the ads are blocked by 10% of the rules. So even with a tenfold reduction, you should still see the vast majority of the ads blocked by even the intentionally-gimped declarativeNetRequest API.
Yes, it's going to make ad blockers slightly less effective and make your page loads slightly slower. But that doesn't get as many clicks as "Chrome is banning adblockers!!1". And it's important to note the difference because when v3 rolls around, all those users that were lied to are going to see that their ad blockers still mostly work, and lose even more trust in whistle blowing.
- croes 3y ago>Chrome is banning adblockers You forgot the part where Google postponed the original timetable for the deprecation of manifest v2. Without that postponement, developers would not have had enough time to change the extension so that there would have been a time when adblockers were banned. The outcry prevented that.