Re:The new Google Pay repeats all the same mistakes of Googl...
by xvector on Monday March 08, 2021 @04:14AM
(#26383648)
Content blockers for Safari are basically the same, but with the added bonus of stronger fingerprinting protection from Mobile Safari than Firefox due to the hundreds of millions of iOS users.
[ Parent
| on HN ]
Re:The new Google Pay repeats all the same mistakes of Googl...
by anonymousab on Monday March 08, 2021 @10:39AM
(#26386837)
Safari content blockers are significantly limited compared to ublock origin. You're limited to domain allow/deny rules, and a quite small amount of those per app (less than a couple hundred thousand I think) and IIRC can't inject cosmetic filters either. These are critical drawbacks.
Re:The new Google Pay repeats all the same mistakes of Googl...
by krzyk on Monday March 08, 2021 @06:10AM
(#26384459)
Aren't content blockers limited in some regard? I think I read that one content blocker can only have a limited list of blocks.
uBlock on Firefox doesn't have that limitation, and if you use Firefox on desktop you can important synchronization between those.
Re:The new Google Pay repeats all the same mistakes of Googl...
by Spivak on Monday March 08, 2021 @10:36AM
(#26386805)
Yes and no. Content blockers have a limited number of rules and you’re fundamentally limited by the expressiveness of the filtering language.
But:
* The filtering language is basically just ABP rules.
* There is only a cap per “extension” so apps with lots of rules just expose many extensions.
Re:The new Google Pay repeats all the same mistakes of Googl...
by lorenzhs on Monday March 08, 2021 @05:15AM
(#26384095)
You can also combine that with a DNS-level ad-blocking pseudo-VPN running on the device (like a pi-hole but without the pi). That gets rid of most in-app ads and a ton of tracking.
Re:The new Google Pay repeats all the same mistakes of Googl...
by ciceryadam on Monday March 08, 2021 @06:00AM
(#26384392)
Yep, you could set it up via https://apple.nextdns.io/