Adblockers exist on iOS since like forever. You even have a dedicated tab for them in the Settings.

I personally use Ghostery to kick CMP and Vinegar to play YT videos in the built-in HTML5 player.

I also heard about a gnome that might hold the secret to find it. He stand in line with us but he doesn’t cook.

If only there was another open source web engine, like some kind of kit to develop a web browser, with privacy in mind.

I don’t know, maybe I’m just daydreaming.

Of course there are unreleased 0-days, but you can’t do anything about it.

And that’s exactly my point.

Using a different browser until a particular issue is fixed when you are e.g. a journalist still helps with getting hacked.

Actually no. Because you never know what currently unfixed 0-day is actively exploited in any browser. Using Gecko or Chromium today because Webkit had a security flaw yesterday doesn’t make anything safer. It might comfort you, but that’s it.

The only important metric is the number of 0-day discovered per year per engine. It’s a matter of probability.

Changing engine would be like changing dice because you had a bad number, without knowing how many side you’ll get with the new ones.

0-days that we know of

There definitely are 0-days in every major browser engines.

As a matter of fact, Mozilla is probably working on a 0-day breach that haven’t been published by security watchdogs yet.

In the meantime, that particular WebKit breach has already been patched.

There’s no point skipping places when everything is on fire. The only thing you can do is going where it’s safer on average and stay there.

That must be why iOS 15 and iOS 16 have been patched last night. /s

Gecko has its own problems. Installing Gecko would fix that webkit security breach for sure, but you would end up with gecko’s security breach. So in the end it doesn’t change anything.

It has been patched in Safari Technology Preview 173. We are currently running 181.

Apple released security patches for iOS 15 and iOS 16 yesterday besides iOS 17.1

I’m pretty sure it has been solved already.

Of course we forget how it works.

The whole point of the documentation is to help remembering.