Makers of ad blockers and browser privacy extensions fear the end is near | Hacker News Reader

Makers of ad blockers and browser privacy extensions fear the end is near

theregister.com

36 pointssidcool22 comments

This is why everyone should be using Firefox, the only viable open source browser that cares about the open web and privacy.

And supports fuck all upcoming web features, disqualifying it as a browser for any serious tinkering.

Which ones is it lacking? Haven't missed anything personally

https://caniuse.com/?compare=firefox+101,chrome+102&compareC...

For me personally, I would live Web Bluetooth to be supported (However its classed as a experimental technology), however until its supported in Safari iOS I'm not going to loose any sleep over it being missing.

How about sqlite? wouldnt you like to have this as a standard? Mozilla killed it.

Like tracking users anywhere and everywhere, and reporting to mothership?

Like @property, which has been around for years now

Import-Maps is another very important one.

Unfortunately this is one of the things Firefox actually does very well even when you explicitly disable telemetry.

But does it consolidate my data all over the devices and the web, tie to my real world identity, and feed to advertisers?

Yet another reason to use only Firefox.

Firefox Mobile supports uBlock Origin too!

How many billions in profit is enough? If adblockers stop working in Chrome, people (me included) are still not going to see ads, and we won't be using Chrome either.

I get that business becomes gamified to try and squeeze the most profit as possible. It happens because the big wigs only look at the numbers, and it's not anyone in particulars fault. I can imagine a new manager of sorts trying to make a name for themselves in a big company such as Google, suggesting that stopping ad blockers could make X Million $ more per year and they might even get a promotion for it.

$title = $title + „for Chrome users“.

Thanks, you saved me a click.

$title = $title + "for Chromium users". Which is almost everyone. Although does Safari use something similar? I think only FF will be using Manifest v2.

Safari will continue supporting v2 for now.

Including on iOS? I thought that they never supported v2 on iOS and only moved to something similar to v3.

"The most widely noted change in Mv3 – and there are many that have significant implications – is the removal of the blocking version of the webRequest API, which is being replaced by an API called declarativeNetRequest."

Safari supports and will continue to support v2, but Safari never supported blocking webRequest.

Thanks. That aligns with my fuzzier understanding.

It sounds like they don't support persistent background pages, for power usage reasons probably, so extensions have to adopt to that.

I imagine that Brave, Vivaldi, etc. will still allow Manifest V2?

Vivaldi already announced that they will not support v2 because of the engineering costs. I don't know if Brave will for the same reason and they also want you to use their integrated ad block

Reply on news.ycombinator.com