3 ms·
Yes, it feels like Apple is increasingly embracing dark patterns. The fact that they are withholding security updates for older iOS versions from devices that
by layer8 2y ago
Yes, it feels like Apple is increasingly embracing dark patterns.
The fact that they are withholding security updates for older iOS versions from devices that support newer iOS versions is also one. (E.g. I can’t upgrade from 17.7.1 to 17.7.2 now, currently staying on iOS 17 like the parent, although it was possible for a few weeks from mid-November to mid-December, but I had somehow missed that. In other cases the updates have been restricted to older devices to start with.)
Furthermore, patterns like the one noted in https://news.ycombinator.com/item?id=42899637 https://news.ycombinator.com/item?id=42899637.
- walterbell 2y agoIt's a disaster for Apple devices breached by an iOS zero day. A "workaround" is to track every outbound network connection, block C&C traffic at the router, then keep using older iOS-infected-with-dormant-malware. If attackers create ransomware (instead of spyware) for iOS, governments will have to force Apple to enable 3rd party backup and restore to a clean DFU install of their existing iOS version. Currently testing Google Pixel tablet and phone with GrapheneOS, where Debian Linux VMs will be possible in Android 16. Better security, weaker hardware, less usability, but at least the OS isn't channeling HAL 9000, https://www.youtube.com/watch?v=ARJ8cAGm6JE https://www.youtube.com/watch?v=ARJ8cAGm6JE
- okamiueru 2y agoFirst I hear about Debian on pixel phones with graphene. Do you have a link to information on this?
- walterbell 2y agoAny Android 16 device that supports AVF, which includes Google Pixels, but excludes Samsung. https://www.androidauthority.com/android-16-linux-terminal-doom-3521804/ https://www.androidauthority.com/android-16-linux-terminal-d...
- deleted 2y ago[deleted]
- bitwize 2y agoTo some extent, Apple has been like this a long time. They broke the compiler suite on macOS 10.3. Or rather, left it broken; there was a GCC ABI change and Apple did not deliver a GCC to macOS 10.3 that could produce binaries compatible with the new-ABI libraries Apple pushed in a security update. To continue compiling C++ code, in particular, for 10.3, you had to upgrade to 10.4 and get the latest Xcode there, it had a backwards compatibility setting. The message was clear: if you develop for Apple, you need to always have the latest and greatest, because Apple simply doesn't care about you if you don't.
- szundi 2y agoApple is not for nieches, that’s clear.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]