Does anyone know when MV3 will be released, or when this will start to impact a large # of users?
MV2 will be disabled by default Chrome in January 2023, and the flag to reenable it will be removed in June
Proxy Chrome extensions are not going to be usable in MV3
41–50 of 215 posts
Re: Proxy Chrome extensions are not going to be usable in MV3
#42btw just like there were enterprise-hacks for Windows v7 to keep it going, manifest v2 will still work if users can be taught to turn on "managed mode" in their Chrome
extends v2 from January 2023 EOL until June 2023
January 2023
Chrome stops running Manifest V2 extensions
Enterprise policy can let Manifest V2 extensions run on Chrome deployments within the organization.
June 2023
Manifest V2 extensions no longer function in Chrome even with the use of enterprise policyRe: Proxy Chrome extensions are not going to be usable in MV3
#43As 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…
Why will auth-less open proxies be bad?
VPN providers won't be able to verify if a user paid for the service.
Re: Proxy Chrome extensions are not going to be usable in MV3
#44Does this impact VPN extensions like Hola VPN ?
Re: Proxy Chrome extensions are not going to be usable in MV3
#45As 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…
If there is one group of people I will never feel bad for, it's the VPN / proxy vendors. They've been doing false advertising for years on every channel, making consumers pay for absolutely useless products.
There's absolutely terrible players in the space.
We're also in the space, I don't think we're selling useless products, or falsely advertising.
Our customers use our proxy servers to test applications that use your IP address to show you localized content (IP Location, GeoIP, etc). We're in 80+ countries 250+ locations globally.
Being able to switch your location with a browser plugin makes it just a few clicks, and _much_ faster than switching VPN endpoints. You also get to proxy just your browser traffic (or even just traffic against a few specific domains) rather than all the traffic on your machine. So your Spotify/Slack/Outlook connections can all run normally, and you're only proxying the site you want to test from somewhere else.
This change is terrible for us. Especially so because users flipping around between different proxies is a major use case. A user needing to re-enter their credentials for each unique proxy server is much worse than just once.
Re: Proxy Chrome extensions are not going to be usable in MV3
#46As 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…
Is there really nowhere else to store Auth information in a synchronous datastore?
For example it looks like you could use a lambda function with the Auth info pre-bound...
Re: Proxy Chrome extensions are not going to be usable in MV3
#47Earlier quoted context omitted.
If there is one group of people I will never feel bad for, it's the VPN / proxy vendors. They've been doing false advertising for years on every channel, making consumers pay for absolutely useless products.
There's absolutely terrible players in the space. We're also in the space, I don't think we're selling useless products, or falsely advertising. Our customers use our proxy servers to test applications that use your IP address to show you localized content (IP Location, GeoIP, etc). We're in 80+ countries 250+ locations globally. Being able to switch your location with a browser plugin makes it just a few clicks, and…
How are you planning to adapt to the change?
Re: Proxy Chrome extensions are not going to be usable in MV3
#48Earlier 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.
>Isn't Chromium completely open source?
No, especially not if you want to watch videos, the DRM plugin is a binary blob that only Google approved browsers get to run.
Then there are all the Google services that will break in unexpected ways in your browser, sometimes just because your user agent isn't identical to Chromes if past reports from Firefox users are any indication. Basically expect to be shit on by the biggest internet giant around at ever possible corner.
Re: Proxy Chrome extensions are not going to be usable in MV3
#49It's extremely frustrating how Google is ignoring this issue. So much for developer relations.
This type of decision has fully cemented that Google is an advertising company. Every decision they make is to benefit advertisers regardless of how it affects users and developers.
Re: Proxy Chrome extensions are not going to be usable in MV3
#50As 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…
Does your extension work on Firefox? If yes, have you considered explaining the situation to your users to encourage them to move to Firefox?