Or, instead of digging through every line of source code and packaging it myself, I can use an operating system where the vendor designed a content blocking framework that is privacy focused by default and that works with third party apps that use web views.

Yeah, because you're just taking Apple's word that they aren't being nefarious. You can quite literally see for yourself whether or not ublock origin is. It's like arguing that being able to film the police shouldnt be allowed because they promise to be good.

You can also see for yourself how ad blockers register what can be blocked to Safari by looking at the open source WebKit code…

Sorta! You can't install it so you can't prove it's the same thing! That's the problem with a locked OS.

So you suggest that everyone look through every line of source code to ensure that it is legitimate?

Did you also verify that Firefox installed from the App Store was the same as the open source version?

Are you using only open sourced code on your phone or are you using Google provided binaries? Are your drivers open source for your chipset?

If not, you are also using “locked down code”

Towards open source freedom is my goal, not towards Tim Cook's bonus. nvidia just moved more towards open sourcing their drivers. You think that's out of kindness? No, it's because AMD and Intel have open drivers and nvidia is scared to lose market share to them.

Vote with your wallet and we can have a better future. I don't care if it's iOS, Android, or Linux! Just that it's actually open.

Nvidia no more moved toward open source than Google with the play store. It still depends on binary closed source blobs.

I assure you that Nvidia is not going to lose market share to Intel in the GPU race. Even Apple is creating chipsets Thad trounce Intel in graphics performance.

That's a great starting point / default but can't block complicated things as effectively and shouldn't be the only option on a platform.

Care to post some real world example websites?

The data processing consent popups on Google properties aren't blockable by this because they are JS-based and integrate with the rest of the page's JS code, so the only way to "defuse" them is to run active JS code provided by the blocker. The declarative framework can't do this by design.

1Blocker iOS

> Block Annoyances: blocks cookie notices

And if you really want to, you can run 1Blocker scripts within Safari that can do the same type of thing. You have to go into Settings and you get a huge privacy warning.

And this also works with embedded web views - unlike with Android