Are we going to lose ublock origin on chrome when v2 will be disabled?
Unless they port it to v3, yes, it won’t work anymore.
It's not looking hopeful https://github.com/uBlockOrigin/uBlock-issues/issues/338
AdGuard publishes the first ad blocker built on Manifest V3
11–20 of 371 posts
Re: AdGuard publishes the first ad blocker built on Manifest V3
#12Earlier quoted context omitted.
Jeeezuuuss! that will hurt, a lot.
Meh, just use Firefox for general browsing and Chrome/ium for the one or two things that only work on that.
It's shocking that in 2022 there are still sites that (or have been forced) to only work in Chrome.
Looking at you Google search results [1] (but I understand their motivation), however I do have one local company site that refuses to move beyond their loading splash in Firefox.
I guess I should be thankful it's no where near as bad as the IE6 days where HTML standards were completely disrespected in the quest for more market share.
[1]: https://addons.mozilla.org/en-US/android/addon/google-search...
Re: AdGuard publishes the first ad blocker built on Manifest V3
#13Re: AdGuard publishes the first ad blocker built on Manifest V3
#14Re: AdGuard publishes the first ad blocker built on Manifest V3
#15> By releasing an extension built with Manifest V3 today — first among developers of ad blockers – we can say that we've met the challenge that Google posed to us. They shouldn't do this IMHO. Manifest V3 is a horrible attempt to kill adblocking (under the banner of "security", as always). But, the web is completely unusable without adblocking. If there are no more (effective) adblockers for Chrome, users will franti…
It’s got me thinking about selling my Google stock. A move like this feels a little bit desperate.
Re: AdGuard publishes the first ad blocker built on Manifest V3
#16It is such a bummer to me that Firefox is implementing MV3 and deprecating MV2[1]. Internet Explorer 6 never left, it just became Google Chrome*.
Vivaldi? Killed, Chrome clone. Edge? Killed, Chrome clone. Brave? Killed, Chrome clone. Firefox? Technically a separate engine and in theory among the last hopes, but so sclerotic it follows Chrome in almost all of its decisions. (Can MV2 be kept as a stable basic-security-maintenance-only API? Probably not) Safari? Can be gone around on desktop (my grandparents use Chrome because of Google prompts), has a stranglehold on mobile, but that has its own problems, and likely once users can ~sideload~ install software (potentially from other app stores), there will be a Chrome surge on mobile, forcing manifest V3 over there too, and the ad trackers will win the war.
Or maybe they already have? More likely, I personally am tiring of the cat and mouse game between the spyware makers and devs that fight for the users.
[1] UPDATE: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi... PREVIOUSLY: https://blog.mozilla.org/addons/2022/06/08/manifest-v3-firef...
* In the sense that one browser implementation, and not W3C or WHATWG web standards, drives the web browser market. Chrome is much more evergreen than IE.
Re: AdGuard publishes the first ad blocker built on Manifest V3
#17Earlier quoted context omitted.
Meh, just use Firefox for general browsing and Chrome/ium for the one or two things that only work on that.
It's shocking that in 2022 there are still sites that (or have been forced) to only work in Chrome. Looking at you Google search results [1] (but I understand their motivation), however I do have one local company site that refuses to move beyond their loading splash in Firefox. I guess I should be thankful it's no where near as bad as the IE6 days where HTML standards were completely disrespected in the quest for mo…
User agent spoofing seems like what should be done on the user's end in those cases, if it's not possible to avoid using such sites for whatever reason.
Problems would begin once we'll eventually get Chrome-specific functionality or something that Mozilla won't implement due to a variety of concerns, thus simply breaking sites: https://mozilla.github.io/standards-positions/
Then we'll basically be back in the days of IE, except that this time Google will be the ones with the browser monopoly, if we're not already there somewhat - the majority of folks haven't even heard of Firefox.
Re: AdGuard publishes the first ad blocker built on Manifest V3
#18Earlier quoted context omitted.
Jeeezuuuss! that will hurt, a lot.
I use firefox so i don't know much about chrome vs chromium politics, but if the chromium people have one thing to do now, it would be to maintain manifest v2 in their fork..
chromium people are chrome people. google provide chromium either as a literal requirement for compliance with some other open source licence, or as a vestige from the “don’t be evil” days.
Re: AdGuard publishes the first ad blocker built on Manifest V3
#19> By releasing an extension built with Manifest V3 today — first among developers of ad blockers – we can say that we've met the challenge that Google posed to us. They shouldn't do this IMHO. Manifest V3 is a horrible attempt to kill adblocking (under the banner of "security", as always). But, the web is completely unusable without adblocking. If there are no more (effective) adblockers for Chrome, users will franti…
I think you overestimate the role adblockers play for regular users. Most people not affiliated with IT in any way I've met actually don't use an adblocker or have forgotten that they in fact do and would not notice the change to Manifest v3.
Also, most people care much more about "it simply works", and that is Chrome. Firefox is neither preinstalled nor as compatible as Chrome (nor as fast or user friendly). There's already a lot of popups like "this site works best in Chrome".
Re: AdGuard publishes the first ad blocker built on Manifest V3
#20Earlier quoted context omitted.
Jeeezuuuss! that will hurt, a lot.
Meh, just use Firefox for general browsing and Chrome/ium for the one or two things that only work on that.
> Chrome/ium for the one or two things that only work on that
Firefox has been my daily driver for close to a decade, and I've not run into something that didn't work on it, but worked on Chrome.