Live data from Hacker News

Proxy Chrome extensions are not going to be usable in MV3

bugs.chromium.org

101–110 of 215 posts

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

#101

It'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.

How does this decision benefit advertisers? Honest question.

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

#102
post #70

Does this impact VPN extensions like Hola VPN ?

Hola essentially puts you in a botnet (Luminati/Bright Data), you shouldn't use it.

Yeah, I know :) I just want to know if it affects them, because I hope it does :)

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

#103
post #69
post #54

Earlier quoted context omitted.

And then you realize all the web sites are optimized for chrome and you have problems using other browsers

google maps is the only site that just didn't work

And it was just a YouTube bug that killed EdgeHTML

https://news.ycombinator.com/item?id=18697824

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

#104
post #91

Earlier quoted context omitted.

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)

Yeah it's clear that was never going to work -- the whole point of dropping the old addons was making big architectural changes that weren't possible with the old APIs. You can't merge the new architectural changes and the old APIs without running into the issues they were trying to avoid by removing the old APIs in the first place.

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

#105
post #48

Earlier quoted context omitted.

>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 big…

Firefox supports all DRM content I have come across, clearly there are ways to implement DRM that don't involve Google.

Open Addons an Themes, click on Plugins, by default you should see a line that says "Widevine Content Decryption Module provided by Google Inc." . Note the Google Inc. .

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

#106
post #21
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.

">Sorry no updates yet. Please star the bug if you wish to see this fixed sooner."

Translation: my manager is blocking this; please star this so have a better chance of changing his mind.

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

#107

Earlier quoted context omitted.

It's cases such as these invalidate the "they're not acting with malice". Thousands of google employees see this stuff, and are clearly being told they can't talk about it.

You haven't applied Hanlon's Razor properly. They're just coordinating incompetence that they find beneficial, not being malicious.

Someone in authority said or inferred some version of "don't talk about this, don't get involved". That's malicious.

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

#109
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.

Firefox gives up 40-60% of the performance of Chrome on my platform, using common browser benchmarks. I don't see Firefox as a substitute good for Chrome. It has much worse performance, worse security, and lacks features I want. Its performance is equivalent to using Chrome on an 8-year-old CPU. The only thing it has going for it is being perceived as counter-cultural, despite the fact that it is 100% funded by Google.

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

#110
post #43

Earlier quoted context omitted.

VPN providers won't be able to verify if a user paid for the service.

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

Authorization and access control are different problems. You can use ssh to create a auth-free SOCKS5 pipe, for example (lots of us do this every day), but that's not an "open proxy" because it's e.g. listening on ::1 or on the internal network interface, etc...
Post reply on HN