@nikitonsky In terms of trusting the extension contents, correct that you are now required to trust two entities instead of one. The difference is that Google (presumably) does not know anything about who is downloading the extensions; it seems to me that this is the problem they were trying to solve.

I'm not sure exactly what your concern is, though. The browser maker might tamper with an extension? They made the entire browser, which you're already running. They could do anything.

@nikitonsky My read on this is that they are asking for permission for things that most other products just do invisibly in the background, without asking. The fact that it's even possible to use Helium without it connecting to any servers ever (!) other than what you type in the address bar makes it different than other web browsers.

For example, how would they do software updates without connecting to a server?

Do we need someone to jailbreak iOS 18.7.2 just so that we can install legitimate security patches on it? After all, it looks like there are exploits already in the wild, so it seems possible that maybe one of them could be leveraged to gain root.

Maybe we can crowdfund it somehow? It would really highlight the absurdity of the situation.

This page shows when each model iPhone stopped getting updates to iOS 18: https://theapplewiki.com/wiki/Firmware/iPhone/18.x

Only iPhone XR and XS are still getting iOS 18 security patches at this point. The patches exist and they could run on the newer phones, but Apple says no.

I also know about NSScrollView.flashScrollers(). But:

1. This is a web site.
2. That was always a garbage solution to the problem.
3. Expecting a user to notice something that only happens briefly, and remember it forever, is always a garbage solution to any problem.