uBlock had been castrated by Chrome. It doesn’t break entirely, but it’s been gimped severely on Chrome. Other Chrome based browsers ignore part of the Manifest V3 restrictions, but as far as I know Chrome and Edge, the most popular Chrome branches, stick with the Google standard.
are they forks? That’s what I don’t get, who controls the merge controls into Chromium’s main branch? It’s open source, but who actually says yay or nay on PRs getting in? I assume it’s Google, and the others are all forks off, but if it makes it into the main branch or not will really decide if it gets adopted
They can, but their very existence increases the Chromium engine’s market share and therefore Google’s control of the web, allowing them to do stuff like this. Once this is implemented in Chrome then these browsers will just become “Chrome but it can’t play netflix/access bank websites/etc” or whatever.
Brave calls itself a fork, which I suppose if its truly a fork, they are cherrypicking patches they can use from the chromium base, rather than recompiling with their own patch set on top
Goggle standard approach to it, is to integrate it so much with other components that it will be a lot of work to disable it, eventually making it impractical.
The right way would be for those clients to switch to gecko engine.
deleted by creator
Most people don’t give a shit about these things. It might actually decrease if Netflix just tells people to install Chrome to watch Stranger Things
That’s what people said about Manifest v3. Turns out most people don’t care.
I don’t care about Manifest V3. I care about ublock origin.
When that stops working, then I’ll swap.
uBlock had been castrated by Chrome. It doesn’t break entirely, but it’s been gimped severely on Chrome. Other Chrome based browsers ignore part of the Manifest V3 restrictions, but as far as I know Chrome and Edge, the most popular Chrome branches, stick with the Google standard.
No, not yet. Existing extensions that use manifest V2 are still supported.
Aren’t Vivaldi and Brave downstream of chromium though 🤔
Vivaldi and Brave can modify Chromium to disable this feature. Chromium is open source after all.
are they forks? That’s what I don’t get, who controls the merge controls into Chromium’s main branch? It’s open source, but who actually says yay or nay on PRs getting in? I assume it’s Google, and the others are all forks off, but if it makes it into the main branch or not will really decide if it gets adopted
You can have your own set of patches (and/or config) and still stay up to date with upstream.
You don’t need to do a hard fork to modify it for your needs.
They can, but their very existence increases the Chromium engine’s market share and therefore Google’s control of the web, allowing them to do stuff like this. Once this is implemented in Chrome then these browsers will just become “Chrome but it can’t play netflix/access bank websites/etc” or whatever.
Brave calls itself a fork, which I suppose if its truly a fork, they are cherrypicking patches they can use from the chromium base, rather than recompiling with their own patch set on top
Goggle standard approach to it, is to integrate it so much with other components that it will be a lot of work to disable it, eventually making it impractical.
The right way would be for those clients to switch to gecko engine.