The specific mention of AI in this tech note makes me wonder if this is related to the recent iMessage database pilfering claim made about Meta.

https://appleinsider.com/articles/26/09/28/metas-new-ai-agent-blatantly-ignores-users-permissions

Before: fopen \
Now: we will introduce additional controls \
In the future: for $4.99/month you can access your own files locally!

icloud.com is just as identifiable as apple.com

They might lose performance relative to new chips, but I don't find the M1 ever holds me back. Fantastic chip.

Kinda cool that the M1 macbooks have been gaining performance over their lifetime as apps moved over from x86 to arm. It was gradual, but now it looks like the gradual increase has leveled out, and NOW it will gradually lose performance versus modern devices.

Dumb. If you’re going to change an Apple-related security URL, change it to an apple.com domain so there’s no mistaking it is an actual Apple-owned website.

That, kiddos, is why you insist on copyleft instead of permissive licensing.

Is there an option to exclude users from Texas? 'Cause that's what I'd choose to do.

I’m over here just wishing I could get open dyslexic font in Books and Reader

To be fair, even with 3G networks being decommissioned, many countries still have 2G networks up and running to support older phones. Data speeds are usually way to slow to be useable, but for text messages it might work.

By the way, it looks like someone already did this (though for iOS 6): https://chatgptlegacy.com/

The app seems to be open-source too: https://github.com/bag-xml/ChatGPT-for-Legacy-iOS

Don't think it would be impossible to make an app for both iOS 3 and 26. You wouldn't be able to make it binary-compatible due to different architectures, but you might be able to use the same source code to target both OSes. You'd have to use a very old Xcode version to target iOS 3, since deployment targets this old generally aren't really supported by recent Xcode versions, and you wouldn't be able to submit that version to the App Store. Naturally you'd have to limit yourself to some subset of UIKit APIs supported back then (that hasn't been deprecated and removed). But if done right, you should be able to open up the project with a recent Xcode, hit build and run it on iOS 26.

It might be an impressive feat, but seems like a pointless one. Who's still got a functioning iPhone 1 - especially one with a battery worth a damn? Never mind the lack of current cellular network support.