News for hackers. Stuff that matters.
Re:Proxy Chrome extensions are not going to be usable in MV3 by jerheinze on Monday September 19, 2022 @01:08PM (#32901037)
It's not like no one was making warnings about this.
Re:Proxy Chrome extensions are not going to be usable in MV3 by pkulak on Monday September 19, 2022 @01:21PM (#32901197)
And every time there's a bunch of replies about how great Brave is, and everyone should just use that... Chromium wrapper.
Re:Proxy Chrome extensions are not going to be usable in MV3 by jorvi on Monday September 19, 2022 @03:03PM (#32902468)
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..
Re:Proxy Chrome extensions are not going to be usable in MV3 by TremendousJudge on Monday September 19, 2022 @03:49PM (#32903020)
I don't think Microsoft has any incentives to protect users.
Re:Proxy Chrome extensions are not going to be usable in MV3 by jacooper on Monday September 19, 2022 @05:03PM (#32903930)
Mozilla only has themselves to blame.

I'm going to repost a previous comment here.

> https://news.ycombinator.com/item?id=32741481

> I used to refuse Chromium for the Same reason.

> But honestly it already happened, Firefox is already irrelevant.

> Mozilla is mis-managed organization that is funded to avoid anti-trust investigations, they dont fully push for privacy because they are afraid of google, do out of touch changes, and focus on political advocacy.

> Compare that to brave, which builds its own independent search engine, ad network, and has privacy by default in its products.

>There is no hope that Mozilla and Firefox will change the status-quo anytime soon, Firefox is losing users at crazy rate, and Mozilla is absolutely failing to do anything to change Firefox's destiny towards irrelevance.

> Brave is almost everything Mozilla should've been.

> Actually do what they sey, no hidden google analytics in their products, no unique ID for each installer downloaded, push for privacy by default and independence from big tech, not being shy from google, because they are their only income.

> I would argue, that if Mozilla wants to turn its course around with their "limited resources" it should drop gecko, and anything irrelevant to the users experience.

> Fork Chromium, the best web engine out there by a mile, and remove any anti-privacy / anticompetitive code, while still taking advantage of the huge development resources directed to chromium from many parties, and maybe Mozilla can also influence Chromium's development.

> Start pushing privacy by default, its the reason brave is gaining users at such a rapid pace, its a browser I recommend to everyone, as just by installing it they already are much more private than with chrome.

> What matters is the users experience, its why brave is growing

Re:Proxy Chrome extensions are not going to be usable in MV3 by teawrecks on Monday September 19, 2022 @06:25PM (#32904952)
I'm out of the loop. I've been using FF for years without any issues across multiple OSes and devices. I plan to continue doing that. I simply don't understand the negative sentiment I see about it, it's served me very well.
Re:Proxy Chrome extensions are not going to be usable in MV3 by Schroedingersat on Monday September 19, 2022 @09:26PM (#32906509)
The negative sentiment is advertising for brave (an advertising company) to get people to switch to their ad delivery software.
Re:Proxy Chrome extensions are not going to be usable in MV3 by jacooper on Tuesday September 20, 2022 @09:35AM (#32911464)
Yeah, when someone disagrees with your opinion, he paid to do so.

Brave ads aren't even enabled by default.

Re:Proxy Chrome extensions are not going to be usable in MV3 by pkulak on Tuesday September 20, 2022 @04:56PM (#32917696)
Exactly. Perfect example, thank you.
Re:Proxy Chrome extensions are not going to be usable in MV3 by imbnwa on Monday September 19, 2022 @02:07PM (#32901782)
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

Re:Proxy Chrome extensions are not going to be usable in MV3 by Caspy7 on Monday September 19, 2022 @02:53PM (#32902351)
https://twitter.com/BrendanEich/status/1534893414579249152

> Brave will support uBO and uMatrix so long as Google doesn’t remove underlying V2 code paths (which seem to be needed for Chrome for enterprise support, so should stay in the Chromium open source). Will Google Chrome Web Store really kick them out over V2? We will host if needed.

https://twitter.com/BrendanEich/status/1534905779630661633

> > I’d be interested to hear a plan for Brave on what will happen if upstream removes the code paths needed for pre-v3 ad blockers.

> We could fork them back in at higher maintenance cost. No point in speculating — I don’t write checks of unknown amount and sign them, and Google looks likely to keep V2 support for a year (thanks be to “enterprise”).

Re:Proxy Chrome extensions are not going to be usable in MV3 by imbnwa on Monday September 19, 2022 @03:03PM (#32902477)
I see my misunderstanding, they're specifically maintaining the webRequest interface
Re:Proxy Chrome extensions are not going to be usable in MV3 by yoasif_ on Monday September 19, 2022 @04:37PM (#32903599)
> I see my misunderstanding, they're specifically maintaining the webRequest interface

They aren't specifically maintaining anything. Brave's CEO doesn't "write checks of unknown amount[s] and sign them".

Re:Proxy Chrome extensions are not going to be usable in MV3 by Caspy7 on Monday September 19, 2022 @05:07PM (#32903972)
I think you're thinking of Firefox.
Re:Proxy Chrome extensions are not going to be usable in MV3 by cpeterso on Monday September 19, 2022 @02:30PM (#32902049)
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.
Re:Proxy Chrome extensions are not going to be usable in MV3 by UberFly on Monday September 19, 2022 @03:33PM (#32902842)
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 by TremendousJudge on Monday September 19, 2022 @04:07PM (#32903208)
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 by marwis on Monday September 19, 2022 @03:36PM (#32902883)
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 by TedDoesntTalk on Monday September 19, 2022 @01:09PM (#32901052)
Someone warned years ago that proxy extensions would no longer be feasible on Chromium? I must have missed that message.
Re:Proxy Chrome extensions are not going to be usable in MV3 by lucideer on Monday September 19, 2022 @02:06PM (#32901767)
> Someone warned years ago that <insert extremely specific thing>

No, the gp said:

> while pretending they weren't supporting google's Chrome monopoly

Monopoly means Google's interests will be served rather than the user's. This means taking away things that are of value to users / users losing control over features / etc. Like proxy extensions, yes.

Re:Proxy Chrome extensions are not going to be usable in MV3 by jerheinze on Monday September 19, 2022 @01:15PM (#32901117)
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 by moffkalast on Monday September 19, 2022 @01:15PM (#32901119)
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 by heavyset_go on Monday September 19, 2022 @02:11PM (#32901828)
The amount of work it would take to fork Chromium and maintain a working secure browser with MV2 hooks into the browser internals would be so large that you'd need a dedicated team whose job it is to constantly backport upstream Chromium changes and ensure they still work with the old MV2 subsystem. That would take a lot of time and money.
Re:Proxy Chrome extensions are not going to be usable in MV3 by moffkalast on Monday September 19, 2022 @06:10PM (#32904803)
Well you don't need to implement every stupid thing big G thinks should be in it, just the really critical stuff. Even if you freeze all features right now you'll probably still have a better renderer than gecko for 5 years into the future.

I mean right now I bet a lot of people will simply not update to MV3 and continue using the last known MV2 build into perpetuity until certs break or something else. I sure intend to.

Re:Proxy Chrome extensions are not going to be usable in MV3 by heavyset_go on Monday September 19, 2022 @06:33PM (#32905055)
Backporting from an entity that is hostile towards MV2 makes me suspect that Google isn't going to play ball and make maintaining an MV2-compatible Chromium fork easy.
Re:Proxy Chrome extensions are not going to be usable in MV3 by josefx on Monday September 19, 2022 @01:45PM (#32901505)
>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 by whoisthemachine on Monday September 19, 2022 @03:32PM (#32902832)
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 by heavyset_go on Monday September 19, 2022 @06:36PM (#32905081)
Depends on the browser and platform. WideVine support on Firefox for Linux is limited, one of the biggest effects of this is that some video platforms refuse to serve up high definition video to Firefox users on Linux. Netflix, for example, will only allow you to watch video at 720p on Firefox for Linux. The existing WideVine support comes directly from Google.
Re:Proxy Chrome extensions are not going to be usable in MV3 by fomine3 on Monday September 19, 2022 @08:54PM (#32906266)
Chrome and Firefox on Windows is also limited to 720p so it's on par. https://help.netflix.com/en/node/23931
Re:Proxy Chrome extensions are not going to be usable in MV3 by josefx on Monday September 19, 2022 @04:09PM (#32903226)
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 by whoisthemachine on Thursday September 22, 2022 @08:56PM (#32946635)
Fair, and I didn't know that or had forgotten it, but I think Firefox is still relevant to the parent's comment, and the context of the topic:

> No, especially not if you want to watch videos, the DRM plugin is a binary blob that only Google approved browsers get to run.

So it might be better to say that you don't need to be locked into Google's browser (or a fork of its OS base) in order to consume a wide variety of online content, and you can thus avoid this issue with Chrome extensions entirely. And at least with Firefox it is just a plugin, so presumably could be replaced with a binary blob from someone else if Google's influence became worrisome enough (and I do wonder, isn't it already worrisome enough??).

Re:Proxy Chrome extensions are not going to be usable in MV3 by ElCheapo on Monday September 19, 2022 @01:51PM (#32901574)
I mean, if the DRM wasn't a blob it would be open source. Andnif it were open source it wouldn't be DRM...
Re:Proxy Chrome extensions are not going to be usable in MV3 by josefx on Monday September 19, 2022 @02:46PM (#32902251)
It could be controlled by a third party that isn't trying to dominate the browser market. And Google already caused issues years ago when it side loaded that plugin on open source distros and initially refused to provide an option to disable this behavior in chromium.
Re:Proxy Chrome extensions are not going to be usable in MV3 by heavyset_go on Monday September 19, 2022 @02:05PM (#32901750)
It's possible to have DRM that's open source using cryptography.
Re:Proxy Chrome extensions are not going to be usable in MV3 by easrng on Monday September 19, 2022 @02:40PM (#32902166)
Secure DRM requires that your device have keys that are burned-in that you can't access. It's impossible to have an open implementation of a non-broken DRM system.
Re:Proxy Chrome extensions are not going to be usable in MV3 by marwis on Monday September 19, 2022 @03:22PM (#32902712)
In addition to what others said, forks are not allowed to use Google services such as Chrome Sync or Translate.
Re:Proxy Chrome extensions are not going to be usable in MV3 by AshamedCaptain on Monday September 19, 2022 @01:15PM (#32901128)
Developer effort.
Re:Proxy Chrome extensions are not going to be usable in MV3 by moffkalast on Monday September 19, 2022 @01:16PM (#32901133)
Don't underestimate the power of spite.
Re:Proxy Chrome extensions are not going to be usable in MV3 by AshamedCaptain on Monday September 19, 2022 @01:17PM (#32901142)
Spite is at times my main source of motivation, and still leaves me physically uncapable of following the rate of breakage of upstream Firefox (i.e. I cant keep my patches up to date), which I'm assuming it's actually a more sensible upstream when compared with Google.
Re:Proxy Chrome extensions are not going to be usable in MV3 by Macha on Monday September 19, 2022 @01:24PM (#32901227)
I actually think not - the few third party gecko browsers abandoned ship to webkit/blink/chromium over the years