Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by jeanlucas on Monday October 07, 2024 @06:08PM
(#41771579)
It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO
[ Parent
| on HN ]
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by TheGlav on Monday October 07, 2024 @06:36PM
(#41771842)
It's not if. It's when. It has been 'when' since 2020. It is coming. It is not going to not come. It will be here in mere releases. Get ready.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by chrisfosterelli on Monday October 07, 2024 @07:22PM
(#41772175)
You're probably right, but FWIW it's not unheard of for google to announce, continually delay, and eventually completely backtrack on things like this, like third party cookie deprecation.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by zarzavat on Monday October 07, 2024 @07:38PM
(#41772289)
This time it affects their bottom line in a profound way so wishful thinking is probably not going to work unfortunately.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by Terretta on Monday October 07, 2024 @07:49PM
(#41772346)
> affects their bottom line in a profound way
Something around 8% of total digital ad spend.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by sebastialonso on Monday October 07, 2024 @08:00PM
(#41772432)
To be fair, that's tremendous
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by timbowhite on Monday October 07, 2024 @10:22PM
(#41773240)
Source?
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by sunaookami on Wednesday October 09, 2024 @05:42AM
(#41786055)
>third party cookie deprecation
It's because they were literally sued and are not allowed to remove it, not because they don't want to.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by jeanlucas on Monday October 07, 2024 @06:49PM
(#41771935)
Yeah, hence why I started already migrating, slowly.
I have a simple tab organizer extension and some greasemonkey scripts that should work perfectly fine on Firefox without any changes.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by godzillabrennus on Monday October 07, 2024 @06:57PM
(#41772003)
I am switching family over to Brave. They don’t even notice the difference and I’m more confident the browser will continue to support user centric content filtering.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by capitainenemo on Monday October 07, 2024 @07:08PM
(#41772082)
Which is fine so long as what they have built into the browser is all you need (and so long as Google does not sabotage those efforts). If ever you might need more such as what uBO offers, though, Brave is also subject to whatever changes Google makes (such as Manifest V3).
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by WD-42 on Monday October 07, 2024 @07:35PM
(#41772271)
Is that going to help? Brave is still blink. They might have some filtering baked in but I’m not sure if it’s as powerful (or can be) as UBO.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by xelamonster on Monday October 07, 2024 @08:06PM
(#41772473)
I don't think the new manifest rules are because of any actual restriction or the engine, maybe I'm wrong but it was my impression that the change is mostly just Google wanting to control what users can do with their browsers even more (and always in ways that make them profit of course). So they should be able to keep V2 support if they're willing to be on the hook for keeping it maintained themselves.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by capitainenemo on Monday October 07, 2024 @08:53PM
(#41772747)
And if the removal of manifest v2 allows google to abandon/remove/refactor code exposed through it (and google could even be inclined to do so deliberately)? At some point Brave would end up having to maintain its own fork, which they probably don't have the resources to do.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by smallerize on Monday October 07, 2024 @07:41PM
(#41772304)
Brave will keep Manifest V2 compatibility as long as they can, specifically focusing on "AdGuard AdBlocker, NoScript, uBlock Origin, and uMatrix". https://brave.com/blog/brave-shields-manifest-v3/
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by WD-42 on Monday October 07, 2024 @07:57PM
(#41772408)
I guess I'm curious what "as long as they can" actually means. If it means they can't pull upstream Blink without losing v2 support, that's bad.
I think Firefox is the only viable solution to continue using UBO at this point.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by EasyMark on Tuesday October 08, 2024 @09:51AM
(#41777379)
I seem to recall they said as long as it was technically AND economically feasible. It depends on how much google attempts to spread the cancer of mv3 throughout their code base. Eventually brave won’t have the manpower to hack v2 in is the likely result without going bankrupt if google really wants to go down that path.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by c2h5oh on Monday October 07, 2024 @06:45PM
(#41771912)
It's already axed in canary release
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by jeanlucas on Monday October 07, 2024 @06:50PM
(#41771948)
I'm still at the "This extension may soon no longer be supported" warning
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by Technetium on Tuesday October 08, 2024 @01:11PM
(#41779498)
2 days ago: "Chrome Canary just killed uBlock Origin and other Manifest V2 extensions" https://news.ycombinator.com/item?id=41757178
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by altdataseller on Monday October 07, 2024 @06:59PM
(#41772020)
For those unaware, what is uBO and how would it affect most extensions?
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by testfrequency on Monday October 07, 2024 @07:30PM
(#41772237)
Maybe it’s a telling sign of the new wave of HN users, but I’m genuinely surprised to read that you don’t know what uBlock is..
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by jeanlucas on Tuesday October 08, 2024 @12:30AM
(#41773839)
I'm happy youngsters still use this ol' forum
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by EasyMark on Tuesday October 08, 2024 @09:54AM
(#41777403)
It’s good that we are still getting Youngbloods who see the superiority of text in communications rather than one sided talking head videos.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by OkGoDoIt on Monday October 07, 2024 @07:16PM
(#41772137)
uBO (uBlock Origin) is a popular open source ad blocker. There is a change coming to the way Google Chrome and some other browsers host extensions called manifest v3, which for (stated) security and privacy purposes limits a lot of the functionality that makes ad blockers work the way they do. There are workarounds but they are suboptimal. This has been an ongoing fight for years and there are plenty of accusations that Google is doing this because they want to cripple ad blockers since they make so much money from advertising. Firefox has explicitly stated they will not force these changes on extension developers, and thus a lot of people have been threatening to move to Firefox whenever Google finally makes this change for real.
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by cholmon on Monday October 07, 2024 @07:08PM
(#41772078)
"uBO" is an abbreviation of "uBlock Origin".
Re:uBlock Origin supports filtering CNAME cloaking sites on ...
by sureIy on Tuesday October 08, 2024 @10:09AM
(#41777554)
> I'm already rewriting my extensions to firefox
What does that mean? Firefox uses the same API. At most you have to change `background.service_worker` to `background.scripts` (literally just rename the key)