Live data from Hacker News

Proxy Chrome extensions are not going to be usable in MV3

bugs.chromium.org

131–140 of 215 posts

Re: Proxy Chrome extensions are not going to be usable in MV3

#131
post #21

Earlier quoted context omitted.

And after they specifically said: >Sorry no updates yet. Please star the bug if you wish to see this fixed sooner. Okay Google, we've starred the bug. Please fix now.

I think this is the real story here. Google pretends to be listening to real-world use-cases and user feedback and developing Chromium in the open, but at the end of the day, some manager has decided the millions of people using these extensions aren’t worth supporting, and that’s the end of the conversation.

It's not really any different for Firefox though is it? In fact it's not really any different for any big open source project. Someone ultimately has the power to decide what features to develop and nothing forces them to listen to their users.

Look at things like Firefox's Pocket integration, or like all of Gnome.

Re: Proxy Chrome extensions are not going to be usable in MV3

#132
post #116

Does this mean that (non-open-proxy) VPNs will no longer be usable on a per-Chrome-profile basis? So one would need to either route all traffic through a VPN at the OS level, or none at all?

You can still authenticate via basic auth popup, but you can’t automate it (UX friendly). There are some workarounds mentioned in the bug comments, but they are workarounds with their own issues.

Re: Proxy Chrome extensions are not going to be usable in MV3

#133
post #122
post #89

So.. Chrome is too big to fork. Then why don't we make a bare-bones OSS no-DRM browser with only a subset of JS and CSS and promote at the same time an old-school webring of 'virtous' websites. If it catches on (and it could since it'd be free and fast ), maybe some big sites would evolve to advertise themselves as 'virtous'.

Something like Ladybird? https://github.com/SerenityOS/ladybird I think it wants to implement all of JS eventually though.

  it wants to implement all of JS
ES6 why not. But the whole Web API is crazy. Bluetooth ? Barcode ? Geolocation ? What the hell. Let's go back to a documents web.

Also small JS engines already exist, like QuickJS.

Re: Proxy Chrome extensions are not going to be usable in MV3

#134
post #8

Earlier quoted context omitted.

V3 will improve performance of ads division.

Doubtful. I suspect that Google Adsense ads will continue to be blocked post-V3.

You're correct. MV3 blockers work fine against Adsense, as expected.

Re: Proxy Chrome extensions are not going to be usable in MV3

#135

Earlier quoted context omitted.

Your claim is that you suffer a _40 to 60_% performance impact by using Firefox from Chrome? Would you like to try that again? I see egregious comments like this of Firefox every so often and I always have to wonder if the last time people making these remarks actually used Firefox was in the pre-Quantum era (assuming one charitable interpretation). To claim that its performance is equivalent to using Chrome on a CPU…

I invite you to try Safari, Chrome, and Firefox on an Apple Silicon CPU right now. Firefox is the slowest of these by a HUGE margin.

Not only the slowest, it also uses the most energy of all browsers on Mac. Scrolling the old Reddit spikes the CPU to 10x more than Brave.

Re: Proxy Chrome extensions are not going to be usable in MV3

#136
post #4

As a proxy extension developer, this is absolutely maddening. We're forced to choose between auth-less open proxies (bad), or baking in a wacky authentication scheme through a side channel (also bad). MV3 drops in 2.5 months, and will leave tens of millions of proxy extension users unable to use products they paid money for. This is all on top of the many other issues with MV3 that Google is pushing under the guise o…

[deleted]

Re: Proxy Chrome extensions are not going to be usable in MV3

#137
Once upon a time many years ago, Chrome was marginally better than Firefox.

That time has long since passed.

I know, I switched from Firefox to Chrome and used it for a couple of years, but Firefox got better and Chrome got worse, so I've been back on Firefox for many years again now.

If Chrome doesn't do what you want or what you like, use Firefox. It does everything Chrome does, and more.

Re: Proxy Chrome extensions are not going to be usable in MV3

#138
post #18

Earlier quoted context omitted.

There are many legitimate use cases of VPN's. Also there are many VPN companies that don't do false advertising such as Windscribe, mullvad or iVPN.

> There are many legitimate use cases of VPN's Yes of course, but that probably represents less than 10% of the customers (I'm being extremely generous on purpose, it's probably 0.1%) of your usual NordVPN and co. > don't do false advertising such as Windscribe "Stop tracking and browse privately" and "block annoying advertisers from stalking you online" proves you wrong. VPNs don't stop trackers. > don't do false ad…

A huge portion of VPN users do it to get around geo-blocking, which has not been falsely advertised.

Re: Proxy Chrome extensions are not going to be usable in MV3

#139
Not trying to throw ML at the wall, but could it be used for this problem (considering all other options seem to be failing)?

As far as I understand, after MV3, ad blockers won't be able to use a long list of ads to remove them.

How about using a simple ML algorithm to detect whether the request is a genuine one or an advertisement? I am sure that getting training data wouldn't be too hard (all the ad lists that will get useless after MV3 are good data).

I don't make chrome extensions so I don't completely know how MV3 will cripple ad blockers.

Any feedback would be appreciated!

Re: Proxy Chrome extensions are not going to be usable in MV3

#140

Once upon a time many years ago, Chrome was marginally better than Firefox. That time has long since passed. I know, I switched from Firefox to Chrome and used it for a couple of years, but Firefox got better and Chrome got worse, so I've been back on Firefox for many years again now. If Chrome doesn't do what you want or what you like, use Firefox. It does everything Chrome does, and more.

I like Firefox and am a loyal, long term user - used it before quantum kind of loyal - but it is by far the least efficient browser on macOS with M1. In my rough personal testing Brave (based on chromium) is significantly more energy efficient, getting me up to 30% more battery time. I'm not sure why, but it's making it harder and harder to justify sticking with FF.
Post reply on HN