4 ms·
An Apple employee tweeted after the news with 11.0 that this was a bug so I'm not surprised, but happy to see it fixed!
by SmileyKeith 6y ago
An Apple employee tweeted after the news with 11.0 that this was a bug so I'm not surprised, but happy to see it fixed!
- devin 6y agoLink?
- _qulr 6y agoThere's no link because the tweet was deleted soon afterward. The tweet seems to have been very ill-advised. I don't know how anyone can describe this as a "bug", because as the linked article describes, there's an explicit "ContentFilterExclusionList" in the Info.plist file with a list of the specific Apple services excluded. That's not by accident, it's by design.
- nytgop77 6y agobug was in the design. (or in decision leading to design)
- chipotle_coyote 6y agoI don't think I'd call it a bug. It's a poor decision. I can easily believe that it wasn't a decision made with malicious intent; the culture at Apple seems (at least from the outside, judging by results) to encourage an "it's okay to give our own software special exceptions" mentality.
- saagarjha 6y agoYou could call it an entitled opinion.
- chipotle_coyote 6y agoI see what you did there. (+1.)
- dingaling 6y agoA bug is unintentional, through error or coincidence of unforeseen circumstances. Coding a feature and providing a configuration file thereto is not a bug.
- LinusS1 6y agohttps://www.zdnet.com/article/apple-removes-feature-that-allowed-its-apps-to-bypass-macos-firewalls-and-vpns/ https://www.zdnet.com/article/apple-removes-feature-that-all... "The bugs were related to Apple deprecating network kernel extensions (NKEs) in Big Sur and introducing a new system called Network Extension Framework, and Apple engineers not having enough time to iron out all the bugs before the Big Sur launch last fall."
- _the_inflator 6y agoA bug? Not a feature? Glad they changed their mind anyway.
- matkoniecz 6y agoAdding entire feature without justification (ContentFilterExclusionList) is not a bug. Calling it a bug is misleading.
- audunw 6y agoThe feature could be a workaround for a bug. That is, one of their internal services didn't handle being blocked well, and instead of fixing that service they just added that feature as a temporary workaround to make sure the new firewall functionality didn't break any important/core features of MacOS I'm not saying this is what happened, but without actually knowing what happened we can't assume the intention was to exclude everything in this list forever either.