As Google Chrome disables uBlock Origin and other unsupported extensions, rivals like Brave and now Opera have confirmed they will support it. The latter has explained how it hopes to do so.
They mention that the shared codebase means they can add functions back in, so there’s that. To me that reads like a hard fork that they’d have to maintain independently.
I imagine that disabling V2 is as simple as setting a flag during compile, at present. Obviously as the rest of the code base progresses it will become less simple to enable V2 support.
From a marketing perspective, the smart play is to say that you’ll continue supporting uBlock Origin and keep saying that for at least the next month or so, in order to gather up some refugees from chrome. Thereafter tell every one that your built in blocker is better than uBlock Origin anyway, and then drop support for V2.
A better title: Opera explains shit on how it plans to keep uBlock Origin support. Will talk to developers so see if anyone has a good ideas.
They mention that the shared codebase means they can add functions back in, so there’s that. To me that reads like a hard fork that they’d have to maintain independently.
This is supposition but…
I imagine that disabling V2 is as simple as setting a flag during compile, at present. Obviously as the rest of the code base progresses it will become less simple to enable V2 support.
From a marketing perspective, the smart play is to say that you’ll continue supporting uBlock Origin and keep saying that for at least the next month or so, in order to gather up some refugees from chrome. Thereafter tell every one that your built in blocker is better than uBlock Origin anyway, and then drop support for V2.