By John Gruber
WorkOS Radar:
Protect your app against AI bots, free-tier abuse, and brute-force attacks.
Jason Snell, at Six Colors:
With the M4 Mac mini being powerfully tempting for desktop Mac users who crave power, Apple has upgraded the Mac Studio to blast past the mini in terms of performance. The base model, still starting at $1999, is powered by the M4 Max chip previously available only in the M4 MacBook Pro. And the new high-end Mac Studio, starting at the same $3999 price tag, is powered by a monstrous chip with 32 CPU cores (including 24 performance cores) and up to 80 GPU cores. It’s a chip never seen before anywhere — the M3 Ultra.
You heard me. For Apple’s fastest Mac ever — and it’s clear that it will be — Apple’s shipping a chip based on two high-end chips (fused together with Apple’s UltraFusion technology) from Apple’s previous processor generation. Weird, right? It seems like a few things are going on here: first, that the development of the Ultra chip takes longer and that Apple won’t commit to shipping an Ultra chip in every chip generation. Second, that the first-generation three-nanometer chip process of Apple’s chipmaking partner, TSMC, isn’t as dead and buried as generally thought. Just this week Apple also introduced an iPad Air with an M3 processor, and of course the new iPad mini shipped with an A17 Pro processor based on the same process.
This M3/M4 generational fork — the M3 Ultra chip debuting in new Mac Studio models alongside the M4 Max — was so unexpected that, during my embargoed press briefing about the news yesterday, I thought the Apple rep misspoke when he said M3, not M4, for the Ultra models. But no, the Ultra chip really is a generation behind. When asked the obvious question — why — Apple’s answer was straightforward: the Ultra chips take a lot longer to engineer.
The M4 Max Studio models are, computationally, equivalent (exactly, I think) with the M4 Max MacBook Pros that debuted October 30, maxing out (no pun intended) at 16 CPU cores, 40 GPU cores, 8 TB of storage, and 128 GB of RAM. The M4 Max Studio models start at $2,000, but that starting price only gets you a 14-core CPU, 32-core GPU, 16-core Neural Engine, 512 GB of storage, and a measly 36 GB of RAM.
The intriguing M3 Ultra models start at $4,000, which gets you a 28-core CPU, 60-core GPU, 32-core Neural Engine, 1 TB of storage, and a healthy 96 GB of RAM. Available upgrades to, uh, ultra out the Ultra models:
SSD storage options for the Ultra models go up to 16 TB (a cool $4,600 over the base storage).
Jason Snell, writing at Six Colors:
Let’s start with the surprises. Both M4 MacBook Air models are priced $100 less than their predecessors: $1199 for the 15-inch model and $999 for the 13-incher. If I’m not mistaken, this is the first time that the new-generation design of MacBook Air introduced with the M2 chip has been available at the classic $999 price at launch. (The M1 Air, based on the Intel-era visual design, debuted at $999, but the M2 Air debuted at $1199 and only reached $999 when it was offered as an older model alongside the M3 Air.) As of now, the M4 Air can hold down the sub-$1000 price point all on its own, and previous models are mostly discontinued.
Another surprise is the the new color option: Space Gray is out. The ultra-dark-blue Midnight remains, as do the classic Silver and hint-of-champagne Starlight. The new color is Sky Blue, which apparently is a metallic light blue that really shows itself as a color gradient when viewed at various angles.
Very cool that the new M4 starts at $999. Each successive generation of Apple Silicon, at least in laptops, is getting more and more predictably regular.
Mark Gurman, reporting for Bloomberg on 6 December 2024, regarding Apple’s first in-house cellular modem, “Apple Plans Three-Year Modem Rollout in Bid to Top Qualcomm”:
For now, the modem won’t be used in Apple’s higher-end products. It’s set to come to a new mid-tier iPhone later next year, code-named D23, that features a far-thinner design than current models. The chip will also start rolling out as early as 2025 in Apple’s lower-end iPads.
We now know the name of that modem, the C1, from its debut in the iPhone 16e last month. Then, also on December 6, in a separate report headlined “Apple Explores Macs, Headsets With Built-In Cellular Data”:
The first modem will also appear in low-end iPads next year, with the 2026 update coming to Pro versions of the iPhone and iPad.
The cellular models of the new 11th generation iPads announced yesterday do not, it turns out, use the C1. The specs don’t match those of the iPhone 16e, and when I asked an Apple representative, they confirmed that none of the new iPads (including the Airs) use the C1 modem. (But, Apple reassured me, they all offer terrific cellular networking.)
I’m not saying Gurman was wrong, because there are nine full months left in 2025 for Apple to release a 12th-generation low-end iPad with the C1. The previous (10th) generation came out in October 2022, but the 9th generation came in September 2021, just 13 months prior. And this week’s new M3 iPad Airs replaced M2 models that arrived just 10 months ago. But, you know, it sure seems doubtful Apple is going to rev this hardware in 2025, so I’ll place my bet that he was wrong about this too.
(And yes, a Bloomberg Terminal subscription really does start at $32,000/year per seat.)
Mark Gurman, in his Power On column for Bloomberg, on January 12:
The new entry-level iPads — J481 and J482 — will get faster processors and Apple Intelligence. The current models have the A14 chip and 4 gigabytes of memory. Look for the new versions to have the A17 Pro chip, matching the iPad mini, and a bump to 8 gigabytes of memory. That’s the minimum needed to support the new AI platform.
The new iPads sport the A16 chip and thus do not support Apple Intelligence. But who cares about little details like that when you know the codenames, which is what really matters.
I’ll bet what happened is that Gurman was right, and the new iPads were set to use the A17 Pro chip and support Apple Intelligence. But after Gurman spoiled it seven weeks ago, Apple scrapped those plans and changed the chips to the A16 just to spite him.
Tapbots:
v2.3 is now available on the App Store for Mac and iOS/iPadOS! What’s new?
- Grouped Notifications (Mention and Notification tabs are now merged)
- Support for AlphaNumeric Post IDs (Can now log into more services like GoToSocial)
- Accessibility Improvements
- Bug Fixes
I don’t like grouped notifications, but I’ve got nothing to complain about, because there’s a simple toggle at the top to just show mentions. Perfect.
The big news from Tapbots, though, is the announcement of Phoenix, a dedicated client for Bluesky:
Why two different clients? Why not one that supports both?
While there may be some conveniences of an app that supports multiple social media protocols, we believe the experience will be much better overall if we keep them separate. We do plan to provide a way to cross-post between them so you don’t have to write duplicate posts.
Hear hear to that.
Mark Gurman, yesterday at noon ET:
It’s not an “Air” — but the new Mac Studio, codenamed J575, appears to be imminent. It could be announced as early as this week along with the new MacBook Airs. There are signs these will come with an M4 Max but that its new Ultra chip will actually be an M3 Ultra.
Quite the scoop breaking this news after Apple started briefing media about it under NDA yesterday.
He’s not fooling anyone by dropping the J575 codename (which Apple would never include in a media briefing). That’s a bit of ham-fisted misdirection to make it seem like his source for this came from a product-aware source inside Apple, when in fact he almost certainly got it from someone in the media yesterday. (Codenames in and of themselves aren’t much of a secret inside Apple. That’s one reason they keep them so boring: letter-digit-digit-digit, usually.)
Apple conducted virtual media briefings yesterday for the iPad (M3 iPad Airs and A16 regular iPads) and Mac (M4 MacBook Airs and M4 Max/M3 Ultra Mac Studios). Apple announced the new iPads on Apple Newsroom yesterday morning at 9:00am ET, before those media briefings took place — the briefings were a recap of the announced news. Apple announced the new Macs today at 9:00am ET, after yesterday’s media briefings, which were under embargo until this morning. If you think it’s a coincidence that Gurman dropped zero last-minute tidbits about the new iPads (which were not briefed to the press ahead of time), but did drop the surprise M3 Ultra Mac Studio news (which was briefed, under embargo, ahead of time), I have a bridge to sell you.
He did the same thing with the VisionOS 2.4 news (Apple Intelligence, the new Spatial Gallery app, guest mode improvements). Apple held media briefings to share this news on Friday 14 February, under the condition that it was embargoed until the VisionOS 2.4 beta dropped the next week. But Gurman ran a report at Bloomberg with the embargoed info on Saturday 15 February. The only stuff he’s right about lately is what he gets from someone (or someones?) in the media leaking him embargoed info. It’s not going to take Sherlock Holmes for Apple to figure this out, especially when most of the Mac briefings yesterday were later in the day, after Gurman’s tweets. I’d put even money on him burning his source yesterday.
Ron Filipkowski:
Trump’s Sec of Agriculture Brooke Rollins says the solution to high egg prices for Americans is to get some chickens and raise them in your backyard.
No exaggeration. She’s selling the idea of everyone raising chickens in their back yards as “awesome”, with a laugh and a smile. And then the Fox News host (Rachel Campos-Duffy — wife of Transportation Secretary Sean Duffy — this whole world is comprised of socially-inbred reality-TV has-beens), smiling and laughing, concludes with “I think everyone who isn’t a farmer right now wants to be, so you’re in the right department, Brooke!”
This is a cult. No sense of “Hey, maybe this egg situation wasn’t so simple. Maybe this blowhard president isn’t going to solve the bird flu and halt inflation on day one...” — as they check their calendar and see that we’re already up to day 43 and their supermarket hasn’t had any eggs, at any price, in a week. No, instead, they’ve decided the answer is that all good-thinking Americans now happily want to be chicken farmers.
Next month: the fun of home dentistry.
Zac Hall, writing at 9to5Mac:
Leitmotif, the team behind the awesome diff and merge Mac app Kaleidoscope, is expanding its portfolio of native Mac apps for developers. The company has acquired Taska, a native Mac app that serves as a frontend for web services like GitHub and GitLab. [...] To celebrate its release of Taska 1.3, Leitmotif is discounting its apps by 50% for a limited time.
When Taska debuted last year, its original developers (Made by Windmill) sponsored DF for the week to promote it (the app was briefly named Sonar, before some sort of legal contretemps prompted a change), and thanking them, I wrote:
Taska combines the lightweight UI of a to-do app with the power of enterprise-level issue tracking, all in a native app built by long-time Mac nerds. The interface is deceptively simple, and very intuitive. Fast and fluid too. Everything that’s great about native Mac apps is exemplified by Taska. If you’ve ever thought, “Man, if only Apple made a native GitHub client...”, you should run, not walk, to download it.
Taska saves all your changes directly to GitHub/GitLab using their official APIs, so your data remains secure on GitHub’s servers — not Taska’s. Do you have team members not using Taska? No problem. Changes you make in Taska are 100% compatible with the web UI.
Leitmotif’s Kaleidoscope is a longtime stalwart in any Mac nerd’s toolbox. I can’t think of a better sibling to an app like Taska. (A few weeks ago I ran into a gnarly syncing glitch with a long log file, where there wasn’t just an old version and new one, but two different “new” versions from two different machines. Kaleidoscope got me out of that jam, no sweat.)
Funny piece — if your surname isn’t “Null” — by Oyin Adedoyin for The Wall Street Journal (News+ link):
Even those without the last name Null are finding themselves caught in the void. Joseph Tartaro got a license plate with the word “NULL” on it nearly 10 years ago. The 36-year-old security auditor thought it would be funny to drive around with the symbol for an empty value. Maybe a police officer who tried to give him a ticket would end up writing null into the system and not be able to process it, he joked to himself.
In 2018 he paid a $35 parking ticket. Soon afterward, he said, his mailbox was flooded with hundreds of traffic tickets for incidents he hadn’t been involved in. Tickets were from other counties and cities for vehicles of different colors, makes and models. A database had associated the word “null” with his personal information and citations were sent to Tartaro, who lives in Los Angeles.
Ben Stiller, in a delightful piece for The New York Times on working up the gumption to tell Gene Hackman — with whom he was working in Wes Anderson’s excellent The Royal Tenenbaums, his favorite Hackman movie:
“ … but I have to say for me, there is one movie you made that means so much to me. It might sound crazy, but I think it’s the reason I wanted to make movies. It’s ‘The Poseidon Adventure.’ It literally was my favorite movie when it came out. I think I was 7 or something and I went to see it in the theater about 10 times, then watched it repeatedly whenever it was on TV. It was so formative, and you were so good in it, and it just for me was my favorite movie for so long because of the excitement of that incredible score and those actors and the action and just all of it. It really changed my life and just … made me want to make movies.”
He smiled a little. He looked forward, thinking, perhaps about the movie, as if it hadn’t crossed his mind for a long time. Then he grinned and said:
“Money job.”
I can hear those words in Hackman’s voice. And I can see the grin.
Dan Moren, writing at Six Colors:
The most consequential part of the Air’s update — perhaps the only real update — is the M3 processor, which brings with it GPU-based capabilities like hardware-accelerated ray tracing and video encoding and decoding for ProRes and ProRes RAW.
Otherwise, the Air is basically unchanged: it comes in 11-inch and 13-inch versions, features the same cameras, battery life, the exact same dimensions, and the same accessory compatibility as its M2-based predecessor. It even comes in the same colors — Space Gray, Blue, Purple, and Starlight — at the same prices starting at $599.
A true speed-bump update — no big whoop, but it’s good for the platform for devices to get regular speed-bump updates in between major new revisions. The previous M2 iPad Air models only came out in May of last year, alongside the M4 iPad Pro models. Just like those M2 iPad Air models, these new M3 iPad Airs have 9-core GPUs. The current (not for long?) M3 MacBook Airs are offered with 8- and 10-core GPUs. I presume these 9-core M3 chips used for the iPad Air are binned chips that didn’t have 10 good GPU cores?
The new Magic Keyboard for Air is interesting in that it seems to meld parts of the older Magic Keyboard with the Magic Keyboard for iPad Pro last May. While the new Magic Keyboard includes a function row and a larger trackpad like its Pro compatriot, it lacks haptics in the trackpad and backlit keys, and it seems to be built on the same design of the original silicone exterior instead of the new aluminum-based model. But you get some cost savings for that: it’s just $269 instead of $299. Also, it only comes in white — black keyboards are for pros, I guess.
$269 feels like a crummy deal. The new-from-last-year $299 Magic Keyboard for iPad Pro, with an aluminum top, feels way more than $30 better than the old-style silicone-covered ones like this new Magic Keyboard for iPad Air. It kind of feels like a design failure of some sort that these new iPad Airs can’t use the same Magic Keyboards as the iPad Pros of the same size.
The base iPad’s update is perhaps somewhat more disappointing, as that model was introduced in 2022 and its A16 processor will make it one of the few current main-line Apple devices — perhaps only — not to support Apple Intelligence.
The recently updated iPad Mini (October) has an A17 Pro chip, and thus supports Apple Intelligence. But the iPad Mini starts at $500, and the regular iPad still starts at just $350. The just-plain iPad is really the only “budget” device that Apple makes. There are no iPhone or Mac models in that price range.
Apple:
Apple is committed to being transparent about government requests for customer data and how we respond. We publish a Transparency Report twice a year disclosing the number of government requests for customer data Apple receives globally.
Apple’s most recent report for the United States covers January to June 2023. They didn’t always lag this far behind. In November 2021 they issued the report for the second half of 2020, so that report came out 11 months after the period it covered. In September 2023 they issued the report covering January to June 2022, 15 months after the period covered. For all I know, they’ll come out with the report for the second half of 2023 sometime this month, continuing to lag 15 months behind the reporting periods. But if that’s the standard schedule for publishing these reports, they should say so. We should know when to expect them.
I don’t think there’s anything worrisome or fishy going on here, but given the recent brouhaha over the UK’s secret gag order demand for Apple to build a backdoor into iCloud Advanced Data Protection, along with the Biden administration’s shameful downplaying of that demand, it has me looking as much at what Apple doesn’t say about government data demands as what Apple does say about them.
Elizabeth Chamberlain, writing for iFixit:
But it’s still missing MagSafe, for no obvious reason other than making the phone less appealing to consumers than the rest of the 16 lineup. Wireless charging without the perfect alignment that MagSafe allows is troubling.
I’ve been waiting for iFixit’s teardown to see if removing MagSafe components might help explain the 16e’s physically larger battery. It doesn’t seem to. The 16e battery seems taller, not thicker, and the MagSafe components in an iPhone 15 don’t seem thick or space consuming. But there remains a very obvious reason for its exclusion: cost. The 16e is priced $200 less than a comparable regular 16, so something has to give, and MagSafe, alas, is one of those things.
The 16e did garner a 7/10 repairability score — very high for an Apple product from iFixit. But their party line is that you still shouldn’t buy one, opting instead for a refurbished older iPhone 14. Refurb iPhones are great, and they’re popular for a reason, but it feels like recommending refurb over new is dogma for iFixit at this point. When’s the last time they recommended any new product? For $600 I think it’s hard to beat a new iPhone 16e for current value and future-proofing.
President Donald Trump, on his very popular bespoke social network (random capitalization and various typos sic):
All Federal Funding will STOP for any College, School, or University that allows illegal protests. Agitators will be imprisoned/or permanently sent back to the country from which they came. American students will be permanently expelled or, depending on on the crime, arrested. NO MASKS! Thank you for your attention to this matter.
Hartley Charlton, writing for MacRumors in October 2022:
The fourth-generation iPhone SE will feature a 6.1-inch LCD display and a “notch” cutout at the top of the display, according to Display Supply Chain Consultants (DSCC) analyst Ross Young.
Good call on the size and notch, but the 16e display is OLED, not LCD. Overall, though, I’ll award Young a Being Right Point for this call from 2022.
Moving to an all-screen design, there will no longer be space for a capacitive Touch ID Home button in the device’s bottom bezel. Multiple reports, including information from MyDrivers and Apple analyst Ming-Chi Kuo suggest that Apple is planning to add a Touch ID Side button to the iPhone SE, much like the iPad Air and iPad mini.
Real shocker there that Kuo and the fabulists at “MyDrivers” were wrong on that. If you follow Charlton’s link on Kuo’s name above, it points to this 2019 report wherein Kuo reported that Apple was planning a 2021 iPhone that would have neither a Lightning nor USB-C port “and provide the completely wireless experience”.
Chance Miller, writing last week at 9to5Mac:
Dark Noise developer Charlie Chapman is out with a new Mac utility called “Framous.” The app aims to be the best way to add device frames to screenshots. [...]
Here are the ways Framous aims to streamline this process:
- Auto-detect your device based on your screenshot to pick the right frame from a growing library of devices
- Combine multiple devices into a single image, or bulk export multiple separate images at once
- Quick customization options to change frame colors and more
- Automate your screenshot framing with Shortcuts support for even more efficient workflows
There are a bunch of ways you can add device frames to screenshots like this, but none as clever, fast, and easy as Framous. I love it. So many little details. You can just drop a screenshot in and copy a framed version out with zero fuss, but there are also all sorts of tweaks and adjustments you can make, right down to choosing which shade of titanium to color your specific iPhone Pro model. Chapman has a great 20-minute walkthrough video showing all of Framous’s features, and he posted a bunch of shorter videos showcasing specific features to Mastodon. I was sold after watching just one of these.
Framous is completely free to use with nice-looking generic device frames, and a $20 one-time purchase to unlock the exquisitely-detailed “real” frames covering all devices through the end of 2025. Or, a $10/year subscription to keep up to date with future device frames. Available at the Mac App Store.
Basic Apple Guy (with screenshot):
The same tagline from Apple’s 2008 announcement for the original MacBook Air.
On the cusp of that announcement at Macworld Expo, AppleInsider photographed a bunch of banners with that slogan Apple had hung inside Moscone West. I swear I’m not making this up, but a bunch of people were speculating that the big announcement would be a deal with Adobe to bring Adobe Air (their still-in-progress next-gen Flash platform) to the iPhone (which was just over six months old).
Fond memories. Here are my initial thoughts and observations on the MacBook Air, post-keynote, and here’s the January 2008 archive of Linked List posts at DF. There were a lot of bad early takes on the Air.
Dan Moren, writing at Six Colors:
In a whitepaper posted to Apple’s developer site entitled “Helping Protect Kids Online”, the company details several improvements it’s rolling out in upcoming software updates, including making it easier to set up child accounts, providing age ranges to developers, and filtering content on the App Store. [...]
It’s also worth noting that these announcements are happening against the backdrop of more stringent age-verification laws enacted in U.S. states like Texas and Oklahoma. Critics of those laws contend that they unfairly target LGBTQ+ communities. Apple, for its part, says that it holds to a standard of data minimization, not sharing any more information than is necessary. So, for example, offering developers access to the age range of a user — with the consent of a parent — rather than providing a birthdate.
From Apple’s whitepaper (PDF):
At Apple, we believe in data minimization — collecting and using only the minimum amount of data required to deliver what you need. This is especially important for the issue of “age assurance,” which covers a variety of methods that establish a user’s age with some level of confidence. Some apps may find it appropriate or even legally required to use age verification, which confirms user age with a high level of certainty — often through collecting a user’s sensitive personal information (like a government- issued ID) — to keep kids away from inappropriate content. But most apps don’t. That’s why the right place to address the dangers of age- restricted content online is the limited set of websites and apps that host that kind of content. After all, we ask merchants who sell alcohol in a mall to verify a buyer’s age by checking IDs — we don’t ask everyone to turn their date of birth over to the mall if they just want to go to the food court.
Meta has been vocally backing the various state initiatives that Moren referenced, that would require app stores to verify the exact age of children. To use Apple’s apt metaphor, Meta wants the mall owner to require checking ID for everyone who enters the mall, not just those who purchase alcohol. Meta also, of course, wants itself to then have access to those exact ages verified by the app store — it wants to know the exact age of every child using its platforms, and wants the App Store and Play Store to do the dirty work of verifying those ages and providing them via APIs to developers.
There are a lot of parents who supervise their kids’ online activities and simply don’t permit them to use platforms — like, oh, say, Meta’s — where age restrictions are necessary for some content. So why should those parents be required to provide privacy-intrusive verification of their kids’ birthdates just to let the kids play and use innocent G-rated games and apps?
Meta is clearly in the wrong here, and they’re using culture-war fear-mongering to try to get what they want through misdirection.
Jeremy Keith, writing at Adactio:
Ask anyone about their experience of using websites on their mobile device. They’ll tell you plenty of stories of how badly it sucks.
It doesn’t matter that the web is the perfect medium for just-in-time delivery of information. It doesn’t matter that web browsers can now do just about everything that native apps can do.
In many ways, I wish this were a technical problem. At least then we could lobby for some technical advancement that would fix this situation.
But this is not a technical problem. This is a people problem. Specifically, the people who make websites.
There are mobile web proponents who are in denial about this state of affairs, who seek to place the blame at Apple’s feet for the fact that WebKit is the only rendering engine available on iOS. But WebKit’s limitations have nothing to do with the reasons so many websites suck when experienced on mobile devices. The mobile web sucks just as bad on Android. Apple’s WebKit-only rule on iOS is just a useful scapegoat for the fact that most websites, as experienced on phones, are designed and engineered to suck. It’s not whatever features WebKit lacks that Chrome-myopic web developers want. It’s all the crap that web developers add — tens of megabytes of JavaScript libraries and frameworks; pop-ups and pop-overs all over the screen; scrolljacking and other deliberate breakage of built-in UI behavior — that makes the experience suck. We should be so lucky if the biggest problems facing the web experience on iPhones were the technical limitations of WebKit.
And the app experiences from the same companies (whose websites suck on mobile) are much better. Not a little better, but a lot better — as I wrote in a piece in January. The truth hurts, just like the experience of using most websites on mobile.
John Cassidy, writing for The New Yorker (requires a free account to read, annoyingly):
Of course, these calculations can’t be taken literally. Even Musk has said that he wants to protect essential workers. If the entire federal workforce were eliminated, there’d be no one to make sure that federal benefits got paid or that federal taxes were collected. The spending and revenue figures would crater; essential services like veterans’ hospitals, air-traffic-control systems, and border-crossing stations would be completely abandoned. But this thought experiment does illustrate the point that “bloated” payrolls aren’t what is driving federal spending and deficits. Since the nineteen-seventies, as the accompanying chart shows, the total number of federal employees has remained fairly steady.
Here’s a copy of the chart. Cassidy continues:
Unlike the figures from the U.S. Office of Personnel Management, the chart, which comes from the Federal Reserve Economic Database, counts members of the U.S. Postal Service as federal employees. It does show that the federal workforce has grown in recent years, but it’s still no larger than it was thirty or forty years ago. During the interim, total employment elsewhere in the economy has grown steadily alongside population growth. Consequently, the size of the federal workforce relative to the workforce at large has fallen considerably, as the following chart shows.
Here’s a copy of that second chart.
I knew the supposed justifications for the whole DOGE endeavor were a sham, but until this piece I was under the incorrect assumption that the federal government workforce has been growing steadily for decades, at least keeping pace with its percentage of the overall US workforce. The opposite is true — because the federal workforce size has remained steady while the population has continued to grow, its share of the overall workforce has in fact shrunk considerably.
Jason Snell, writing last week at Six Colors:
While a lot of us have gotten excited about the potential of Apple’s immersive video format, the truth is that the Vision Pro is also a great viewer of more traditional 3-D video content. And Apple has built a new visionOS app to highlight great spatial content: Spatial Gallery.
Think of Spatial Gallery as something sort of like the TV app, but for spatial videos, photos, and panoramas. The content comes from Apple as well as third-party content sources, and Apple is curating it all itself. The company says the content will be updated on a regular basis, and among the demo content I saw featured was some of 3-D (not immersive) behind-the-scenes content from various Apple TV+ productions such as “Severance” and “Shrinking.”
Just as the Apple Watch has its own app on iOS, so too will the Vision Pro. The new Vision Pro iOS app will be available with iOS 18.4, and will automatically appear on the iPhones of people who have Vision Pros. Of course the app will show off new content and offer tips, but it’s also functional: If you add highlighted media content via the app, it’ll be set to download on the Vision Pro. Similarly, you can use the Vision Pro app to remotely download apps to your Vision Pro, so they’re ready for you when you put the headset on.
VisionOS 2.4 is also making some big improvements to guest mode, making it much easier to let someone else use your Vision Pro. It remains to be seen if Vision is ever going to be a successful platform, but the potential is clearly there, and Apple is definitely rolling on it.
Like any great caricature, Myers’s Elon Musk conveys a better sense of Musk than watching Musk himself does. A cruel and infinitely self-satisfied know-it-all, whose utter self-confidence runs counter to the fact that he’s unfathomably awkward, as uncoordinated socially as he is physically. Just an utter and total spaz, who believes no one’s jokes are funnier than his own. The sort of person no one likes but who has nevertheless parlayed tremendous wealth into great power, forcing his influence upon the world.
Ming-Chi Kuo, back on Sunday September 15:
Based on my latest supply chain survey and pre-order results from Apple’s official websites, I’ve compiled key data on iPhone 16’s first-weekend pre-orders for each model, including pre-order sales, average delivery times, and shipments before pre-order. [...]
Analysis and Conclusions:
iPhone 16 series first-weekend pre-order sales are estimated at about 37 million units, down about 12.7% YoY from last year’s iPhone 15 series first-weekend sales. The key factor is the lower-than-expected demand for the iPhone 16 Pro series.
Note that pre-orders for the iPhone 16 lineup only started two days prior, on Friday September 13. Here were Kuo’s estimates for first-weekend pre-order sales, compared year-over-year to the equivalent iPhone 15 models:
iPhone 16 Pro Max | -16% |
iPhone 16 Pro | -27% |
iPhone 16 Plus | +48% |
iPhone 16 | +10% |
These numbers bear no resemblance to Apple’s actual financial results for the October-December quarter. There was no marked downswing in demand for the 16 Pro and Pro Max, and there was no wild upswing in demand for the 16 Plus. Just one month after posting the above opening-weekend nonsense, Kuo himself reported, “iPhone 16 orders were cut by around 10M units for 4Q24–1H25, with most of the cuts affecting non-Pro models.” So in September Kuo claimed Pro sales were alarmingly down and regular iPhone 16 and 16 Plus sales were surprisingly strong, but in October he said Apple cut orders mostly with the “non-Pro models”. So why was any of this reported as news?
My thesis has long been that while Kuo clearly has some insight into some of Apple’s suppliers in Asia, he has no insight whatsoever into Apple’s sales. How could he? “Apple’s official websites” don’t publish sales numbers. I think he just pulls this stuff right out of his ass and hand waves that it has something to do with the estimated ship dates for new iPhone models. Further, I think Kuo picks these numbers not at random, and not based on an honest attempt to even guess the actual sales, but rather to create headlines and inject his name into the news. Has he ever once issued a “survey” that reported that iPhone demand was pretty much in line with expectations? If all you did was follow Ming-Chi Kuo’s reporting, you’d think Jeff Williams is incompetent and should have been fired years ago, because he has no ability to accurately forecast demand for Apple’s most important product. Clickbait in its purest form, detached completely from any factual reality.
My thanks to WorkOS for sponsoring last week at DF. Does your app get fake signups, throwaway emails, or users abusing your free tier? Or worse, bots attacks and brute force attempts?
WorkOS Radar can block all this and more. Their simple API gives you advanced device fingerprinting that can detect bad actors, bots, and suspicious behavior.
Your users trust you. Keep it that way. Check out WorkOS Radar today.
TMZ:
Seems Elon Musk is truly going to colonize Mars ... even if he has to do it himself, ’cause the tech mogul just welcomed his 14 child! Elon helped break the news Friday along with Shivon Zilis, with whom the billionaire already had three children.
You know what you call a man who has 14 children with four different mothers and has little interest or involvement in most of their lives? You call him a weirdo. This isn’t some quirk or fluke. He’s obviously some sort of eugenics freak who isn’t interested in family or fatherhood, but in spreading his seed like he’s some sort of prized racehorse. How is this any different than polygamy or assembling some sort of harem, other than that polygamists might live with and take an active role in raising their various children?
Think too about how conservative news outlets would portray any woman who had children with four different fathers (and counting). Or if Musk were a black man working for a Democratic president. (Imagine the Fox News take if Barack Obama had five children from three different mothers, like Donald Trump does.)
Nora Deligter, writing for Screen Slate in June 2023, “Elegy for the Screenshot”:
About five years ago, Catherine Pearson started taking screenshots of every bouquet featured on The Nanny (1993–1999), the six-season CBS sitcom that was then streaming on Netflix. She was just becoming a florist, and she found the arrangements — ornate, colorful, and distinctly tropical — inspirational. She now keeps them in a folder on her desktop, alongside screenshots of flower arrangements featured on Poirot (1989–2013), the British detective drama. A few months ago, however, Pearson suddenly found that when her fingers danced instinctively toward Command-Shift-3, she was greeted by a black box where her flowers used to be, a censored version of what she had meant to capture.
It was around this time when streaming platforms like Netflix, HBO Max, Amazon Prime, and the Criterion Channel imposed a quiet embargo on the screenshot. At first, there were workarounds: users could continue to screenshot by using the browser Brave or by downloading extensions or third-party tools like Fireshot. But gradually, the digital-rights-management tech adapted and became more sophisticated. Today, it is nearly impossible to take a screenshot from the most popular streaming services, at least not on a Macintosh computer. [...]
For PC users, this story takes a different, and happier, turn. With the use of Snipping Tool — a utility exclusive to Microsoft Windows, users are free to screen grab content from all streaming platforms. This seems like a pointed oversight, a choice on the part of streamers to exclude Mac users (though they make up a tiny fraction of the market) because of their assumed cultural class. This assumption isn’t unreasonable. Out of everyone interviewed for this article, only one of them was a PC user.
Deligter’s essay has been sitting in my long (and ever-growing) list of things to link to ever since she published it back in 2023. I referenced it in my post earlier today re: Matthew Green’s entreaty to Apple to add “disappearing messages” to iMessage, and re-reading it made me annoyed enough to finally write about it.
I’m not entirely sure what the technical answer to this is, but on MacOS, it seemingly involves the GPU and video decoding hardware. These DRM blackouts happen at such a low level that no high-level software — any sort of utility you might install — can route around them. I think Windows still offers easy screenshotting of frames from DRM video not because the streaming services somehow don’t care about what Windows users do (which, when you think about it, would be a weird thing not to care about, given Windows’s market share), but because Windows uses a less sophisticated imaging pipeline. Or perhaps rather than less sophisticated, it’s more accurate to say less integrated. These DRM blackouts on Apple devices (you can’t capture screenshots from DRM video on iPhones or iPads either) are enabled through the deep integration between the OS and the hardware, thus enabling the blackouts to be imposed at the hardware level. And I don’t think the streaming services opt into this screenshot prohibition other than by “protecting” their video with DRM in the first place. If a video is DRM-protected, you can’t screenshot it; if it’s not, you can.
On the Mac, it used to be the case that DRM video was blacked-out from screen capture in Safari, but not in Chrome (or the dozens of various Chromium-derived browsers). But at some point a few years back, you stopped being able to capture screenshots from DRM videos in Chrome, too — by default. But in Chrome’s Settings page, under System, if you disable “Use graphics acceleration when available” and relaunch Chrome, boom, you can screenshot everything in a Chrome window, including DRM video. You can go to the magic URL chrome://gpu/
before and after toggling this setting to see a full report on the differences — as you’d expect, it turns off all hardware acceleration for video encoding/decoding, compositing, and more. You wouldn’t want to browse like this all the time (certainly not on battery power), but it’s a great trick to know for capturing stills from videos.
What I don’t understand is why Apple bothered supporting this in the first place for hardware-accelerated video (which is all video on iOS platforms — there is no workaround like using Chrome with hardware acceleration disabled on iPhone or iPad). No one is going to create bootleg copies of DRM-protected video one screenshotted still frame at a time — and even if they tried, they’d be capturing only the images, not the sound. And it’s not like this “feature” in MacOS and iOS has put an end to bootlegging DRM-protected video content. This “feature” accomplishes nothing of value for anyone, including the streaming services, but imposes a massive (and for most people, confusing and frustrating) hindrance on honest people simply trying to easily capture high-quality (as opposed to, say, using their damn phone to take a photograph of their reflective laptop display) screenshots of the shows and movies they’re watching. ★
Matthew Green:
If you install WhatsApp, Facebook Messenger, Signal, Snap or even Telegram(please don’t!) you’ll encounter a simple feature that addresses this problem. It’s usually called “disappearing messages”, but sometimes goes by other names.
I’m almost embarrassed to explain what this feature does, since it’s like explaining how a steering wheel works. Nevertheless. When you start a chat, you can decide how long the messages should stick around for. If your answer is forever, you don’t need to do anything. However, if it’s a sensitive conversation and you want it to be ephemeral in the same way that a phone call is, you can pick a time, typically ranging from 5 minutes to 90 days. When that time expires, your messages just get erased — on both your phone and the phones of the people you’re talking to.
A separate feature of disappearing messages is that some platforms will omit these conversations from device backups, or at least they’ll make sure expired messages can’t be restored. This makes sense because those conversations are supposed to be ephemeral: people are clearly not expecting those text messages to be around in the future, so they’re not as angry if they lose them a few days early. [...]
To recap, nearly every single other messaging product that people use in large numbers (at least here in the US) has some kind of disappearing messages feature. Apple’s omission is starting to be very unique.
I do have some friends who work for Apple Security and I’ve tried to talk to them about this. [...] When I ask about disappearing messages, I get embarrassed sighs and crickets. Nobody can explain why Apple is so far behind on this basic feature even as an option, long after it became standard in every other messenger.
I can only speculate why iMessage doesn’t offer this feature. Perhaps Apple doesn’t want to imply that “disappearing messages” are in any way guaranteed to be ephemeral, which would be impossible. Who’s to say the recipient hasn’t screenshotted them? And if Messages were to impose a software block against capturing a screenshot of a “disappearing message” (like the way you can’t capture screenshots of DRM-protected video), who’s to say the recipient hasn’t used another device to take a photograph of the display showing the ostensibly-ephemeral message? E2EE is a mathematical guarantee. There’s no way to offer such a guarantee regarding ephemerality, and perhaps that gives Apple pause.
But I think that would be letting a desire for perfection get in the way of offering a feature that’s useful and good enough. People who use disappearing messages on other platforms — and as Green points out, all of iMessage’s rivals offer the feature — understand the risks. Vanishingly few people understand the difference between “encrypted in transit” and “end-to-end encrypted”. But just about everyone intuitively understands that even a “disappearing message” might be screenshotted, photographed, or otherwise recorded. There’s an implicit trust between sender and recipient.
The other angle I can think of is complexity. Messages is one of Apple’s most-used apps, and in many ways it exemplifies Apple’s approach to software design and computing in general. Where critics see an app that is popular despite offering fewer features than its rivals, Apple (and I) see an app that is popular and beloved to some degree because it offers fewer features. All new features necessarily add some complexity, and disappearing messages would add quite a bit. Can you have two chats with the same person/group, one standard and one ephemeral? If so, now you’ve raised the specter of accidentally sending what’s intended to be a disappearing message to the non-ephemeral chat with that person or group. If not, how do you send a brief disappearing-message exchange with someone with whom you have a long archive of messages you want to keep forever? (Perhaps the idea of private browsing in Safari could serve as an inspiration for disappearing messages in Messages — an entirely separate mode with a distinct visual state.)
The basic idea of disappearing messages is pretty trivial and easily understood. A good design for implementing them in Messages is not trivial. Solving these hard design problems is what makes Apple Apple, though. They’ve added some rather superficial features to Messages (Genmoji and message effects for example), so I agree with Green that they ought to tackle disappearing messages and that surely they can find a way to do it where the added complexity doesn’t create confusion. It’s a hard challenge, to be sure, but a worthy one. Apple’s designers could really have some fun with this too, with novel ways to present “disappearingness” visually.
Meghan Bobrowsky and Jeff Horwitz, reporting for The Wall Street Journal:
Meta apologized Wednesday night for what it said was an “error” that led to graphic and violent videos flooding the feeds of a vast number of Instagram users, including minors. The videos, which were recommended on some users’ Reels tab, included people who appeared to have been shot to death and run over by vehicles. Some of the recommended videos had “sensitive content” warnings on them while others didn’t.
A Wall Street Journal reporter’s account featured scores of videos of people being shot, mangled by machinery, and ejected from theme park rides, often back to back. The videos originated on pages that the reporter didn’t follow with names such as “BlackPeopleBeingHurt,” “ShockingTragedies” and “PeopleDyingHub.”
“We accidentally started showing people the absolute worst stuff available on our platform” is one hell of a glitch.
Jeff Teper, president of collaborative apps and platforms at Microsoft:
In order to streamline our free consumer communications offerings so we can more easily adapt to customer needs, we will be retiring Skype in May 2025 to focus on Microsoft Teams (free), our modern communications and collaboration hub.
NPR:
Microsoft, which acquired Skype in 2011 for $8.5 billion, announced in a post on X on Friday that the iconic voice-over-Internet protocol (VoIP) service would soon go dark. It encouraged Skype users to instead migrate to a free version of Microsoft Teams — a communication app that helps users work together in real time.
In the more than two decades since it was founded, Skype has been largely overtaken by a bevy of competitors, such as FaceTime, WhatsApp, Zoom, and Slack.
The writing has been on the wall for a long time that Skype was no longer strategic for Microsoft. Really, even right after the acquisition, it never seemed Microsoft had any sort of plan for what to do with Skype — even though, at the time, it was their largest-ever acquisition.
But man, for a long while, Skype was singularly amazing, offering high-quality / low-latency audio calls at a time when everything else seemed low-quality / high-latency. I continued using Skype to record The Talk Show until a few years ago, and I can’t say I miss it. But I used Skype to record at least around 400 episodes — which means I’ve spent somewhere around 1,000 hours talking to people over Skype. I can close my eyes and just hear Skype’s kinda clunky but distinctive ringtone. In the early days of podcasting, seemingly every show used Skype because it was so much better than anything else. And it was free! It felt like the future. I don’t think it’s an exaggeration to say that if not for Skype, podcasting would’ve been set back several years.
Alex Heath, reporting for The Verge:
Meta has fired “roughly 20” employees who leaked “confidential information outside the company,” according to a spokesperson.
“We tell employees when they join the company, and we offer periodic reminders, that it is against our policies to leak internal information, no matter the intent,” Meta spokesperson Dave Arnold tells The Verge exclusively. “We recently conducted an investigation that resulted in roughly 20 employees being terminated for sharing confidential information outside the company, and we expect there will be more. We take this seriously, and will continue to take action when we identify leaks.”
These firings, of course, are the follow-up to one of my favorite headlines so far this year: “Meta Warns That It Will Fire Leakers in Leaked Memo”. As I wrote in that post a month ago:
It’s not fear of getting fired that keeps employees at most companies from leaking. It’s that they find themselves aligned with the company’s mission. They feel like part of a team that they want to see succeed, and they naturally adopt an attitude of being a team player. Team players don’t leak the playbook because they don’t like the coach’s play-calling or how much playing time they’re getting. I’ve never gotten the sense that that sort of attitude exists at Meta.
I’m not sure this public crackdown will help. Meta seems to be leaning into fear to keep employees in line, rather than team spirit. Their war on leakers might prove about as effective as America’s decades-long “war on drugs”, that saw illegal drug use rise, not fall, even while our prisons filled up with non-violent drug-law offenders. What’s the Princess Leia line? “The more you tighten your grip, Tarkin, the more star systems will slip through your fingers.” One longtime reader, who works at Netflix, contacted me after my month ago post and observed:
That is such a great take on Meta’s leaks. Netflix stuff almost never leaks, because Netflix is a place full of people who don’t want to leak things. There are virtually no barriers, just a culture and collection of people who don’t do that.
Penalties are a deterrence. But the reason most people don’t commit crimes — whether it be shoplifting or murder — isn’t fear of the potential penalties. It’s that they’re good honest people who don’t want to steal (and definitely don’t want to kill anyone).
Founder Nirav Patel, writing this week on Framework’s company blog:
We went live this morning at the Framework (2nd Gen) Event with our biggest set of announcements yet: Framework Desktop, Framework Laptop 12, and the new Ryzen AI 300 Series Framework Laptop 13. You can watch a recording of the livestream on our YouTube channel.
Sean Hollister has a good roundup of the announcements at The Verge. Back in 2021 when Framework debuted with their first laptop, I expressed pithy skepticism regarding their modular approach. I’m still skeptical, but it’s hard not to root for them and cheer for their success. In principle, Framework’s “everything is a swappable, replaceable module” approach to system design is a fun nerdy throwback to the days when it was expected that you could get inside any computer and replace or upgrade its components yourself. And Framework’s style of modularity is designed with ease-of-use in mind, like snapping Lego blocks together. But as Hollister points out, Framework still hasn’t shipped a promised GPU upgrade component for its now two-year-old Framework 16 laptop.
Also of note is how much Framework is building around chips from AMD, not Intel. Is there a single category where anyone would say “Intel makes the best chips for this”? In an alternate universe where Apple had never moved the Mac to Apple Silicon, I’m not sure if it would be tenable for Apple to still be exclusively relying on Intel for x86 chips. Intel’s chips just aren’t competitive with AMD’s.
Ben Domenech interviewed President Trump yesterday in the Oval Office, after Trump’s meeting with UK Prime Minister Keir Starmer. The Spectator has published the entire transcript, and I read it so you don’t have to, to get the part about Apple and the UK’s encryption backdoor demand:
BD: But the problem is he runs, your vice president obviously eloquently pointed this out in Munich, he runs a nation now that is removing the security helmets on Apple phones so that they can —
DJT: We told them you can’t do this.
BD: Yeah, Tulsi, I saw —
DJT: We actually told him… that’s incredible. That’s something, you know, that you hear about with China.
It feels quite odd to strongly agree with Trump on something, but he’s not wrong about everything.
(Most of the interview is just bananas stuff, ping-ponging all over the place. I swear Trump even goes back to Hannibal Lecter, and his mistaken belief that political asylum policies are somehow related to foreign countries emptying their asylums for the criminally insane.)
Hamilton Nolan, in a 2021 piece for The Columbia Journalism Review, under the headline “Bezos Has Been Hands-Off. What if That Changes?”:
Bezos has given the paper the resources to be bigger and better, and, by most accounts, pretty much stayed out of the newsroom’s hair, besides appearing one day to present a bicycle to former editor Marty Baron. The Amazon boss has never been an overtly political man, except to the extent that he supports whatever helps him stay rich and take over the world with his robotic form of ultra-capitalism. But he is not inclined to spend his time on the phone haranguing Post editors about coverage decisions. When you are worth close to $200 billion, your time is too valuable for that.
There is no guarantee, however, that that will always be true. [...]
Discussing this question with nuance is not easy. The paper will always say that Bezos does not interfere. Bezos himself will always say that he does not interfere. Factions of the public on the right and the left will always hold that Bezos’s ownership inherently corrupts the paper’s coverage.
I do give Bezos credit for taking public ownership of his assertion of control over the paper’s opinion pages now. This is a major change, and he’s not trying to hide it or shy away from responsibility for it.
Jeff Bezos, in a memo he shared publicly on X:
I shared this note with the Washington Post team this morning:
I’m writing to let you know about a change coming to our opinion pages.
We are going to be writing every day in support and defense of two pillars: personal liberties and free markets. We’ll cover other topics too of course, but viewpoints opposing those pillars will be left to be published by others. [...]
I offered David Shipley, whom I greatly admire, the opportunity to lead this new chapter. I suggested to him that if the answer wasn’t “hell yes,” then it had to be “no.” After careful consideration, David decided to step away. This is a significant shift, it won’t be easy, and it will require 100% commitment — I respect his decision. We’ll be searching for a new Opinion Editor to own this new direction.
He owns the paper, and the opinion pages are the traditional place for a newspaper’s owner to assert their beliefs. And while Bezos was famously hands-off for the first decade of his ownership (he bought the Post from the Graham family for $250 million in 2013), this latest dictum doesn’t feel out of the blue or surprising in the least. It feels like the natural culmination of his asserting control over the paper’s opinion pages that started with his blockbuster decision to nix the paper’s endorsement of Kamala Harris just a few weeks prior to the election, and reached a breaking point when the paper refused to run a cartoon by Pulitzer-winning Ann Telnaes that mocked Bezos (along with other billionaires) for paying into Trump’s inauguration committee racket — prompting Telnaes to resign in righteous protest.
How are remaining staffers at the Post taking this? Not happily. Reports Liam Reilly, media reporter at CNN:
Current staffers echoed those sentiments. Philip Bump, who writes the “How to Read This Chart” newsletter at the Post, asked Bluesky “what the actual fuck” five minutes after the announcement went out. Post tech reporter Drew Harwell on Bluesky shared a summary of comments on the story generated by the Post’s own AI tool that highlighted “significant discontent” from readers and “a strong sentiment of betrayal among long-time subscribers.” And, tellingly, David Maraniss, an editor at the paper, said on Bluesky that he would “never write for (the Post) again as long as (Bezos is) the owner.”
More tellingly, the Post’s own media critic, the excellent Erik Wemple, intended to write about the policy change but saw his own column spiked. It’s a good sign that things have gone off the rails when a publication’s own media critic is disallowed from writing about their own publication.
Loved this remembrance by Manohla Dargis in The New York Times:
When Clint Eastwood needed a performer who could persuasively go boot-toe to boot-toe with him in his brutal 1992 western Unforgiven, he needed an actor who was his towering equal onscreen. Eastwood needed a performer with strange charisma, one who could at once effortlessly draw the audience to his character and repulse it without skipping a beat. This actor didn’t need the audience’s love, and would never ask for it. He instead needed to go deep and dark, playing a villain of such depravity that he inspired the viewer’s own blood lust. Eastwood needed a legend who could send shivers up spines. He needed Gene Hackman.
Just an unbelievable career, in such a wide variety of films. His roles in The Conversation, The French Connection, and Unforgiven are atop most people’s lists, and I do love each of those movies. But he was so good in everything. What a great Lex Luthor he was in 1978’s Superman. Mississippi Burning, The Royal Tenenbaums, Bonnie and Clyde, The Birdcage, Hoosiers. By chance, I just re-watched David Mamet’s Heist a few weeks ago. Like so many of Hackman’s movies, that’s another one that repays multiple viewings across decades.
I’ve spent the last six days using the iPhone 16e, and the experience has been a throwback. In many ways, the iPhone 16e both looks and feels like the modern-day progeny of the early Steve Jobs era iPhones. Early iPhones like the plastic 3G and 3GS, and the glass-back/metal-sides 4 and 4S were simpler offerings. Two colors, black and white. Single-lens inconspicuous cameras. The iPhone 16e feels like their direct descendent.
Let’s start with the camera. With just a single lens on the back, the iPhone 16e camera doesn’t just look less conspicuous compared to its dual- and triple-lens brethren, it feels less conspicuous. Especially for me, coming from several years of daily-driving an iPhone Pro model, the 16e feels strikingly smaller in hand and pocket because it lacks the entire “mesa” protrusion from which iPhone 16 and 16 Pro camera lenses further protrude.
Apple’s tech specs for iPhone thickness don’t include the camera lenses or camera mesas. Apple just measures and reports the thickness of the flat non-camera part of the phone. But those camera modules and lenses protrude quite a bit. Using a digital caliper, I measured the thickness of the three “levels” of the 16e, regular 16, and 16 Pro:
Base | Mesa | Lens(es) | |
---|---|---|---|
iPhone 16e | 7.8mm | — | 9.5mm |
iPhone 16 | 7.8mm | 9.6mm | 11.3mm |
iPhone 16 Pro | 8.3mm | 10.3mm | 12.5mm |
So not only does the 16e completely omit the mesa, but the thickness of the entire camera, from the lens to the front display, is less than the thickness of the iPhone 16 and iPhone 16 Pro at their mesas, not even including their lenses.
Just look at this screenshot from Apple’s comparison page, showing all three side-by-side in their black color options:
The iPhone 16e looks like a phone with a tiny camera on the back. The iPhone 16 Pro looks like a camera that also happens to be a phone. You can really feel the difference in hand, too — not just the weight, but the balance.1 You can feel that the 16 Pro’s extra camera hardware adds extra weight. Per Apple’s specs, the iPhone 16e weighs 167g; the 16 Pro 199g — a 16 percent difference. (Also take note of a clever touch: Apple’s default wallpapers for each phone subtly suggest how many camera lenses they have.)
The 16e camera lens is not flush with the back of the phone, but it protrudes so little (just 1.7mm by my measurement) that it harks back to when iPhone cameras first started jutting out from the back of the phones at all. The 16e still wobbles when laid on a tabletop, but dramatically less than a regular iPhone 16 or especially the iPhone 16 Pro, whose camera module seems downright bulbous in comparison. But the 16e’s 1.7mm camera lens protrusion is so minimal that, when put in a case, the phone does lay perfectly flat on a table, because the cases need no protective rim for the camera, because the 16e camera lens protrudes less than the thickness of the case. (Apple included two of its $39 Silicone Cases with my review kit, in blue and black. They’re fine, and feel exactly like Apple’s usual Silicone Cases.)
Because the “macro” mode on the recent regular and Pro iPhone models uses the 0.5× ultrawide camera, a secondary lens the 16e doesn’t have, the 16e doesn’t have a macro mode. Starting with the iPhone 13 Pro, macro mode has allowed iPhone Pros to focus on objects less than an inch away. But, because the 16e’s 1× camera has a smaller sensor and smaller lens than the 1× camera on more expensive iPhone models, it’s able to focus at shorter distances than those bigger and otherwise better 1× cameras. The 1× camera on an iPhone 16 Pro has a minimum focus distance of 24cm (~9.5 inches). The 1× camera on an iPhone 16e has a minimum focus distance of 12cm (~4.75 inches). Actual macro mode (on regular and Pro iPhone models) is better, but you don’t need it as much when the 16e’s lone camera can focus on objects at half the distance, just over 4 inches away, in its regular shooting mode.
The 16e’s inconspicuous camera comes with a price, of course: image quality. You can really see the difference in low light. The 16e camera is slower (resulting in blurry images with subjects in motion) and images are noisier. The difference is especially obvious when shooting in low light with Process Zero in Halide. It’s a fine camera though, for point-and-shoot purposes. For most people who might be considering the iPhone 16e, it’ll probably be the best camera they’ve ever owned. And there’s something to be said for the simplicity of just one lens, offering 1× and 2× fields of view. If you know what an ƒ-stop is, you probably shouldn’t buy an iPhone 16e. If you don’t know what an ƒ-stop is, you probably won’t notice any difference in camera quality from an iPhone 16 or even 16 Pro. It’s a perfect camera for anyone who just wants a decent camera.
Peruse Apple’s comparison page, comparing the 16e to the 16 Pro and regular 16, and you’ll spot dozens of small differences. But the one omission that grabbed the most attention (and generated the most “WTF Apple?” reactions) is MagSafe. I own a bunch of MagSafe peripherals, and personally would never want to buy an iPhone without it. I have a dock at my desk (great with StandBy mode), a charger at my nightstand, and convenient doodads like this magnetic folding stand. One week into using the 16e as my main phone, and I still miss MagSafe as much as I did the first night.
But according to Apple representatives, most people in the 16e’s target audience exclusively charge their phones by plugging them into a charging cable. They tend not to use inductive charging at all, and when they do, they might not care that the 16e is stuck with a pokey 7.5W Qi charging speed, when recent more expensive iPhones charge via MagSafe at 15W or even 25W. For me, it’s not the high charging speed I miss most; it’s the snapping into place.2 I think Apple knows the 16e’s intended audience better than I do. Daring Fireball readers aren’t in the 16e demographic; it’s the friends and family members of DF readers who are.
What features do typical low-end iPhone buyers care about? They want a phone that looks good, with a good display, a decent camera, and long battery life. Do they care that the 16e only supports Wi-Fi 6, not 7? No, because they have zero idea what Wi-Fi version numbers even mean. They just think Wi-Fi is Wi-Fi. Do they care about superspeed mmWave 5G networking from Verizon (a.k.a. “ultra wideband”)? No. They just want their cellular connection to be fast and strong. (My review unit from Apple came with a temporary eSIM on AT&T. Cellular connections were fast and strong all week. The only place where I noticed a weak signal was in a deeply suburban / borderline rural area while visiting family over the weekend; my wife’s iPhone 15 Pro Max lost its signal on Verizon at the same location. I have zero complaints about Apple’s C1 modem.)
The iPhone 16e also omits the other “ultra wideband”, the chip Apple uses for precise location detection — like tracking an AirPod to within a foot. Precision finding is super cool, and when you’re truly bedeviled by a lost item like a keychain, remarkably helpful. Ultra wideband has been included on all new iPhones other than the SE (and now 16e) since the iPhones 11 in 2019. From a nerd’s perspective, it really does seem like a curious omission from the 16e five years later. But how many people in your extended family know what “ultra wideband precision finding” is?
To date, only Apple’s iPhone Pro models have supported ProMotion — Apple’s marketing name for a display that features adaptive refresh rates that go up to 120 Hz and down to 1 Hz for the “Always On” display mode. Given that the regular iPhone 16 (and 16 Plus) don’t support ProMotion, there was zero chance the 16e would. There are mid-range Android phones with high-refresh-rate displays, but (a) I don’t think they’re better displays, all things considered, and (b) they’re mid-range Android phones. It’s like bragging about the refresh rate on the dashboard display in a Kia Sorento. The 16e display also sports a throwback notch in lieu of the fancier, more playful, and at times cleverly useful, dynamic island.
The iPhone 16e targets the “I only care about the basics” iPhone buyer: the screen looks good, the camera is good but simple, the battery lasts a long time (the difference should be quite striking for anyone upgrading from a four- or five-year-old iPhone), it runs all their existing apps, and it charges fast when plugged into a USB cable. Those are the basics, and the basics are all that casual users care about. That it’s lighter in weight and physically smaller thanks to its minimally protruding single camera lens is gravy.
The only aspect of the 16e garnering more discussion than its omission of MagSafe is its starting price of $600 for a 128 GB base model. “It should cost $100 less” say some people, who tend to be the same people who also strongly believe it should include MagSafe and a ProMotion display. Here’s Apple’s current iPhone lineup, plus the discontinued (but still available from some carriers) 3rd-generation SE:
iPhone | Chip | 64 GB | 128 GB | 256 GB | 512 GB | 1 TB |
---|---|---|---|---|---|---|
SE (3rd gen) | A15 | $430 | $480 | $580 | — | — |
16e | A18 | — | $600 | $700 | $900 | — |
15 | A16 | — | $700 | $800 | $1000 | — |
16 | A18 | — | $800 | $900 | $1100 | — |
16 Plus | A18 | — | $900 | $1000 | $1200 | — |
16 Pro | A18 Pro | — | $1000 | $1100 | $1300 | $1500 |
16 Pro Max | A18 Pro | — | — | $1200 | $1400 | $1600 |
That’s a tidy pricing matrix with $100 increments. The new 16e starting at $600 makes more sense than the old SE starting at just $430. $600 is clearly the next logical “rung” under the year-old iPhone 15’s $700 starting price. Complaining that Apple no longer makes a phone that’s priced in the $400-500 range is like complaining that BMW no longer makes any cars that cost less than $40,000. They’re Apple. It’s an iPhone. Of course it costs more than a no-name Android phone, or the 27th model down the ladder in Samsung’s sprawling product lineup. Anyone who wants to spend less than $600 for an iPhone can buy one from the flourishing pre-owned/refurbished market — just like buying a BMW for under $40,000.
The iPhone 16e is an iPhone for people who don’t want to think much about their phone. But they do want an iPhone, not just any “whatever” phone. A just plain iPhone, with a good screen, good enough (and simple) camera, and great battery life. I think Apple nailed that with the iPhone 16e. ★
There’s a decided feel difference with the side rails of the 16e too. The sides feel sharper, less rounded, than the regular 16 and 16 Pro (and the 15/15 Pro, and 14/14 Pro ...). That squareness (sharp-cornered-ness?) isn’t bad, per se, but it does subtly convey a sense of the 16e being a less premium device. ↩︎
One of the most surprising aspects of my professional life in recent years is how much time I spend thinking and writing about magnets. But the “snapping into place” thing does raise the question of why Apple didn’t include magnets in its cases for the 16e. ↩︎
Joseph Menn, reporting for The Washington Post:
The U.S. Justice Department told Congress in November there were no major disputes with the United Kingdom over how the two allies seek data from each other’s communication companies.
But at that time, officials knew British authorities were preparing a demand that Apple build a back door to its users’ encrypted data, according to people familiar with the process, who spoke on the condition of anonymity to discuss internal department matters. [...]
The department said it reminded its British counterpart of the CLOUD Act’s “requirement that the terms of the Agreement shall not create any obligation that providers be capable of decrypting data.” The report did not mention the looming order, and said any demands for reduced security would come under Britain’s Investigatory Powers Act, and so were not within the scope of the CLOUD Act.
On Wednesday, Sen. Alex Padilla and Rep. Zoe Lofgren, both California Democrats, faulted the November certification, saying “it splits the finest of hairs” by suggesting that the CLOUD Act didn’t apply to any decryption order. The two lawmakers, who sit on the Judiciary committees in their respective chambers of Congress, asked Bondi to reconsider whether Britain was violating the Cloud Act by ordering a break to Apple’s encryption.
Two of the people familiar with the certification process said the FBI has pursued backdoor capabilities unsuccessfully in the United States and would have been in a stronger legal position to win that if Apple had already had to create such a mechanism for another government.
Just utterly disgraceful behavior from the Biden administration — choosing to look the other way at a clear violation of the CLOUD Act to help their purported buddies in the UK, at the direct expense of a US company’s autonomy and US citizens’ privacy. I don’t see how this dissembling can be defended. Upon learning of the UK’s odious demands on Apple, the Biden administration’s response wasn’t to defend Apple (or Americans’ privacy), but instead to try to hide it from Congress. Unreal.
Zac Hall, reporting for 9to5Mac:
According to a letter seen by 9to5Mac, the Trump Administration is investigating whether the UK may have broken a bilateral agreement when secretly demanding that Apple build a global backdoor into iCloud.
Trump’s Director of National Intelligence Tulsi Gabbard wrote in a letter responding to Senator Ron Wyden of Oregon and Representative Andy Biggs of Arizona that she was not made aware of the UK’s secret demand by her UK counterparts. However, she suggested, the UK government may have broken a bilateral privacy and surveillance agreement in making the demand.
Gabbard’s letter is available here (and I’m hosting a copy). From her letter:
Thank you for your letter dated 13 February 2025 concerning reported actions by the United Kingdom toward Apple that could undermine Americans’ privacy and civil liberties at risk. I am aware of the press reporting that the UK Home Secretary served Apple with a secret order directing the company to create a “back door” capability in its iCloud encryption to facilitate UK government access to any Apple iCloud users’ uploaded data anywhere in the world. I share your grave concern about the serious implications of the United Kingdom, or any foreign country, requiring Apple or any company to create a “backdoor” that would allow access to Americans personal encrypted data. This would be a clear and egregious violation of Americans’ privacy and civil liberties, and open up a serious vulnerability for cyber exploitation by adversarial actors.
I was not made aware of this reported order, either by the United Kingdom government or Apple, prior to it being reported in the media. I have requested my counterparts at CIA, DIA, DHS, FBI and NSA to provide insights regarding the publicly reported actions, and will subsequently engage with UK government officials. The UK’s Investigatory Powers Act of 2016, also known as the Snoopers’ Charter, which I understand would be at issue, allows the UK to issue a “gag order,” which would prevent Apple or any company from voicing their concerns with myself, or the public. [...]
My lawyers are working to provide a legal opinion on the implications of the reported UK demands against Apple on the bilateral Cloud Act agreement. Upon initial review of the U.S. and U.K. bilateral CLOUD Act Agreement, the United Kingdom may not issue demands for data of U.S. citizens, nationals, or lawful permanent residents (“U.S. persons”), nor is it authorized to demand the data of persons located inside the United States. The same is true for the United States — it may not use the CLOUD Act agreement to demand data of any person located in the United Kingdom.
I’m so pleased by Gabbard’s response here, including making it public, that I’m gladly willing to overlook her “back door”/”backdoor” and “UK”/”U.K.” inconsistencies. (DF style is now to close it up: backdoor.)
Short of the UK backing down and retracting its secret demand for an iCloud backdoor from Apple, this is the best that Apple and privacy advocates could hope for. The gag-order aspect of the UK’s Investigatory Powers Act prevented Apple from even fighting it in court. But a US ruling that would hold it illegal for Apple to comply would put Apple in an impossible situation, where they can’t comply with a UK legal demand without violating the law of the home country. That would actually give Apple the ground to fight this in the UK.
It is not coincidental that UK Prime Minister Keir Starmer is set to visit the White House tomorrow. This is a message in advance that the US considers all aspects of this demand on Apple unacceptable.
I referenced Downie twice earlier today — once in my item linking to Charlie Monroe (developer of Downie) writing about the indie app business, and earlier in my post about using Downie to download the MP3 from Jony Ive’s interview on the BBC’s Desert Island Discs.
I somehow hadn’t heard of (or more likely, just hadn’t noticed) Downie until a few weeks ago, when I first came across Monroe’s blog post, via Michael Tsai. Here’s the pitch for Downie, from its website:
Ever wished you could save a video from the Internet? Search no more, Downie is what you’re looking for. Easily download videos from thousands of different sites.
That’s it. You give it a web page URL, and Downie will download any video (or audio) files embedded on the page. Downie offers all sorts of convenience features, like browser extensions, post-processing, and more. But the main interface is super obvious and easy.
For years, I’ve used the open source yt-dlp command-line tool for this task (and before yt-dlp, its predecessor, youtube-dl). When I saw Downie, I thought to myself, “That looks cool, but I don’t really download that many video or audio files to justify paying for a commercial app.” But then I slapped myself (figuratively) and I realized I should at least try it. I’m so glad I did. It’s like using Transmit instead of the command-line tools for secure FTP connections. It’s cool that the Mac has a Unix terminal interface and support for zillions of free and open source utilities, but the point of using a Mac is to use great Mac apps. And Downie is a great Mac app.
What I’ve found over the last month isn’t just that I enjoy using Downie far more than invoking yt-dlp, but that I use Downie more often than I used yt-dlp, because it’s so much easier and more reliable. For example, when I wrote about Fox Sports’s new scorebug that debuted in the Super Bowl, I used Downie to download local 4K copies of this month’s Super Bowl 59, along with Super Bowl 57 from two years ago, to compare Fox’s new scorebug with their previous one. Local video files are easy to navigate frame-by-frame to capture the perfect screenshot; YouTube’s website makes it impossible to navigate frame-by-frame.
Downie is a $20 one-time purchase (and is also included with a Setapp subscription). I’ve only been using it for a month or so, and I already feel like I’ve gotten $20 of utility from it. (I went ahead and bought Monroe’s other major app, Permute, too.)
Charlie Monroe, developer of excellent apps such as Downie and Permute:
But also don’t do this alone. I work 365 days a year. Last year, I worked 366 days (2024 was leap year). I’m not saying that I work 8 hours each day, but even during weekends, holidays, vacation, I need to tend to support emails in the morning for an hour or so and then once more in the afternoon or evening. I cannot just take off and leave for a few days without seeing the consequences and going insane when I get back. I currently receive about 100 reports from my apps each day. Some are about license code issues, some are crash reports, some are Permute conversion issues, some are Downie download issues, but it all adds up to the average of the 100 reports a day.
If I were to leave for a vacation for 10 days… You do the math what would I be getting back to. Plus your users don’t want to wait for 10 days. Even 5 days. There are users who are unwilling to wait an hour and just don’t realize that you cannot be at the computer 24-hours a day and that you’re perhaps in a different time zone and sleeping. The unfortunate thing about this is that going through the support emails in my case is something that takes about 2-3 hours a day — which is not enough to hire someone and train them. Not to mention that most of the reports actually need some technical knowledge. So unless I would hire another developer, in the end, the really administrative stuff that someone could do instead of me is a 30-minute-a-day job.
I wouldn’t recommend never taking a complete break for anyone, but there are some businesses where someone needs to spend an hour-plus on certain tasks each day. If you’re a one-person operation, that person is you, even while on vacation. No one gets into indie development because they look forward to doing support, either. It’s the designing, programming, crafting, and refining of the apps that drives them. But it’s like being a musician or comedian in some ways. For those endeavors, the grind is traveling from one city to another for gigs. Or like running a restaurant, as dramatized on The Bear — prep work, cleaning, procurement, reservations, food allergies, more cleaning. It never stops. For indie developers, the grind is support. (Small restaurants typically close for a day or two each week; technical support email addresses don’t.) There’s just always a lot of menial work involved with being a professional artist. But that’s also why so many indie developers — like, seemingly, Monroe — find the endeavor worthwhile. Because artistic work is deeply fulfilling.
A while back — around 20 years ago, at the height of the “Delicious” renaissance in indie development for Mac OS X — there was a developer who burst onto the scene with a deservedly very popular app. It was gorgeous and fast. It had a lot fewer features than other apps in its somewhat-crowded category, but that was also part of the app’s appeal. It was like a sporty little roadster in a category full of practical sedans and trucks. He eventually came out with a second app, and it too was popular. His apps were sort of like Panic’s, aesthetically, I’d say. They not only looked cool, they were well-designed from a usability perspective too. This developer, so I’ve been told, spent almost no time at all on tech support from customers. How was this possible, a friend of mine asked him. Easy, this developer said. When the inbox for support emails looked full, he’d do a Select All, then Delete. Inbox zero.
This story has always made me laugh. It’s hilarious, in a way. But ultimately it was a sign that he just wasn’t cut out for the indie app business. I don’t think it’s a coincidence that his apps went dormant around 2010, and I haven’t heard of him or from him in like 15 years. He was super talented so I wouldn’t be surprised if he’s doing great work in some other business, perhaps inside a much bigger company, where developers and designers are isolated from customers, rather than enmeshed with them like indies inherently are.
Alex Heath, writing for The Verge:
Just a few weeks after everyone freaked out about DeepSeek, Elon Musk’s Grok-3 has again shaken up the fast-moving AI race. The new model is ending the week at the top of the Chatbot Arena leaderboard, while the Grok iOS app is at the top of the App Store, just above ChatGPT. Even as Musk appears to be crashing out from his newfound political power, his xAI team has managed to deploy a leading foundational model in record time. [...]
While its Deep Research reports are nowhere near as in depth as OpenAI’s, Grok-3’s “thinking” capabilities appear to be roughly on par with o1, according to Andrej Karpathy, who noted in his deep dive comparison that “this timescale to state of the art territory is unprecedented.”
Benedict Evans, back in 2021, observed:
Elon Musk is a bullshitter who delivers. This breaks a lot of people’s pattern-matching, in both directions.
This summation of Musk is more apt, and more useful, today than it was four years ago. The Boring Company is seemingly a complete fraud, and he’s been making unfulfilled promises about Tesla “full self-driving” for over a decade. But Tesla Motors has done more to make electric cars mainstream than all other automakers combined. Starlink delivers extraordinary satellite Internet service, with no real competitors. SpaceX has rejuvenated the rocket industry. xAI seems to fall on the “actually delivers” side.
Twitter/X seems to fall squarely in the middle. It’s a mess in many ways, and seems not one iota closer to Musk’s promised vision of an “everything app”, but under Musk’s ownership it has been transformed, and while it isn’t more popular than it used to be, it also isn’t less (or much less) popular. It’s just a different somewhat scummier audience and vibe.
My betting money says the whole DOGE thing is very much on the bullshit side, but Musk’s overall track record spans the gamut from outright scams to extraordinary historic accomplishments. He’s such a prolific and shameless bullshitter that I wouldn’t take Musk at his word about anything, even what he had for lunch. But I’d be loath to bet against him on an engineering endeavor.
Chris Welch, writing at The Verge:
Apple has acknowledged a peculiar bug with the iPhone’s dictation feature that briefly displays “Trump” when someone says the word “racist.” The Verge has been unable to reproduce the issue, but it picked up attention on Tuesday after a video demonstrating the strange substitution went viral on TikTok and other social media.
The company provided a statement to The New York Times and Fox News confirming the bug. “We are aware of an issue with the speech recognition model that powers dictation, and we are rolling out a fix as soon as possible,” an unnamed spokesperson said, according to Fox News.
From the Times story:
The issue appeared to begin after an update to Apple’s servers, said John Burkey, the founder of Wonderrush.ai, an artificial intelligence start-up, and a former member of Apple’s Siri team who is still in regular contact with the team.
But he said that it was unlikely that the data that Apple has collected for its artificial intelligence offerings was causing the problem, and the word correcting itself was likely an indication that the issue was not just technical. Instead, he said, there was probably software code somewhere on Apple’s systems that caused iPhones to write the word “Trump” when someone said “racist.”
“This smells like a serious prank,” Mr. Burkey said. “The only question is: Did someone slip this into the data or slip into the code?”
Paul Kafasis (my guest on the latest episode of The Talk Show) captured a video of the glitch in action. I guess it could be a protest prank from a rogue employee, but I suspect it’s just a machine learning glitch — maybe caused by the fact that Trump’s name gets mentioned alongside “racist” so often? It’s definitely a little weird, but all sorts of things about Siri are a little weird.
Apple, in a very precisely worded statement issued to the media (including me) this morning:
Apple can no longer offer Advanced Data Protection (ADP) in the United Kingdom to new users and current UK users will eventually need to disable this security feature. ADP protects iCloud data with end-to-end encryption, which means the data can only be decrypted by the user who owns it, and only on their trusted devices. We are gravely disappointed that the protections provided by ADP will not be available to our customers in the UK given the continuing rise of data breaches and other threats to customer privacy. Enhancing the security of cloud storage with end-to-end encryption is more urgent than ever before. Apple remains committed to offering our users the highest level of security for their personal data and are hopeful that we will be able to do so in the future in the United Kingdom. As we have said many times before, we have never built a backdoor or master key to any of our products or services and we never will.
The context for this is the news that broke two weeks ago, by Joseph Menn in The Washington Post, and Tim Bradshaw in the Financial Times, that (quoting Menn’s report, emphasis added):
Security officials in the United Kingdom have demanded that Apple create a back door allowing them to retrieve all the content any Apple user worldwide has uploaded to the cloud, people familiar with the matter told The Washington Post. The British government’s undisclosed order, issued last month, requires blanket capability to view fully encrypted material, not merely assistance in cracking a specific account, and has no known precedent in major democracies. [...]
The office of the Home Secretary has served Apple with a document called a technical capability notice, ordering it to provide access under the sweeping U.K. Investigatory Powers Act of 2016, which authorizes law enforcement to compel assistance from companies when needed to collect evidence, the people said. The law, known by critics as the Snoopers’ Charter, makes it a criminal offense to reveal that the government has even made such a demand. An Apple spokesman declined to comment.
By definition, end-to-end encryption can have no secret backdoor, so compliance with this order from the UK would, in broad strokes, require Apple to abandon end-to-end encryption — not just for users in the UK but all users in all countries globally.1 More insidiously and outrageously, they are apparently forbidden by UK law, under severe penalty (imprisonment), from even informing the public about this demand, or, if they were to comply, from telling the public what they’ve done. The UK expects Apple to give them secret access to all iCloud data without Apple telling anyone — including, I believe, even the US government — that they’ve granted the UK government this breathtaking access.
Rather than comply, Apple is choosing instead to pull Advanced Data Protection from the UK. For UK users not already using ADP, the ability to enable it was already turned off before Apple’s statement was sent. This report from BBC News has a screenshot of what UK users see if they attempt to enable it today.
Re-read Apple’s statement above, which I’ve quoted in full, including the hyperlink. What stands out is that Apple is offering no explanation, not even a hint, why the company “can no longer offer Advanced Data Protection (ADP) in the United Kingdom to new users and current UK users will eventually need to disable this security feature”. On issues pertaining to security and privacy, Apple always explains its policies and features as best it can. The fact that Apple has offered no hint as to why they’re doing this is a canary statement of sorts: they’re making clear as best they can that they’re under a legal gag order that prevents them from even acknowledging that they’re under a legal gag order, by not telling us why they’re no longer able to offer ADP in the UK. This sort of read-between-the-lines implicit confirmation that they’re under a gag order is the only sort of confirmation they can legally offer, at risk of imprisonment.
Enabling ADP is controlled server-side, so Apple was able to disable the ability for UK users to turn on ADP without requiring a software update to devices. But it’s an open question how this will play out for users in the UK who already have ADP enabled. Apple cannot disable ADP remotely. With a moment’s thought, you can realize why they can’t: it would defeat the entire purpose. In the same way that Apple can’t hold its own key to decrypt a user’s data with ADP, they also can’t hold the ability to disable ADP.
Enabling ADP is reversible, however. After turning it on, a user can revert to standard protection, turning it off. But they must manually confirm it. I suspect what Apple is going to do for UK users with ADP already enabled is begin issuing warnings, instructing them to disable it manually, before some deadline. Once that deadline passes, I think Apple will have to stop allowing iCloud access to ADP-protected accounts in the UK. That won’t leave the data of those users unprotected — they simply will lose access to sync until they disable ADP and revert to standard protection.
The bottom line is that the UK government is proceeding like a tyrannical authoritarian state. That’s not hyperbole. And the breathtaking scope of their order — being able to secretly snoop, without notice that they even have the capability, not only on their own citizens but every Apple user in the entire world — suggests a delusional belief that the British Empire still stands. It’s simultaneously infuriatingly offensive, mathematically ignorant (regarding the nature of end-to-end encryption), dangerous (as proven by the recent Salt Typhoon attack China successfully waged to eavesdrop on non-E2EE communications in the United States), and laughably naive regarding the UK’s actual power and standing in the world.
Apple is, rightly and righteously, telling them to fuck off. ★
If you use Advanced Data Protection, your iCloud data can only be decrypted (a) by your own devices, (b) using the recovery key that you control from when you enabled ADP, or (c) by any recovery contacts you’ve created in iCloud. Apple insists that you must generate a recovery key or specify at least one recovery contact to enable ADP. Lose your devices, lose your recovery key, and lose your iCloud passphrase, and no one, including Apple, can recover your iCloud data. That level of cryptographically guaranteed security is the benefit of ADP. It’s also the risk of ADP. And there’s a convenience cost. For example, web access to iCloud. Quoting from Apple’s own ADP documentation:
When a user first turns on Advanced Data Protection, web access to their data at iCloud.com is automatically turned off. This is because iCloud web servers no longer have access to the keys required to decrypt and display the user’s data. The user can choose to turn on web access again, and use the participation of their trusted device to access their encrypted iCloud data on the web.
After turning on web access, the user must authorize the web sign-in on one of their trusted devices each time they visit iCloud.com. The authorization “arms” the device for web access. For the next hour, this device accepts requests from specific Apple servers to upload individual service keys, but only those corresponding to an allow list of services normally accessible on iCloud.com. In other words, even after the user authorizes a web sign-in, a server request is unable to induce the user’s device to upload service keys for data that isn’t intended to be viewed on iCloud.com, (such as Health data or passwords in iCloud Keychain). Apple servers request only the service keys needed to decrypt the specific data that the user is requesting to access on the web. Every time a service key is uploaded, it is encrypted using an ephemeral key bound to the web session that the user authorized, and a notification is displayed on the user’s device, showing the iCloud service whose data is temporarily being made available to Apple servers.
It’s for reasons like “I lost my only device and forgot my iCloud password”, and to provide easy access to iCloud through the web, that Advanced Data Protection is not the default for all users.
I think it’s technically possible that Apple could maintain “end-to-end encryption” in a pedantic sense while adding an additional UK-controlled signing key to all encrypted data in iCloud. Let’s say you own two Apple devices, an iPhone and a Mac, and you use Advanced Data Protection. Your data can only be decrypted by those two devices, or by your recovery key, or by a device controlled by one of your recovery contacts. Apple could do something like add the UK government as, effectively, a recovery contact, to each and every user in the world’s encrypted iCloud data. That would still be “end-to-end”, it’s just that the UK government would control one of those end points. But the way iCloud security is designed, something like that cannot be added silently. When a new device is added to your iCloud account, all of your existing devices get a notification that a new device has been added. I personally see these notifications hundreds of times a year, every year, as I add new review unit devices to my account. Like back in September, I got four iPhone 16 review units, two Apple Watch review units, and purchased my own iPhone 16 Pro. And I own several Macs, several Apple Watches, and an iPad. Each one of those devices, when added to my iCloud account, even just temporarily for testing, generated a notification about the new device being added to my iCloud account to each and every one of my other devices, new or old, currently signed into my iCloud account. That’s a minor annoyance for me as a product reviewer, but of course I wouldn’t have it any other way. Apple’s system is built such that new devices cannot be added to the chain without a notification being generated and sent to every existing device in your account. This notification regarding new devices happens even with standard protection — it’s not exclusive to users who’ve enabled ADP.
So while in theory some company could (I think?) build a system that is fairly (but deceptively) described as “end-to-end encrypted” where one of the “ends” is secretly and silently controlled by the UK government, Apple’s iCloud is not such a system. Apple is prevented by UK law from explaining this, unfortunately, but I think it’s true that as iCloud currently stands, Apple cannot comply with the UK’s demands for ADP-protected accounts, because they can’t add a UK-controlled decryption key to existing iCloud accounts without notifying every device signed into every account. ↩︎