Chromium is going to remove all the MV2 APIs from Chromium's code.
When a Chromium fork will have to add itself all the MV2 code at least twice a month... it's just won't an option from browsers with limited resources.
Only Microsoft has the resources to add back all this code and test it if it works properly so frequently. Not Opera, not Vivaldi, not Brave etc.
Just tweaking the flags like they do now won't be enough in future when Chromium removes all the MV2 code from Chromium.
The distribution of an extension was never the issue.
I will never use a crypto browser from a shady company because it has a built in adblocker. I am not that desperate and I do care about the ethics of the browser I use.
Adguard is the way to go, the app, not the MV3 extension combined with Adguard assistant extension for controlling everything directly in my browser.
I prefer paying 10 bucks for a lifetime license of Adguard than ending up using shady crypto browsers for an adblocker.
No, Statcounter can detect browsers even if they use Chrome's user agent.
For example Brave which uses Chrome's user agent is detected with window.navigator.brave it adds in every HTML it loads.
Brave adds it in order to be detected from sites which serve ads from Brave's ad company though Brave Rewards.
No, StatCounter can find out the browser even if it uses Chrome's user agent.
Even browsers which use Chrome's user agent like Brave can be found.
Brave can be found with the window.navigator.brave it adds in every HTML it loads.
Brave adds it in order to be detected from sites which serve ads from Brave's ad company though Brave Rewards.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now