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.
Proxy Chrome extensions are not going to be usable in MV3
101–110 of 215 posts
Re: Proxy Chrome extensions are not going to be usable in MV3
#102Re: Proxy Chrome extensions are not going to be usable in MV3
#103Earlier 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
Re: Proxy Chrome extensions are not going to be usable in MV3
#104Earlier 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)
Re: Proxy Chrome extensions are not going to be usable in MV3
#105Earlier 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.
Re: Proxy Chrome extensions are not going to be usable in MV3
#106Chromium 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.
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
#107Earlier 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.
Re: Proxy Chrome extensions are not going to be usable in MV3
#108Re: Proxy Chrome extensions are not going to be usable in MV3
#109So.. 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
#110Earlier 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.