# iOS 应用 1.5.0 不再允许内容拦截器？ **URL:** \ **Category:** Feature\ **Created:** [2019年五月12日 00:25 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489 "2019-05-12T00:25:35Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月12日 23:33 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/22 "2019-05-12T23:33:47Z")
No joy in either, interestingly enough. ![image](https://global.discourse-cdn.com/meta/original/3X/5/7/576a51594f35da36e29fcf2c16e284948192a771.png) ![image](https://global.discourse-cdn.com/meta/original/3X/7/8/7891da09fb6a5e33c1c54e62da154e15312ccb8e.png) ---
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [2019年五月12日 23:36 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/23 "2019-05-12T23:36:37Z")
If Google and Mozilla are having trouble swinging this and they have large dedicated teams, I think the odds, sadly, of us being able to swing anything are very low. Maybe open a ticket on GitHub for Firefox and/or Chrome (perhaps there is already a ticket there) if they give us a roadmap of how to do this it makes this feasible. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月12日 23:37 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/24 "2019-05-12T23:37:36Z")
Nice find on the API. I also filed a bug report with Apple, and may be able to call in a favour from the Safari Evangelist. Opening tickets with the other browsers is an excellent idea. I’ll do that. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月12日 23:48 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/25 "2019-05-12T23:48:36Z")
Firefox (oldest first, later better) - [Add content blocking support · Issue #1271 · mozilla-mobile/firefox-ios · GitHub](https://github.com/mozilla-mobile/firefox-ios/issues/1271) - [1210111 - [meta] Support content blocking in Firefox iOS](https://bugzilla.mozilla.org/show_bug.cgi?id=1210111) - [1390148 - Feature: Tracking protection](https://bugzilla.mozilla.org/show_bug.cgi?id=1390148) ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年五月13日 02:28 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/26 "2019-05-13T02:28:19Z")
This all screams “fix it at the source” to me. I’d buy a plane ticket to the site owner’s home town (with their permission, of course) to convince them in person. Probably be a more effective use of the same block of time as well. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月13日 09:04 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/27 "2019-05-13T09:04:11Z")
Factor in the other 40 sites I do this for. (I just checked) ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 08:38 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/28 "2019-05-14T08:38:41Z")
> [@sam](#): > > What about if you lobbied to remove it once a user donates? This worked. Cheers! Now, about those tweaks for the other 40 sites… ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年五月14日 15:26 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/29 "2019-05-14T15:26:58Z")
The other 40 sites also have this badly placed donation banner on mobile? I am unclear. Maybe you can be much more specific? ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 18:06 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/30 "2019-05-14T18:06:54Z")
Come on now. Really? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年五月14日 18:18 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/31 "2019-05-14T18:18:19Z")
I seriously don’t know what you are referring to. So.. yes. Really. ---
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [2019年五月14日 18:20 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/32 "2019-05-14T18:20:49Z")
Well you cited one example, and after the suggestion from @sam you made a request back to the community in question which improves the experience for all users who donate. Are the other 40 sites all adding this kind of stuff? If not what is it you’re blocking? Adverts? When there are so many communities who rely on adverts to survive, it wouldn’t be received well if the Discourse team to out of their way to help make adblock work within their app. It works in the browser today, they don’t control the browser. Actively assisting the blocking of ads within Discourse Hub is an entirely different matter though. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 19:08 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/33 "2019-05-14T19:08:22Z")
Sorry @codinghorror I thought you were being facetious. I mean, of course they don’t all have that badly placed button. My last mention of 40 was left as a trailing thought… not a question. I wasn’t expecting further discussion at this point. @Stephen > [@gingerbeardman](#): > > Not ads, no. Other things like buttons and menus I’d rather not see. So, again: not ads, no. I don’t have time to list specifics and screens of all 40 content blocks (I said sites, but a better metric would be to count blocks as I use multiple on a few sites) right now but I’ll add further examples when I can. Generally, though, “page elements” is a good catch-all term. Like, headers, footers, avatars, dickbars, etc. Will go into detail when I can. ---
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [2019年五月14日 19:15 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/34 "2019-05-14T19:15:21Z")
You can see the problem though, right? Spending any engineering time trying to fix content blockers will also hit the ad revenue of all sites running Discourse, including CDCK’s paying customers. It’s a totally different situation if Apple decides to change something. They chose to allow content blockers in iOS in the first place, and determine the scope of their penetration into the network stack. Can you imagine the uproar if content blockers worked iOS-wide? Ad-funded apps would no longer make sense at all. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 19:34 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/35 "2019-05-14T19:34:30Z")
Third time lucky: _I’m not blocking ads_ That said, I completely agree on your reasoning - that would indeed cause money problems in some places. > As an aside, content blocking iOS-wide is a thing. Check out FutureMind’s Weblock app. ---
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [2019年五月14日 19:38 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/36 "2019-05-14T19:38:01Z")
It’s unfair for them to call that an app, it’s just delivering a proxy server setting (pac) to the phone. You could do the same with a VPN. Also worth noting: > Blocking ads is done by **sending all communication with different ad servers via the dummy proxy server**. It will fail every time and prevent the ads from being shown. Weblock **works only with Wi-Fi, since we can’t change cellular proxy settings** without jailbreaking the device or putting it into supervised mode. AdBlock will work on both Wi-Fi and Cellular. > [@gingerbeardman](#): > > Third time lucky: _I’m not blocking ads_ Yes, I read your last re-quote. If you can come up with a way to allow elements to be blocked, without also allowing adverts to be impacted then please do share. My point (_third time lucky?_) is that content blockers either work, or they don’t. There is no halfway house. Fixing your problem has more _undesirable_ outcomes, than _good._ ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 19:51 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/37 "2019-05-14T19:51:15Z")
Sure thing. Point taken. (I had the displeasure of raising the Weblock app internally when I worked at Apple as a Technology Evangelist. Back then it used different presentation/language, but was still just a configuration app for a user-defined PAC (proxy auto config). App Store couldn’t nix it, because it was in a grey area. The best that could be done was to ask them to change the language — they also added a VPN mode down the line for good measure, ha!) ---
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [2019年五月14日 19:53 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/38 "2019-05-14T19:53:40Z")
Well they did just ream out Google and Facebook for using their enterprise certificates for sideloading apps which proxied traffic. I can totally forsee a future change to the app store terms which nixes abusing proxies in this way, they opened the door for Content Blockers to make this kind of practice unnecessary. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月14日 19:58 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/39 "2019-05-14T19:58:05Z")
Weblock has been around for 6 years, so it’s not new. I can’t see Apple having another go at it after leaving it be for all that time. Unless it became the number one paid app or something equally crazy. ---
**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\ **Post date:** [2019年五月26日 21:32 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/40 "2019-05-26T21:32:52Z")
> [@sam](#): > > What about if you lobbied to remove it once a user donates? Didn’t work after all. Admin initially agreed, but then backed out due to being unable/uncomfortable making the change with their skill level. 😢 ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年五月26日 21:43 UTC](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489/41 "2019-05-26T21:43:57Z")
You can have them contact us, provided they are willing to provide admin access for a bit, we could assist and write up a how-to here? I am definitely willing to commit to that cc @hawk if we get a nice how-to writeup out of it. [上一頁](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489.md?page=1) [下一頁](https://meta.discourse.org/t/ios-app-1-5-0-no-longer-allowing-content-blockers/117489.md?page=3)