I agree with your point, though I can easily modify ~/Library/Messages/Attachments or ~/Library/Containers/com.apple.MobileSMS/Data on macOS, which is a platform similarly secure to an iPhone when you take sandboxing, sip, etc. into account. So Apple already supports macOS, which can be tinkered, no? I guess the argument is that by locking down iOS, a platform which was never open, they just never needed to handle that class of security risks which are introduced when customers have more freedom.
I did actually discover a bug in iOS (related to photos which have failed to sync to icloud for the past four years) by investigating why there were over 23k empty folders in ~/Library/Containers/com.apple.photos.ImageConversionService/Data/tmp/, fwiw.
You're right, but I could see Apple acting on iOS alone, just because of scale.
There are some orders of magnitude more iOS/iPadOS devices than macOS devices.
There's a bunch of ways we could debate ourselves about things Apple would or wouldn't do, but at the end of the day, Apple is going to do whatever is in it's best interest.
I don't even bother writing mermaid by hand when I'm making decision trees. Instead of visualizing it using PrecisionTree in excel (I just use that for the actual data modeling), I've been first modeling the tree in plaintext, then pipe it through claude with a previous tree I've made as reference. I then ask it to use the content of the current tree and match it to the style of the previous one.
That overengineered isight camera worked through multiple adapters up until the introduction of the M1, when they sadly finally removed the driver. I used to use it connected to my intel macbook pro for meetings in the the late 2010s for fun.
It still worked for video on Apple Silicon, only the built-in mic stopped working (which was easily bested by the built-in mics on the laptop anyways). Only after they removed FireWire support in Tahoe did it die.
reply