Proxy Chrome extensions are not going to be usable in MV3 • Hacker News Board

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

#21

Post by aftbit » Mon, Sep 19, 2022, 5:13 PM UTC

olso wrote: post #2

Chromium team has not commented on this bug with 650+ stars (within top 10 https://bugs.chromium.org/p/chromium/issues/list?sort=-stars... issues) in months

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.

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

#22

Post by s_ting765 » Mon, Sep 19, 2022, 5:14 PM UTC

I thought they were pushing it when they announced MV3, which would purposely can ad blockers. But this would finally put the nail to this coffin.

Now I'm even more curious to see how badly Chromium bangles this migration to V3.

I'm also curious as to why big internet advocacy organizations such as the EFF [0] have been quiet on this move.

--

Edit: It appears the EFF has spoken out about this a couple of times.

[0] https://www.eff.org/deeplinks/2021/12/googles-manifest-v3-st...

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

#23

Post by jerheinze » Mon, Sep 19, 2022, 5:15 PM UTC

TedDoesntTalk wrote: post #17

jerheinze wrote: post #15

Earlier quoted context omitted.

It's not like no one was making warnings about this.

Someone warned years ago that proxy extensions would no longer be feasible on Chromium? I must have missed that message.

Not that explicitly, but many warned about Google abusing their power if it started hitting their profits.

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

#24

Post by moffkalast » Mon, Sep 19, 2022, 5:15 PM UTC

TedDoesntTalk wrote: post #17

jerheinze wrote: post #15

Earlier quoted context omitted.

It's not like no one was making warnings about this.

Someone warned years ago that proxy extensions would no longer be feasible on Chromium? I must have missed that message.

I'm more interested why it isn't possible to just fork the thing and maintain a version that's plugin enabled. Isn't Chromium completely open source?

Especially for Brave, Vivaldi, Opera, etc.

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

#25

Post by aftbit » Mon, Sep 19, 2022, 5:15 PM UTC

yegor wrote: 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…

Have any of the Chromium forks committed to maintain MV2 into the future? Having functioning extensions while maintaining the other features that people like from the browser could help pull some marketshare from Google Chrome. Probably just dreaming though...

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

#26

Post by forgotusername6 » Mon, Sep 19, 2022, 5:15 PM UTC

Has someone tried to fix this themselves yet?

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

#27

Post by AshamedCaptain » Mon, Sep 19, 2022, 5:15 PM UTC

moffkalast wrote: post #24

TedDoesntTalk wrote: post #17

Earlier quoted context omitted.

Someone warned years ago that proxy extensions would no longer be feasible on Chromium? I must have missed that message.

I'm more interested why it isn't possible to just fork the thing and maintain a version that's plugin enabled. Isn't Chromium completely open source? Especially for Brave, Vivaldi, Opera, etc.

Developer effort.

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

#28

Post by vlunkr » Mon, Sep 19, 2022, 5:15 PM UTC

superkuh wrote: post #7

I don't want to pile on here but everyone who used Chromium while pretending they weren't supporting google's Chrome monopoly, pretending Chromium was something else, are getting the only outcome that was possible. It was entirely predictable from the start and if you play stupid games you win stupid prizes.

And the stupid prize is what? You might have to use a different browser? Doesn't seem that serious to me.

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

#29

Post by moffkalast » Mon, Sep 19, 2022, 5:16 PM UTC

AshamedCaptain wrote: post #27

moffkalast wrote: post #24

Earlier quoted context omitted.

I'm more interested why it isn't possible to just fork the thing and maintain a version that's plugin enabled. Isn't Chromium completely open source? Especially for Brave, Vivaldi, Opera, etc.

Developer effort.

Don't underestimate the power of spite.

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

#30

Post by TedDoesntTalk » Mon, Sep 19, 2022, 5:16 PM UTC

staticassertion wrote: post #19

TedDoesntTalk wrote: post #16

Earlier quoted context omitted.

> A proxy extension requires rewriting arbitrary requests on the fly That is completely incorrect. A proxy extension routes requests through a proxy server. It does not rewrite anything.

OK and presumably it does that by taking a request for an address A and rewriting part of it so that it actually goes to B with some additional headers to indicate how to forward it. edit: Apparently I've hit my HN rate limit so I can't reply! Thanks Dang. As for the proxying, obviously something has to rewrite the address that the request is going to. Depending on the type of proxy (ex: HTTP CONNECT) you may also ha…

I mean, you are just completely wrong. It does not rewrite the request. It does not change headers. There is an API that allows the extension to set a proxy server destination:

https://developer.chrome.com/docs/extensions/reference/proxy...

And that API does not change the request, either. That is not how proxying works.