Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Proxy Chrome extensions are not going to be usable in MV3

bugs.chromium.org

Post reply on HN
Print view View original

91–100 of 215 posts

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

#91

Post by UberFly »

cpeterso wrote: post #64
imbnwa wrote: post #60

Earlier quoted context omitted.

Brave has publicly declared support for Manifest v2 in perpetuity, no? They even seem to be pondering how to distribute v2 extensions post-sunset in Google Chrome[0] [0] https://github.com/brave/brave-browser/issues/15187

Maintaining out-of-tree patches for a project as large and quickly-changing as Chromium will be a lot of work. I know someone who worked on Amazon's Silk browser team and they had an engineer (rotation) working working full-time to keep their Chromium fork up to date within Google's upstream. Brave doesn't have nearly the resources that Amazon does.

Yea you've seen it tried in projects like Waterfox and Palemoon and it eventually becomes too much to deal with. (Following the old Firefox addons system that is)

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

#92

Post by MatthiasPortzel »

aftbit wrote: post #21
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.

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.

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

#93

Post by marwis »

cpeterso wrote: post #64
imbnwa wrote: post #60

Earlier quoted context omitted.

Brave has publicly declared support for Manifest v2 in perpetuity, no? They even seem to be pondering how to distribute v2 extensions post-sunset in Google Chrome[0] [0] https://github.com/brave/brave-browser/issues/15187

Maintaining out-of-tree patches for a project as large and quickly-changing as Chromium will be a lot of work. I know someone who worked on Amazon's Silk browser team and they had an engineer (rotation) working working full-time to keep their Chromium fork up to date within Google's upstream. Brave doesn't have nearly the resources that Amazon does.

There are few projects and companies that do exactly that, including CEF open source project. Perhaps they should join forces and make a joint OpenChromium project.

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

#94

Post by vlunkr »

lolinder wrote: post #80
LegitShady wrote: post #76

Earlier quoted context omitted.

I use firefox every day without issue.

I use it every day as my primary browser, but there's definitely been an increase in applications that will not work except on Chrome. It's not text content that's ever the issue, it's SaaS products.

It's your anecdote vs. mine, but this is not my experience. I find that Chrome is better for Google Meet (not surprising.) Other than that FF is fine. In the last 4-5 years have become increasingly similar and easy to support as a developer.

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

#95

Post by miohtama »

_aizw wrote: post #63
TedDoesntTalk wrote: post #55

Earlier quoted context omitted.

Not just VPN providers or other paid services. Open proxies on the internet are bad for everyone.

What are the other issues with open proxies?

Cyberattacks use open proxies to amplify the attack/hide their source.

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

#96

Post by TremendousJudge »

alcover wrote: 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'.

I don't get it, Firefox already exists and is a complete OSS reimplementation of everything Chrome does (and works better imo). Only thing to do is convince sites to test more on Firefox. This strategy worked last time around.

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

#97

Post by TremendousJudge »

jorvi wrote: post #77
pkulak wrote: post #36

Earlier quoted context omitted.

And every time there's a bunch of replies about how great Brave is, and everyone should just use that... Chromium wrapper.

To be honest, I don’t understand why people keep acting like Google has control over Chrome(ium) with some iron fist. It’s dual open license. Microsoft is contributing so many patches that they have a decent amount of sway over it already. If Google ever truly steps over the line, Microsoft will just fork it and everyone will swap their upstream to Microsoft-Chromium..

I don't think Microsoft has any incentives to protect users.

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

#98

Post by agilob »

MatthiasPortzel wrote: post #92
aftbit wrote: 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.

opensource coming from Google, Amazon, Microsoft, OpenAI or even recent garbage coming from RedHat is just a nice facade. It's broken, it's locked to a platform, often no compiling instructions or out of date by 3 years with multiple bug reports. It's just a marketing move that came from Google early 00s' and then was widely adopted by MS: "Microsoft <3 OpenSouce - Contribute Here (for us for free, we can't be bothered to fix this TOP 10 bug or update documentation)".

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

#99

Post by TheChaplain »

MatthiasPortzel wrote: post #92
aftbit wrote: 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 about support, it's a money issue. Adblocking doesn't generate money, so out it goes.

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

#100

Post by lizardactivist »

I don't know the full scope of consequences and Google's reasoning for this, but I'm going to guess it's either done under the false pretenses of improving performance, or improving security. Could there possibly be a positive outlook for improving ad revenue as well?

Time to settle with Firefox.

Post reply on HN