4 ms·
The more likely scenario is that browsers effectively ban or restrict ad blocker extensions. Apple already refuses to support browser extensions on their mobile
by wildrhythms 4y ago
The more likely scenario is that browsers effectively ban or restrict ad blocker extensions. Apple already refuses to support browser extensions on their mobile OS, and Google does not allow extensions on Chrome mobile, and we already know mobile accounts for a significant portion of web traffic.
- Teever 4y ago> Apple already refuses to support browser extensions on their mobile OS It's going to be interesting to see how Apple deals with this now that the EU is forcing them to allow users to install apps from alternate sources.
- dylan604 4y agoyou make this comment like the comment you are replying to is true. it's not, and just makes your comment even more ridiculous
- chrisbolt 4y ago> Apple already refuses to support browser extensions on their mobile OS My iOS Wipr extension begs to differ.
- dylan604 4y agoThis is one of those things that won't die like iOS can't copy&paste. Yes, both things were true for a painfully long time. They are no longer true now, so continuing to saying use these as examples is just moronic at this time.
- wildrhythms 4y agoThe last time I looked at Wipr it still wouldn't let me block an individual element or set up my own filter. And what I'm calling a browser extension must be quite different from Apple's recent definition.
- SllX 4y agoI currently have 17 extensions installed on my iPhone for Safari. There’s some overlap, but not total overlap with the 7 content (read: ad) blockers I have installed too.