Live data from Hacker News

About Google Chrome's "This extension may soon no longer be supported" (2024)

github.com

81–90 of 179 posts

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#81
post #7

Earlier quoted context omitted.

The part where they say they are not developing it further. CEO discussing it further here: https://x.com/joshm/status/1850717644779110643 They have not shipped anything but browser updates and minor fixes for months.

> They have not shipped anything but browser updates and minor fixes for months. I would LOVE my browser to do just that!

The fixes are really really minor. Larger functional bugs that aren’t catastrophic are hanging out.

That said, it’s been fine for me and I’m still using it. I don’t see any reason to abandon it yet. When the company fails maybe they’ll open source or sell it. I’d happily pay for this.

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#82

Google is milking a dying cow. LLMs are much better in searching for information than advertisement-exposure optimized google. People are paying for LLMs, consumers are no longer a commodity. Internet will change, maybe creators will be paid for their content? But what will happen with advertisers?

> People are paying for LLMs, consumers are no longer a commodity.

Ask your LLM: "How many percents of world populations is paying for LLMs? Any estimates how many will never pay for it?"

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#83
post #43

Earlier quoted context omitted.

They mention "other browsers" in addition to Firefox that will continue to support Manifest v2, but I can't find a list. Does anyone know off-hand the additional browser options for Manifest V2 and multiple-OS support?

Brave and Vivaldi will continue to support it for some time. Brave also does not really depend on MV2 as they have their own adblocker (which is about as effective as uBO, I believe). edit: link to their adblocker: https://github.com/brave/adblock-rust

Edit: I was wrong. See below.

Original comment: Brave's built in blocker is OK for what it does but I believe that it only replaces a subset of all uBO's features. For example I don't think that Brave's built in blocker has an element picker that lets you create cosmetic filters on the fly. I use that feature all the time in uBO.

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#84
post #56

Earlier quoted context omitted.

I think some Chromium-based browsers like Brave have pledged that they'll keep v2 around for as long as it's practical? Though IMO, people who depend on Manifest v2 with Chromium forks are running on borrowed time, Chromium moves fast and I can't imagine that keeping the Manifest v2 code working will be very easy. Especially if Google takes advantage of the limited access extensions now have to the HTTP request flow…

Yep, currently brave (and others I assume) switch it on at build time, when Google removes that from chromium they may move it to their patch set, but who knows how long they’ll keep that once it starts breaking.

The dynamic web request hook is the only thing still relevant in MV2, right? Are there any other features to be backported from MV2?

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#85
post #72
post #18

I tried uBlock Origin Lite for a very short time. Then I realized that in Lite, the user can’t add custom rules[0]. That’s when I had enough. So now I’m using Firefox instead, where I can use uBlock Origin. [0] See https://old.reddit.com/r/uBlockOrigin/comments/1in2ls4/ubloc...

I simply cannot give up the option of zapping distractions off of my screen. I really cannot understand how people can use Youtube or even a Youtube embedded video without zapping away the distractions. There is no way I'm coming back to Chrome if they don't support manifest V2. It's Firefox for me.

I'm also using it to remove distractions from stack exchange sites like hot network questions. I can stay focused on solving my problem much better if my eyes can't wander to interesting unrelated stuff.

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#87
This is a clear example of conflict of interest Google has.

It makes money almost exclusively from ads, and people want to block ads. No matter how they try to portray decisions like this - it is obvious they are moving in direction where people are unable to do what they want.

I am sure if Google from today would launch a browser, it would fail to gain traction knowing all the state of their core business and negative sentiment users have.

Let's hope Mozilla doesn't go the same route, but it seems they are also not under good leadership and are slowly loosing the trust of users.

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#88
post #18

I tried uBlock Origin Lite for a very short time. Then I realized that in Lite, the user can’t add custom rules[0]. That’s when I had enough. So now I’m using Firefox instead, where I can use uBlock Origin. [0] See https://old.reddit.com/r/uBlockOrigin/comments/1in2ls4/ubloc...

For anyone else like me that hasnt tried uBO lite wondering what features are missing: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#89
post #56

Earlier quoted context omitted.

I think some Chromium-based browsers like Brave have pledged that they'll keep v2 around for as long as it's practical? Though IMO, people who depend on Manifest v2 with Chromium forks are running on borrowed time, Chromium moves fast and I can't imagine that keeping the Manifest v2 code working will be very easy. Especially if Google takes advantage of the limited access extensions now have to the HTTP request flow…

Yep, currently brave (and others I assume) switch it on at build time, when Google removes that from chromium they may move it to their patch set, but who knows how long they’ll keep that once it starts breaking.

The best thing for Brave to do would just be to build it into their own ad blocker because Google is going to intentionally make it more and more impractical to support older extensions that interfere with their business model.

Re: About Google Chrome's "This extension may soon no longer be supported" (2024)

#90
post #56
post #43

Earlier quoted context omitted.

They mention "other browsers" in addition to Firefox that will continue to support Manifest v2, but I can't find a list. Does anyone know off-hand the additional browser options for Manifest V2 and multiple-OS support?

I think some Chromium-based browsers like Brave have pledged that they'll keep v2 around for as long as it's practical? Though IMO, people who depend on Manifest v2 with Chromium forks are running on borrowed time, Chromium moves fast and I can't imagine that keeping the Manifest v2 code working will be very easy. Especially if Google takes advantage of the limited access extensions now have to the HTTP request flow…

Chromium browsers can't make that pledge and those that promised have red flags in my book.

1. These browsers can barely add their own functionality on top of upstream, and maintaining Manifest v2 compatibility may be expensive. Consider that the development of Chrome exceeds 1 billion per year.

2. They all use Chrome's Webstore as a distributing channel, except for Edge, but IMO, Microsoft has an even bigger interest in seeing uBO die.

Brave itself has ad-blocking built-in, which won't be affected, and it's fairly capable, but promising that they'll keep compatibility with uBO is a lie, if they ever made that promise.

Post reply on HN