But on the other hand, if you care about your privacy, why would you trust a third party to intercept all of your web traffic?
uBlock Origin is free and open source, and its code is thoroughly reviewed by many contributors every release. I trust uBlock Origin over a filtering mechanism built into a closed source browser such as Safari.
But did you personally download the open source version review the code and install it?
Yes, I have personally downloaded the uBlock Origin source code. I have also reviewed the code and suggested improvements. However, I don't even need to download the code to realize the benefits of uBlock Origin being free and open source. Even if I hadn't downloaded the code, there are many other users and contributors who have reviewed the code, and you can confirm this by taking a simple look at the activity in the GitHub repos.
What are you talking about? You are the one who accused other developers of that. Let me quote you again:
> But on the other hand, if you care about your privacy, why would you trust a third party to intercept all of your web traffic?
https://news.ycombinator.com/item?id=34699213
My point is that because uBlock Origin is free and open source, anyone can see that it is not tracking users maliciously. On the other hand, Safari is closed source, so your FUD would be more applicable to Safari. There is no easy way for users to verify how a closed source browser such as Safari implements its content blocking. In terms of transparency, uBlock Origin is strictly superior to Safari.
Until you use an app with a web view…
But tell me what can’t I block in your experience with 1Blocker on Safari?
If we are comparing ad blocking extensions. We know that there is no possible method for a third party ad blocker on iOS to intercept your traffic.
You’re comparing an ad blocker to a browser.
The fact is that your ad blocking extension won’t work at all within embedded web views.
We know for a fact that a third party ad blocking extension can not intercept your web browsing history on iOS whether it is open source or closed sourced. It has no access to your web browsing history.
Your assurance comes from open source, mine comes from knowing that my third party as blocker doesn’t have any access to my web browsing.
You have been spreading FUD about fully-featured content blocking extensions like uBlock Origin, which is not a very good argument because Safari itself is closed source and its behavior is opaque. A combination of Firefox + uBlock Origin is fully free and open source, and its behavior is fully and easily verifiable. It is absurd for you to criticize combinations such as Firefox + uBlock Origin when the combination of Safari + a Safari-compatible content blocking extension is clearly less transparent due to Safari being closed source.
Apple's anti-competitive App Store restrictions are preventing the superior combination of Firefox + uBlock Origin from existing on iOS. Fortunately, regulations will soon make some of Apple's anti-competitive restrictions illegal in some major markets.
uBlock Origin not being able to protect web views on iOS is yet another restriction imposed by Apple. If browsers on iOS were able to supply web views to other apps and activate extensions in those apps, as the Custom Tabs feature works on Android, uBlock Origin would have no issues blocking content in iOS web views. Don't blame uBlock Origin for a restriction that Apple created.
What you meant to say: Chrome implements its own non-standards against strenuous objections if both Firefox and Safari.
I guess in your world "every other browser" is Chrome. And, sure enough, there are some parts of the API that are only implemented by Chromium-only browsers, and are not implemented by either Safari or Firefox.
So, what other untruths you're going to tell us?
Viewport units have been around for a decade now, and Safari still can't get them right.
For example:
Let's say we want to make a chat window, where a user can type in an input field at the bottom and little message bubbles appear above. Sounds like a job for flexbox and viewport units.
Okay, we'll have one flexbox div container with it's children being the chat messages and the input which get aligned to the bottom. Now we'll position the container so it takes up the full page using viewport units (e.g. take up 100% of the viewport's width, and take up 100% of the viewport's height).
Oh no! When the user scrolled through the messages, the browser's tab bar appeared and instead of calculating that 100% of the viewport is 100% of the viewport, the viewport isn't being updated, and now the input field has been scrolled out of the page.
That's okay, we'll just use the new dynamic viewport units which specifically account for the problem that Safari had invented, and which only took 8 years to come out.
Okay looks good, time to send a message.
Oh no! When tapping on the field input, now the keyboard covers up field so we can't see what we're typing.
>_<
Good work Safari... Real good work...
When I say I want something to take up 100% of the viewport, I mean 100% of the viewport.