Live data from Hacker News

Pausing Manifest V2 phase-out changes

groups.google.com

61–70 of 170 posts

Re: Pausing Manifest V2 phase-out changes

#61
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…

uBlock Origin already has less control in Chrome than in Firefox.

https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

Re: Pausing Manifest V2 phase-out changes

#62
post #52
post #27

Earlier quoted context omitted.

Why wait? Move to Firefox now.

Using 2-3x as much battery as all other browsers on my Macbook is the dealbreaker for me.. I want to use the same browser on all systems when I move..

Would Brave maybe work better? But I personally feel a bit awkward about the crypto stuff in it even if it can be disabled. I don't think a browser should deal with these things. However, it might be personal preference... It does offer built-in ad blocking and more.

Re: Pausing Manifest V2 phase-out changes

#63
post #46

Earlier quoted context omitted.

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

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

> I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches

Been using Firefox on Linux as my daily driver and haven't seen any of that. Can you provide any examples?

Re: Pausing Manifest V2 phase-out changes

#64
post #46

Earlier quoted context omitted.

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

Switched to Firefox for like 6-12 months, eventually moved back to Edge a couple of weeks ago. Had to open it constantly anyways. I couldn't get used to Firefox's DevTools and the JSON viewer in Firefox is bad compared to the JSON Formatter chrome extension.

Huh. I'm rather surprised you're comparing the out of the box firefox json formatting (rather good compared to chrome's non-existent formatter) to an extension. Are there no JSON formatting extensions for firefox?

Re: Pausing Manifest V2 phase-out changes

#65
post #31
post #29

Earlier quoted context omitted.

Feels slow in old computers with 4GB and Chrome has a better built-in for freeing up memory from inactive tabs.

But will likely be plagued with performance degrading ads.

And it's still fast in spite of that, which speaks to how far behind Mozilla is.

Re: Pausing Manifest V2 phase-out changes

#67
post #10

I love it when advertisment companies who make money handcrafting the perfect ad for you, analysing your search history, talk about Privacy. Yes, this V3 manifest will break adblockers but think about your pRiVaCy gUys!!!

I don't disagree with you (always follow the money), but on the other hand, who better to understand the privacy concerns than the people who work around them for a living? I would definitely want to listen to them. That doesn't mean we just take what they say uncritically, but their perspective is very important.

onBeforeRequest(), though, is just one of several ways to run arbitrary JS on a 3rd party page within an extension. There's a reason it's "first to be hobbled", and that reason isn't privacy. Nobody can prove intent, of course, but I'm predicting the pace of "privacy improvements" slows considerably after the smart heuristic-based ad blockers are out of the way.

Re: Pausing Manifest V2 phase-out changes

#68
post #62
post #52

Earlier quoted context omitted.

Using 2-3x as much battery as all other browsers on my Macbook is the dealbreaker for me.. I want to use the same browser on all systems when I move..

Would Brave maybe work better? But I personally feel a bit awkward about the crypto stuff in it even if it can be disabled. I don't think a browser should deal with these things. However, it might be personal preference... It does offer built-in ad blocking and more.

I also feel weird about all the crypto stuff in Brave. I chose Vivaldi (also a Chromium based browser with built-in adblocker). It's developers include a lot of former Opera devs.

Re: Pausing Manifest V2 phase-out changes

#69

Earlier quoted context omitted.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

I'm using Firefox on Linux¹ and I have experienced none of those problems. Although I'm not particularly happy with the direction that Mozilla has been headed, Firefox is certainly a vast improvement over Chrome or even Chromium. 1. Latest version of Firefox (not ESR), Latest Debian, both Intel & AMD graphics. I can't speak for NVIDIA graphics on Linux as I gave up on NVIDIA a few years ago.

Admittedly there were a few issues in the past, just nothing in the last couple of years that I can think of.

Re: Pausing Manifest V2 phase-out changes

#70

Earlier quoted context omitted.

Or working on pressuring Firefox to implement MV3.

firefox already implements mv3 as much as they can, but without removing what mv2 offered don't they?

That’s correct. Starting in version 109 earlier this year, Firefox supports many MV3 APIs without removing or deprecating MV2 APIs. To ease the transition to MV3 for extension developers, Firefox extensions can use both MV2 and MV3 APIs.

https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signi...

Post reply on HN