Gregory's Server@porglezomp @ieure I have never seen that distinction/behaviour but I won’t dispute it.
|
19 comments
 @chris @porglezomp After removing the quarantine bit, the program launches and runs perfectly. It wasn't damaged, but Apple chose to write software which actively lies to its users. Worth pondering why they decided to do that.  @ieure @porglezomp I honestly can't be bothered with this kind of conspiracy stuff, no matter what company it is. Saying something is "damaged" isn't a lie if it's not conforming to *minimal* expectations. Yes, security is inconvenient but it's no big secret. https://support.apple.com/en-ca/guide/security/sec7c917bf14/web @chris @porglezomp lmao are we hitting the denial stage of grief? Is a program "damaged" because I haven't removed the quarantine bit? Is Apple the one who gets to decide what software I run on my computer?   @ieure @chris @porglezomp „Why“ seems relatively obvious: Apple believes to make more money that way. But to me it raises the question: What else evil and maybe more subtle trickery might they do to cripple things or to keep the profitable ways for themselves and out of the reach of others, including the customers. @chris @porglezomp @ieure My memory is the “damaged” thing happens when an application doesn’t have a signature at all (the system generates a local-only signature when it’s run the first time), while right-click > Open is needed for the first launch of signed applications downloaded directly rather than through the App Store. @bob_zim @chris @porglezomp Yes, it's some nonsense like this. While I'm moderately curious to understand why it works like this, the entire setup is so odious that I don't want to pretend that it's reasonable or engage with it in any way. I get to decide what runs on my computer. Not Apple. @ieure @chris @porglezomp I think it’s a pretty reasonable default to keep most users safe. It’s also super easy to disable the check: https://bikeshed.party/objects/e9f4384b-6cc2-4b22-9463-9d2414b310b7  @bob_zim @ieure @chris @porglezomp Disallowing exec and telling you why is a reasonable default. Lying that it's damaged to trick you into not trying to find a workaround to execute it is vile and user hostile. @dalias @bob_zim @ieure @chris @porglezomp pretty much any browser will throw up a warning if you make an HTTPS connection to a website with a self signed cert too. @distinct @dalias @bob_zim @chris @porglezomp I also think this behavior is horseshit. @distinct @dalias @bob_zim @chris @porglezomp It's not the same, though: the browser explicitly tells you exactly what the problem is, and offers options for you to choose what to do (proceed or not). macOS does not do this. @ieure @distinct @dalias @bob_zim @porglezomp @distinct @bob_zim @ieure @chris @porglezomp The browser doesn't lie and say the DNS lookup failed or the host is unreachable. It says the certificate is untrusted and asks you how to proceed.  It happens all the time and is by design. Happened to me just this morning with a copy of freecad. If you have a few minutes and a few gigs of free space it will for you too. |
@chris @porglezomp I have experienced this firsthand with multiple programs I've downloaded with a browser.
Right-click, open *should* do the same thing as double-clicking. That it no longer does, that even users with years of experience find this surprising, is exactly why it's a dark pattern.