Absolutely clickbait. Nothing in the article suggests that review times are increasing, they’ve always been “from a few minutes to a few days”.
Also filters do not depend on extension updates at all, they are plain text files that can be updated at any time. Not to mention that they can contain “scriptlets”, which make them quite literally “remotely hosted code” and still allowed by MV3 (because they’re not raw JavaScript)
> We've covered this already. But we haven't talked about the other side of the equation: Ad block rules can't be updated quickly anymore. Today, ad blockers and privacy apps can ship filter list updates themselves, often using giant open-source community lists. Manifest V3 will stop this by limiting what Google describes "remotely hosted code." All updates, even to benign things like a filtering list, will need to happen through full extension updates through the Chrome Web Store. They will all be subject to Chrome Web Store reviews process, and that comes with a significant time delay.
If this is factually incorrect, it would absolutely warrant a correction to the article.
> If this is factually incorrect, it would absolutely warrant a correction to the article.
It is incorrect. MV3 definition updates go through an automated fast-track process for safe rules. See the presentation[1] and Q&A[2] at the recent Ad Blocking Summit.
I wouldn't hold my breath on a correction. Ron never corrects his articles, like when he confused the Privacy Sandbox with the Topics API a couple months ago[3].
Then it would make sense to write such articles if and when that happens. Until that point, the claims being made in this article are simply incorrect.
The only real part is that MV3 does not allow actual remote JS to be run on web pages. However you could still run it in a sandboxed iframe (not super helpful to adblockers though)
Also filters do not depend on extension updates at all, they are plain text files that can be updated at any time. Not to mention that they can contain “scriptlets”, which make them quite literally “remotely hosted code” and still allowed by MV3 (because they’re not raw JavaScript)