Pausing Manifest V2 phase-out changes • Hacker News Board

Re: Pausing Manifest V2 phase-out changes

#101

Post by akomtu » Sat, Apr 01, 2023, 11:35 PM UTC

charcircuit wrote: post #96

akomtu wrote: post #77

Earlier quoted context omitted.

That's lie pushed by Google. MV3 removes the ability to block requests, but keeps the ability to observe requests. Great for ads-related spying.

MV3 is more than declarativeNetRequest and the reason why declarativeNetRequest improves privacy is that users are not giving out as overly broad permission. A user may want to block ads, but may also want to not give the ad blocker the ability to observe the requests. Even if the user trusts the developer of the adblocker, there is always the chance they get hacked. The average user should not be giving out the webR…

If that was the case, mv3 would let extensions block arbitrary requests on a subdomain, e.g. "uBO wants to block requests on *.com, Yes/No".

Re: Pausing Manifest V2 phase-out changes

#102

Post by arcanemachiner » Sat, Apr 01, 2023, 11:40 PM UTC

miohtama wrote: post #53

kej wrote: post #46

Earlier quoted context omitted.

You can just do this anyway, you know. Firefox is pretty great these days.

Also it would be healthy for the web ecosystem overall if users, especially power users, would use less Chrome. Any excuse to uninstall Chrome is a good excuse.

Or at least change their user agent to skew the statistics. :/

Re: Pausing Manifest V2 phase-out changes

#103

Post by jacooper » Sat, Apr 01, 2023, 11:42 PM UTC

qwertox wrote: post #44

> As we head towards Manifest V3 migration, we are intently monitoring comments from the developer community to help inform our timelines. Here's some feedback: If uBlock Origin loses full control over what gets loaded and what not, I will immediately uninstall Chrome from all my and my family's devices and switch back to Firefox, after a decade of using Chrome as the main browser. I will then also recommend the excl…

Switch to brave, a browser that unlike firefox has privacy actually by default.

Re: Pausing Manifest V2 phase-out changes

#104

Post by darreninthenet » Sat, Apr 01, 2023, 11:45 PM UTC

nozzlegear wrote: post #83

darreninthenet wrote: post #74

Earlier quoted context omitted.

I found it's lack of support for native functionality in MacOS too irritating (eg doesn't support system wide autocomplete - so my @@ shortcut that puts my email address in doesn't work in FF - I know I could put it in again in FF but it's annoying it just doesn't work) so I went back to Chrome in the end. I was using Edge for a while but the absolute car crash their UI has become - and can't be configured - sent me…

My biggest complaint with Firefox on macOS is the lack of support for native picture-in-picture. They implement their own version that doesn’t stay visible when you swap between the virtual desktops; won’t overlay on top of full screen applications; and can’t be moved across monitors (iirc) either.

Now that's weird as PIP in FF always worked fine for me - including swapping between desktops and full screen. In fact I thought PIP in Chrome wasn't as well implemented as took several more clicks to activate.

Can't comment about monitors as I don't use a multi monitor setup on my Mac.

Re: Pausing Manifest V2 phase-out changes

#105

Post by jacooper » Sat, Apr 01, 2023, 11:46 PM UTC

m_a_g wrote: post #5

Anything that breaks uBlock Origin is a deal breaker. With the chrome team making so many alterations to their plans, I guess we'll have to wait and see.

Use brave.

Re: Pausing Manifest V2 phase-out changes

#106

Post by danielheath » Sat, Apr 01, 2023, 11:56 PM UTC

arcanemachiner wrote: post #102

miohtama wrote: post #53

Earlier quoted context omitted.

Also it would be healthy for the web ecosystem overall if users, especially power users, would use less Chrome. Any excuse to uninstall Chrome is a good excuse.

Or at least change their user agent to skew the statistics. :/

Statistics come from google analytics, which most Firefox users block. When I compare stats from my webservers with GA, it’s clear that either bots overwhelmingly prefer Firefox UAs, or it’s underrepresented in GA stats.

Re: Pausing Manifest V2 phase-out changes

#107

Post by p1mrx » Sun, Apr 02, 2023, 12:04 AM UTC

charcircuit wrote: post #59

lewisjoe wrote: post #4

Great news. One thing that I'm sure about V3 is that it isn't well thought-out at all. For example, imagine your extension has to cache data for a browser session (across tabs but with a single cache), it's impossible as of now. The only workaround to do that has a 1MB storage limit, essentially forcing you to have a server-side cache mechanism (redis or whatever) for this trivial use-case. And worse, Google develope…

>has a 1MB storage limit They changed this a couple days ago to be 10 MB with Chrome 112.

The 1MB limit was ridiculous. My MV3 extension uses storage.local (on disk) for session data, only because the quota is 5X bigger than storage.session (in ram). I'm waiting for 112 to hit stable so I can migrate to storage.session only.

MV3 also has this bug where extensions just stop receiving events at random. Search `lostEventsWatchdog` for a workaround.

Re: Pausing Manifest V2 phase-out changes

#108

Post by suddenclarity » Sun, Apr 02, 2023, 12:14 AM UTC

noman-land wrote: post #82

qwertox wrote: post #44

> As we head towards Manifest V3 migration, we are intently monitoring comments from the developer community to help inform our timelines. Here's some feedback: If uBlock Origin loses full control over what gets loaded and what not, I will immediately uninstall Chrome from all my and my family's devices and switch back to Firefox, after a decade of using Chrome as the main browser. I will then also recommend the excl…

Why would you wait for this one single thing when you have had so many historical reasons to choose Firefox over Google already? Why wait for Google to piss you off for the thousandth time when 999 times is plenty?

I don't have any other major issues with Chrome and I've developed several plugins for it that I regularly use. Is Firefox better nowadays because when I left it, Chrome just seemed better in most ways. Firefox felt like an outdated (design) memory hog.

Re: Pausing Manifest V2 phase-out changes

#109

Post by nailer » Sun, Apr 02, 2023, 12:16 AM UTC

If anyone is working on extensions, the documentation for manifest v3 is no longer being maintained. Check out stack overflow: https://stackoverflow.com/questions/tagged/chrome-extension-...

There’s one guy (wOxxOm, who isn’t a google employee) holding all of Manifest V3 on his shoulders, including pointing out places where the docs are missing information or simply inaccurate, while Google do very little to support Chrome developers.

Re: Pausing Manifest V2 phase-out changes

#110

Post by suddenclarity » Sun, Apr 02, 2023, 12:20 AM UTC

jacooper wrote: post #103

qwertox wrote: post #44

> As we head towards Manifest V3 migration, we are intently monitoring comments from the developer community to help inform our timelines. Here's some feedback: If uBlock Origin loses full control over what gets loaded and what not, I will immediately uninstall Chrome from all my and my family's devices and switch back to Firefox, after a decade of using Chrome as the main browser. I will then also recommend the excl…

Switch to brave, a browser that unlike firefox has privacy actually by default.

A browser that injected affiliate links and is pushing crypto. I'm not sure if Brave is the solution.