Comment by kbenson
4 years ago
The problem is that this is not an issue that should be viewed only in the current context. Just because things are rare now, don't last very long doesn't mean that they will continue to be that way, or that it will work at all in the future if Apple decides that only EOL OSs could be using this system at some future point where it's mostly changed.
Not caring about this now is like not caring about government or corporate privacy invasions because "I have nothing to hide". It completely ignores all the variables that have to align to make this benign that happen to at this point, but are in now was assured for the future.
He's not commenting how the problem should be viewed. He's communicating how he thinks most people view it. IOW, you're arguing what should be while he was talking about what is.
> Just because things are rare now, don't last very long doesn't mean that they will continue to be that way, or that it will work at all in the future if Apple decides that only EOL OSs could be using this system at some future point where it's mostly changed.
Okay, sure, you could attempt to estimate future damage from what appears to be a simple (albeit bad) bug in MacOS. Maybe it means all Macs will completely stop working in 2 years. But again, I think consumers will subconsciously estimate the likelihood of this to be extremely low.
> Not caring about this now is like not caring about government or corporate privacy invasions because "I have nothing to hide".
What? I thought we were talking about the immediate user-visible bug here, where some third-party apps could not be opened on some Macs for some period of time today. Sure, there are separate potential privacy concerns any time an OS phones home for any reason. But the problem here is just a blatant bug that manifests when the OS phones home and the servers are having problems. Macs continue to work fine when they're not connected to the internet, so it's pretty clear this is just a bug that's not actually related to the privacy concerns with phoning home.
> What? I thought we were talking about the immediate user-visible bug here, where some third-party apps could not be opened on some Macs for some period of time today.
>>>>> these problems are extremely rare, they don't last very long, and they tend to have fairly simple workarounds.
This is about Apple controlling what software you can run on your computer, for all third parties, and in a way that if the system/service is malfunctioning or shut down there's a chance it blocks all non Apple software.
You can either choose to accept that Apple is a good steward of this because they haven't screwed up too much yet, and that you're okay with it because you have no or little need for third party software it might affect (or are willing to deal with it), or you can view this as an erosion of your rights to control the hardware you bought, which while only slightly inconveniencing now are still fundamentally the same as what could be used egregiously in the future.
You either vigorously defend the rights (or what you want to be a right) now, or you watch it erode slowly. That's how the system works. You want privacy or believe it's important? Protect it now and even if you don't have anything to hide. You want the ability to control your own computer and run your own software, and not be beholden to some companies deprecation schedule affecting things they didn't write, or at least believe it's important for a possible future? Then defend it now.
Given how iOS functions, and how Apple is moving to their own silicon for their other products, do people seriously doubt that a future where you actually can't run anything on MacOS except what you get through their store isn't at least a possible future? If that's something we care about, it's something we should be vocal about now.
The bug has now illustrated a huge privacy issue for people in macOS, that was not obvious before. So we are now talking about THAT too.