News for hackers. Stuff that matters.

A comment on Chrome's next weapon in the War on Ad Blockers: Slower extension updates. Parent comment

Re:Chrome's next weapon in the War on Ad Blockers: Slower ex... by Dylan16807 on Saturday December 02, 2023 @11:43AM (#38499848)
The article is claiming that lists won't be able to self-update at all. That goes far beyond a ban on remote JS.

> cosmetic filters updates do not require an extension update

Cosmetic meaning what exactly?

> remote JS was never allowed in Mozilla Addons store

I don't see any issues with ublock in firefox, so what's going on there?

> A little bit more research and one can learn about the no-review-fast-track that Chrome WebStore plans to implement next year.

That sounds like something that can and will randomly stop approving ad blocker updates more than once.

[ Parent | on HN ]
Re:Chrome's next weapon in the War on Ad Blockers: Slower ex... by ameshkov on Saturday December 02, 2023 @12:08PM (#38500039)
> Cosmetic meaning what exactly?

Filter lists are composed of two types of rules: “cosmetic” and “network”. Network rules define what needs to be done with web requests (block or redirect). In MV3 these rules should now be implemented via new declarative API.

Cosmetic rules is a very wide subset of ad blocking rules that define how a web page needs to be changed. These are implemented the old way.

> I don't see any issues with ublock in firefox, so what's going on there?

uBlock Origin does not use remote JS so yeah, what’s going on with the article is a good question.

[ Parent | on HN ]
Re:Chrome's next weapon in the War on Ad Blockers: Slower ex... by ameshkov on Saturday December 02, 2023 @11:58AM (#38499947)
The article’s claim is factually incorrect, self-update will also still be possible to implement even without the fast track. It will be more complicated than it is now as we’ll need to do that via differential updates, but nevertheless.
[ Parent | on HN ]