uBlock was the original name for the add-on that subsequently was ethically compromised/"sold out to" advertisers
uBlock Origin is the 2nd version written by the original author (gorhill) and is not compromised.
Just wasn't sure which you are talking about
https://addons.mozilla.org/en-US/firefox/search/?page=1&q=ub...
It's still called uBlock Origin, and in general I don't think keeping track contextually of when you can get away with a name collision is a great way to do things, and this is an area of privacy concern so I think many of the people interested in the space would like to remain educated about it.
Only “remote browsers” like Opera Mini can currently use something other than the system’s webview.
https://github.com/AdguardTeam/AdguardForiOS/blob/master/COP...
Honestly, no idea.
https://www.reddit.com/r/Adblock/comments/koowte/encrypted_d...
I like how I don’t need a separate app (just install the profile) but I do wonder if I need to implicitly trust the website that has the profiles for download.
So far so good though.
I use the mullvad ones. Sometimes it breaks public wifi signins, so I switch to a less restrictive one in those situations (usually CIRA, which is the Canadian domain registrar)
The really nice thing about DNS profiles is that they’re system wide, so it works against in-app ads too.
The only exception i can recall right now was youtube but SponsorBlock does great there in Safari.
Safari/iOS blocking is closer to uBlock Origin than to DNS blocking, but is not as powerful as uBO and some sites "exploit" those limitations.
Most serious iOS content blockers ship both a native list (or multiple) and an active counterpart, usually focusing on YouTube ads.
However I am aware that adblocking is still poor on Safari, maybe nobody just can match uBO
Injecting code via Web Extensions is too late for reliable blocking - by then, either the malicious JS you are trying to defuse has already ran (if it wasn't blocked declaratively), or if not then the rest of the page's JS depending on it has already exploded and "fixing" it after the fact (by substituting a neutered shim via Web Extensions) doesn't fix the rest of the page.
I mean, to each their own principles but…