Apple has released its regular weekly update to XProtect for all versions of macOS, bringing it to version 5346. As usual it doesn’t release information about what security issues this update might address.

This version removes 11 Yara rules for MACOS.f3edc61, MACOS.d1e06b8, OSX.Bundlore.D, OSX.OpinionSpy, OSX.DevilRobber.A, OSX.DevilRobber.B, OSX.Mdropper.i, OSX.FkCodec.i, MACOS.d4735e3, MACOS.HONKBOX.B, and MACOS.FLUFFYFERRET.CT, and many of the component rules for MACOS.ADLOAD. There are no changes in the Osascript rules in XPScripts.yr.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5346

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5346 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has released its regular weekly update to XProtect for all versions of macOS, bringing it to version 5345. As usual it doesn’t release information about what security issues this update might address.

This version adds one new Yara rule for MACOS.SILLYSTRAW.IMA, which appears to be a new genus, and in the Osascript rules in XPScripts.yr it adds a new rule for MACOS.OSASCRIPT.TADE and amends the existing rule for MACOS.OSASCRIPT.SYPR.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5345

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5345 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

How would you cope if you started your Mac up to find every datestamp on every file had been set to 1 January 1970 at 00:00? Or that every Finder Tag had vanished? What if all the Exif information for your images had been wiped out? Metadata like those aren’t optional extras we can afford to lose, although other metadata, like Finder Info and the URL from which a file was downloaded, are more ephemeral.

Xattr flags

Back in 2013, when iCloud was just two years old, Apple’s engineers implemented a scheme to determine how metadata stored as extended attributes (xattrs) should be copied, to take into account its permanence. This was important at that time to ensure only the right xattrs were preserved when files were stored in iCloud Drive. They did this by adding flags to the xattr’s name to indicate which actions should result in preservation of that type of xattr, and the metadata it contains.

Apple provides an extensive suite of xattr types to store metadata such as author names, keywords and comments, whose names all start with com.apple.metadata:. These are matched by corresponding metadata attribute keys, for example the xattr com.apple.metadata:kMDItemKeywords bears the metadata content accessed by the key kMDItemKeywords. Rather than appending flags to them all, this scheme laid down a table of default flags to be applied.

Being exemplary engineers, this was all detailed in the source code for copyfile, which is also open source. However, as this was just after Apple stopped creating much of its technical documentation, and little has ever been published about iCloud Drive, that’s as far as that information went.

For iCloud Drive, the relevant flag is S, XATTR_FLAG_SYNCABLE, defined as “This indicates that the extended attribute should be copied when the file is synced on services like iCloud Drive. Sync services may enforce additional restrictions on the acceptable size and number of extended attributes.”

Default flags set for xattr types com.apple.metadata:* (except for five of the less used types) are PS to preserve them during copy, save, sync and backup. You can read the macOS 26 version of those source files in Apple’s Open Source GitHub.

FileProvider

For the next decade or so, iCloud Drive mostly respected those behaviours, although without documentation it all appeared puzzling until you read the copyfile source. Then Apple decided to modernise it by implementing its FileProvider framework, a major architectural change for the better. Although the framework is intended to be common to all cloud storage services, there remains ample scope for iCloud Drive to offer enhancements.

Current FileProvider documentation for developers states:
“The extended file attributes are part of the item’s metadata. The system sets extended attributes on dataless files, and preserves them on files that it renders dataless. The system decides which attributes to sync. To sync an attribute, it calls the xattr_name_with_flags(_:_:) method and passes the XATTR_FLAG_SYNCABLE flag. Some older attributes are also synced.”

While FileProvider appears intended to conform to the xattr flag scheme, there’s no mention of the tables of default flags listed in the copyfile source code.

Implementation

Last week I set out to test and document how well iCloud Drive manages metadata, following the xattr flag system and copying up all those invaluable com.apple.metadata:* xattrs, only to discover it doesn’t any more. Of Apple’s many standard xattrs, the only ones I found that synced reliably over iCloud Drive in macOS 26.4.1 were:

• com.apple.metadata:_kMDItemUserTags (Finder Tag)
• com.apple.lastuseddate#PS
• com.apple.quarantine
• com.apple.TextEncoding

The good news is that iCloud Drive through FileProvider does respect the S flag, but only where it’s explicit, rather than being set in that table of defaults. For those of us who have our own xattr types, such as those used for integrity checking by Dintch, Fintch and cintch, can still rely on iCloud Drive to sync those, provided they bear that S flag.

The bad news is that none of the most popular metadata-bearing xattrs are synced, apart from Finder Tags. All those com.apple.metadata:kMDItem* xattrs are blocked, as FileProvider doesn’t recognise them as having their default PS flags.

Workarounds

I have since looked at two workarounds, explicitly adding the S flag to those types that should be accorded it by default, and changing the xattr names from com.apple.metadata:kMDItem* to com.apple.metadata:_kMDItem*.

Adding xattrs like com.apple.metadata:kMDItemKeywords#S with an explicit S flag does ensure FileProvider syncs those xattrs. However, as neither Spotlight indexing nor the Finder appear to understand that flag isn’t really part of the type name, those preserved xattrs are of no use: they aren’t recognised by Spotlight for indexing, nor are they displayed in the Finder’s Get Info dialog or Preview pane.

Inserting an underscore into the xattr’s name was even worse, as it didn’t lead to their preservation, and was ignored by Spotlight indexing and the Finder.

This raises another interesting issue, in that there doesn’t appear to be a way to extend Spotlight indexing to encompass additional xattr types. There are extensive third-party type libraries, such as org.openmetainfo:* from Tom Andersen of Ironic Software and OpenMeta. But those appear to require their own indexing, search and presentation support.

Error

When I first realised the impact on metadata in iCloud Drive, I assumed this arose because the engineers implementing FileProvider, or those porting iCloud Drive to use that framework, had’t been aware of the xattr flag system and its primary purpose. But if that had been true, they couldn’t have respected explicit use of the S flag. Thus, I’m left with two plausible explanations:

• Apple’s FileProvider/iCloud Drive engineers are unaware of the system defaults table in copyfile, so assumed that com.apple.metadata:* xattrs weren’t intended to be preserved when syncing.
• Apple decided to end default sync support for com.apple.metadata:* xattrs in iCloud Drive.

The second of those is even more erroneous than the first, as it reduces iCloud Drive support for metadata to a level common with third-party cloud providers. In this respect, users will see no difference from the behaviour of Dropbox or Microsoft OneDrive, which isn’t the marketing choice I’d have expected from Apple.

Conclusion

iCloud Drive no longer syncs much metadata stored in xattrs, in particular that stored in com.apple.metadata:* xattrs, apart from Finder Tags. There is no workaround, and unless Apple restores that feature, it limits the use of iCloud Drive with Macs.

Apple has released an update to XProtect for all versions of macOS, bringing it to version 5344. Version 5343 doesn’t appear to have been released. As usual it doesn’t release information about what security issues this update might address.

This version makes minor amendments to the Yara rules for MACOS.SHEEPSWAP.OBF.C, MACOS.SHEEPSWAP.OBFE.COMMON and MACOS.ADLOAD. There has been no change in the Osascript rules in XPScripts.yr.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5344

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5344 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

The update bringing macOS Tahoe to version 26.5 is modest in size and, apart from its security fixes, seems largely routine maintenance.

The only release notes worth reading are those listing vulnerabilities fixed, available here. Among the 69 listed there are 9 in the kernel, which must be the highest number in any recent macOS update. I wonder whether those have been swelled by AI, and one of the kernel bugs is credited to a researcher “with Claude and Anthropic Research”. There could of course be fixes resulting from early use of Mythos, but they’re unlikely to appear in a public list. None of the fixes listed are reported as being known to exist in the wild.

The new build number for 26.5 is 25F71. Apple silicon Macs have a firmware update bringing them to mBoot 18000.120.36, and Intel Macs with T2 chips are updated to 2103.100.6.0.0 (iBridge 23.16.15067.0.0,0).

Bundled apps have routine increments in version numbers:

• Books, from version 8.4 to 8.5
• Freeform, 4.4 to 4.5
• Music, 1.6.4 to 1.6.5
• News, 11.4 to 11.5
• Passwords, 2.4 to 2.5
• Safari, 26.4 (21624.1.16.11.4) to 26.5 (21624.2.5.11.4)
• Stocks, 8.4 to 8.5
• TV, 1.6.4 to 1.6.5.

Although there are abundant increments in build numbers reflecting routine maintenance, there are few substantial changes apparent in /System/Library, including:

• In kernel extensions, the whole AGX series has a substantial change in version, as does AppleUSBAudio, and smbfs is updated to version 6.0.1
• APFS is incremented to version 2811.120.14
• There’s a new AppleAccountTransparency in private frameworks.

Apple has released the update to bring macOS Tahoe to version 26.5, and security updates for Sequoia and Sonoma to bring them to 15.7.7 and 14.8.7.

If you were expecting 15.7.6 or 14.8.6, then you’ll be as surprised as I was that Apple appears to have skipped those and gone straight on to x.x.7. I haven’t seen any explanation for this curious change in version numbering.

Download size for the 26.5 update on an Apple silicon Mac is around 3.8 GB, and the last 5 minutes of preparation takes maybe a tad longer than that. Intel Macs should download around 2.9 GB instead.

In Apple silicon Macs, firmware is updated to mBoot 18000.120.36, while Intel firmware is updated to 2103.100.6.0.0 (iBridge 23.16.15067.0.0,0).

Release notes are the bland and unhelpful statement that “This update includes enhancements, bug fixes, and security updates for your Mac.”

Security release notes are here for Tahoe with around 69 vulnerabilities fixed including more kernel bugs than I’ve ever seen in a single update, here for Sequoia with around 45, and here for Sonoma with a mere 43 or so.

Apple still hasn’t posted any enterprise release notes here but might think of something to report later.

Updated 20:00 GMT 11 May 2026 with firmware info.

距离苹果全球开发者大会 WWDC 还有一个月不到的时间，彭博社又送上关于苹果新系统的全新爆料：

苹果准备对 macOS 27 的界面进行一轮小幅调整，进一步完善「液态玻璃」设计语言的视觉表现。

但问题在于，对于如今的 Mac 来说，除了需要继续打磨的 UI，最迫切的更新显然远不止于此。

液态玻璃，缝缝补补又一年

对比 iPhone 以及 iPad，Mac 的性能和续航都更有盈余，实际上 macOS 26 的界面，视觉效果要更接近去年 WWDC 上面演示的「满血版」液态玻璃。

不过，液态玻璃立项之初，就是专门为 OLED 屏幕设计的，而目前所有 Mac 产品都在使用 LCD 屏幕，在呈现半透明、阴影和玻璃质感的方面，效果不如 OLED。

于是 macOS 26 的一些高透明效果和阴影，会导致列表和文字可读性下降——这也是「液态玻璃」被一直诟病的问题。

和 iOS 27 一样，macOS 27 也将仔细打磨液态玻璃，让它更接近苹果一开始设想的效果：兼顾透明度和可读性，同时进一步优化能耗表现。

不过，macOS 26 在 UI 上的问题根本不止于液态玻璃本身，不对齐的圆角、大量分散注意力的小图标，以及重新设计后辨识度大打折扣的应用图标，对可读性和美观层面都造成了一定的影响。

苹果评论员 John Gruber 对于 macOS 液态玻璃的点评相当一针见血：作为一种「内容优先」的设计语言，液态玻璃让系统 UI 隐身于媒体之后，在 iPhone 上或许能行，但作为强调生产力而非内容消费的桌面平台，Mac 包含大量的窗口、组间，因此复杂性更高，仍然需要应用界面保证清晰的结构、分明的功能区域，和强辨识度的界面。

在 Stephen Lemay 接任设计总监一职后，这位在苹果服务近 30 年的老将表现让人期待——Lemay 以公司内部的高口碑和稳定发挥著称，或许也称得上是苹果内部目前最懂苹果系统界面的人。

在他的把控下，macOS 27，以及 iOS 27 如何扭转液态玻璃褒贬不一的口碑，回到实用性和美感并举的方向，确实值得期待。

但对于 macOS 来说，界面上的「拨乱反正」固然必要，却已经不是最重要的更新了。

对苹果而言，未来系统的更新有两条主线：一方面，优化系统稳定性，另一方面，则是为 Apple 智能预备好。

最好的 AI 载体，需要一个 AIOS

根据彭博社爆料，苹果打算为「Apple 智能」打造一个「Extensions」功能，允许用户更换第三方 AI 模型，例如 Google Gemini、Claude 等等。

Siri 除了会集成到邮件、短信、相册等应用，自己也会化身聊天机器人，成为一个单独的应用。更多 AI 功能还会覆盖文本、图像等生成与编辑任务。

但这些更新，说实话更多还是做 AI 的单点功能，并非系统级别的编排能力，并未能进一步发挥 Mac 硬件上的优势。

今年年初的龙虾热，让 Mac mini 这个前年才火过的产品，又再一次出圈，这次火到苹果自己也没库存了，「入门版」在官网彻底售罄。

Mac 和 Windows 在不少层面上互有胜负，但在 AI 的问题上，Mac 作为「最佳 AI 容器」的论断几乎毫无争议。

关于这个问题，爱范儿已经出过一篇文章详细讨论。简单来说，就是因为 Mac 不管是 UNIX 系统底层还是集成运存的硬件架构，都非常契合 AI Agent 和大模型的运行方式，并且由于 ARM 架构的特性，运行功耗低还静音，非常适合 AI 常驻。

这更像是「无心插柳柳成荫」，苹果其实一开始并没有围绕 AI 去打造自己的 Mac，却无意间完成了所有 AI 的技术储备，严格意义上说是一种「适配度优势」。

从这个角度看，macOS 即使什么都不做，本身 Mac 也已经是一个很好的 AI 平台。苹果完全可以走 App Store 的逻辑，让用户自己部署想要的第三方 AI 智能体，自己继续扮演「收过路费」的角色。

这确实也是苹果长期以来的做法：在移动互联网兴起之时，苹果没必要自己做搜索引擎和网购平台。而 AI 时代，大众的需求变化万千，有人需要一个能剪辑的 Agent，也有人需要一个搞科研的 AI，必须要靠第三方满足。

在今年 5 月的财报会议上，苹果特别提到了 AI 公司 Perplexity 的智能体产品 Personal Computer，认为这种产品很好利用了 Mac 平台的能力。

既然觉得人家做得不错，何不自己上手做一个「iClaw」？

第三方 AI 百花齐放固然很好，这和苹果自己做一个却并不冲突，并且很多事情，只有第一方能做得好，能做得让人放心。

第三方应用再强，也很难自然获得系统级的上下文，苹果不可能将最底层的权限开放，只有系统底层自己能对文件位置、窗口状态、本地个人数据知道一清二楚，而 AI 应用的体验，往往就卡在了这些权限边界之上。

其实苹果并不是没有这种想法，那个迟迟没能推出的 AI Siri，其实就有着类似的构想，可以读取用户的文本和应用窗口，可以跨应用进行检索和处理。

对比 iPhone 和智能手机，AI 应用的主流使用场景其实还是在于桌面端，这也是为什么 Mac 能成为今年最热门的 AI 硬件，但苹果却没有继续在 macOS 的系统层面，赋予 Mac 足够分量的原生 AI 能力。

隔壁的 Windows 阵营在这方面要激进不少，系统层面有「Recall」和 「Copilot」这样的 AI 功能入口，联想和荣耀这样的 OEM 厂商，甚至为产品准备了开箱即用的龙虾应用，砍掉了门槛，并因为和本地深度集成，能节省不少 Token。

微软自己也已经坐不住了，据悉正在将原本只能你问我答的 Copilot，改造成一个 24/7 在线的数字分身，实现类龙虾能力。

对比 OpenAI、Anthropic 或者 Google，说实话我更愿意将这些敏感的数据，交给在隐私保护方面更上心的苹果。

更深一步，macOS 最缺少的不是 AI 应用，而是 AI 时代的「基建」。Mac 已经准备好了 AI 大有可为的土壤，但 macOS 还没能成为一个真正意义上的「AI 系统」。

苹果不仅可以做自己的 AI 智能体能力，也需要把模型、权限、上下文、自动化和跨应用任务重新梳理，让系统成为 AI 工作流的原生中介，成为一个掌控所有 AI 的「任务集散中心」。

就像是智能体运行所需要的「个人知识库」，现在我们用文件夹也可以搭建，但它还不够好用。

苹果完全可以自己承接这个环节，用户靠 Mac 自带的工具搭建、生成一个「知识库」文件，它可以和 Apple ID 绑定，利用 iCloud 流转，这样不管用哪一家的智能体服务，都能快速调用自己的知识库，不用从头开始配置，同时还能保证自己的内容被苹果的隐私政策保护。

并且，这些配置的模块都能整合进入 Apple 的订阅系统之中，iClaw 和 Token 也能成为苹果在 AI 时代提供的增值服务。

实际上，苹果已经开始了这样的进程。在 macOS 26.1 中，苹果集成了「模型上下文协议」，一个面向不同 AI 的通用开放标准，Agent 可以通过这个协议，访问用户的个人数据；苹果的基础模型框架，让 macOS 开发者可以调用系统内置的基础模型，零网络延迟，零 API 费用，数据不离开设备。

作为计算机图形系统的祖师爷，macOS 在过去的数十年间都是围绕「应用」构建的桌面系统。

在接下来十年，应用和图形界面还会是人机交互的主流，因此 macOS 27 要将界面风格修缮得更好，当然非常重要。

但未来五十年甚至更远，AI 都会成为无可避免的主旋律，macOS 不可避免会被进一步改造，成为一个围绕「任务」运转的 AIOS。

#欢迎关注爱范儿官方微信公众号：爱范儿（微信号：ifanr），更多精彩内容第一时间为您奉上。

Apple has released an update to XProtect for all versions of macOS, bringing it to version 5342. As usual it doesn’t release information about what security issues this update might address.

This version doesn’t appear to bring any additions or amendments to either the main Yara rules, or for Osascript rules in XPScripts.yr, but there has been extensive reformatting, tidying, and relabeling of lists.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5342

Sequoia and Tahoe systems only

This update has now been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5342 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has released an update to XProtect for all versions of macOS, bringing it to version 5341; the previous public release was 5338. As usual it doesn’t release information about what security issues this update might address.

This version amends the Yara rule for MACOS.PIRRIT.TWEN, and adds new rules for MACOS.AIRPIPE.IM, MACOS.EIGER.SUNOTO, MACOS.EIGER.BA and MACOS.MONCH.BA. Osascript rules in XPScripts.yr have amendments to those for MACOS.OSASCRIPT.BOZO, MACOS.OSASCRIPT.BOWISP and MACOS.OSASCRIPT.GEPEPA, and new rules added for MACOS.OSASCRIPT.DUCACI, MACOS.OSASCRIPT.DUCOOB and MACOS.OSASCRIPT.AMSCLUCL.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5341

Sequoia and Tahoe systems only

This update has now been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5341 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Overnight, Apple has released its regular weekly update to XProtect, bringing it to version 5338. As usual it doesn’t release information about what security issues this update might address.

This version adds four new Yara rules for MACOS.BONZAIBREEZE, MACOS.BONZAIBUFFOON, MACOS.BONZAIBOOMER and BONZAIBUNNY, additions to the Bonzai family of what appear to be clickfix stealers. To accompany those are four new entries in the Osascript rules in XPScripts.yr, for MACOS.OSASCRIPT.BOPADO, MACOS.OSASCRIPT.BOSTA, MACOS.OSASCRIPT.BOMSPAA and MACOS.OSASCRIPT.BOMSPAB.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5338

Sequoia and Tahoe systems only

This update has now (as of 1700 GMT 10 April) been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5338 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has just released an update to macOS Tahoe, bringing it to version 26.4.1.

Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.” Otherwise, this update has no published CVE entries, and no general user release notes.

The download is about 2.13 GB for Apple silicon Macs.

The build number is 25E253, just 7 builds since 26.4, and there don’t appear to be any firmware updates.

There are no changes in bundled app version or build numbers, even in Safari, and the only change in /System/Library is in the Private Framework for Icon Services in SwiftUI. I suspect that the bug fixed is in one or more binaries elsewhere in the SSV. However, this may fix more than that single bug, as iOS and iPadOS 26 also had a patch update yesterday for unidentified “bug fixes”.

Last updated 1850 GMT 9 April 2026.

Apple has overnight released its out-of-cycle update to XProtect for macOS prior to Sequoia, bringing it to version 5337. This update has already been released for macOS Sequoia and Tahoe, and this update provides the same version for those Macs still using on the older bundle location.

This version removes the Yara rule for MACOS.SOMA.MAENB, and makes no changes to the Osascript rules in XPScripts.yr.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5337

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5337 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has just released an out-of-cycle update to XProtect for macOS Sequoia and Tahoe only, bringing it to version 5337. As usual it doesn’t release information about what security issues this update might address.

This version removes the Yara rule for MACOS.SOMA.MAENB, and makes no changes to the Osascript rules in XPScripts.yr.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page.

Currently this update is only available for Macs running Sequoia or Tahoe. Those running earlier versions of macOS can only update to XProtect version 5336 via softwareupdate.

This update has only been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5337 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

前段时间，一款改装的「透明版 iPhone Air」在网上引起了热议 。

但是，直接剥离背板油漆露出内部精密零件，真的是一种很酷的极客审美，还是对工业设计的一种糟糕误解 ？本期节目，我们将穿过这场透明风波，去扒一扒 iPhone Air 玻璃背板下真正隐藏的极端工程追求 。同时，我们也将借此一窥，在 AI 开始接管物理世界的今天，科技巨头们到底在暗中筹划着一个怎样的未来 ？

在 YouTube 观看视频：https://youtu.be/tIDCztqm9I8

在 Bilibili 观看视频：https://suithink.me/2026/04/01/16ylog/

本期主要议题

把精密零件裸露出来就是很酷的设计感吗 ？我们将重新审视历史上经典透明设计的真正语境，聊聊为什么「透明版 iPhone Air」本质上可能是一场审美误会 。

iPhone Air 让人惊叹的纤薄，并不仅仅是视觉和比例上的魔法，更源于对核心元器件集成度边界的疯狂压榨 。苹果全新的“高原”设计语言和 Apple Watch 有什么关联 ？

标准版 iPhone 面向当下，而 Air 却是一个指向未来的坐标 。当计算核心不再被强制绑定在一块大屏幕之下，我们身边的电子设备生态将迎来怎样的一场无声大洗牌 ？

AI 的颠覆绝不止于聊天、写代码或生成图片，它正在悄悄渗透进物理世界的技术栈里 。结合苹果近期低调收购的 AI 初创公司，以及 Air 机身上隐藏的全球最大消费级 3D 打印零件，AI 驱动的逆向工程将如何改变我们习以为常的几何美学 ？

作为极具前瞻性的工程探索，iPhone Air 遭遇了商业上的滑铁卢 。既然时机并未成熟，消费者也倾向于“既要又要”，为什么 Apple 仍然愿意掏出这笔极其昂贵的「学费」 ？

本期关联播客

https://suithink.me/2026/04/01/16ylog/

补充一个AI逆向设计的工程案例：

https://weibo.com/1401527553/5282872370135897

节目简介

欢迎收听这期节目！前段时间，一款改装的「透明版 iPhone Air」在网上引起了热议 。但是，直接剥离背板油漆露出内部精密零件，真的是一种很酷的极客审美，还是对工业设计的一种糟糕误解 ？本期节目，我们将穿过这场透明风波，去扒一扒 iPhone Air 玻璃背板下真正隐藏的极端工程追求 。同时，我们也将借此一窥，在 AI 开始接管物理世界的今天，科技巨头们到底在暗中筹划着一个怎样的未来 ？

Show Notes

把精密零件裸露出来就是很酷的设计感吗 ？我们将重新审视历史上经典透明设计的真正语境，聊聊为什么「透明版 iPhone Air」本质上可能是一场审美误会 。

iPhone Air 让人惊叹的纤薄，并不仅仅是视觉和比例上的魔法，更源于对核心元器件集成度边界的疯狂压榨 。苹果全新的“高原”设计语言和 Apple Watch 有什么关联 ？

标准版 iPhone 面向当下，而 Air 却是一个指向未来的坐标 。当计算核心不再被强制绑定在一块大屏幕之下，我们身边的电子设备生态将迎来怎样的一场无声大洗牌 ？

AI 的颠覆绝不止于聊天、写代码或生成图片，它正在悄悄渗透进物理世界的技术栈里 。结合苹果近期低调收购的 AI 初创公司，以及 Air 机身上隐藏的全球最大消费级 3D 打印零件，AI 驱动的逆向工程将如何改变我们习以为常的几何美学 ？

作为极具前瞻性的工程探索，iPhone Air 遭遇了商业上的滑铁卢 。既然时机并未成熟，消费者也倾向于“既要又要”，为什么 Apple 仍然愿意掏出这笔极其昂贵的「学费」 ？

本期互动问题：

如果未来的计算设备真的变成了一张看不见、摸不着的分布式网络，手机这个实体彻底消失，你觉得人类最难克服的「物理习惯」会是什么呢？欢迎在评论区留言，跟我们一起大开脑洞！

本期关联视频

https://www.bilibili.com/video/BV1Qw9jBeESW/

｜相关链接｜

若你所使用的播客客户端未能完整显示插图，或遇网络问题未能正常播放，请访问：

荒野楼阁 WildloG 的地址：https://suithink.me/zlink/podcast/

阅读设计相关的各类文章：https://suithink.me/zlink/idea/

｜其他社交网络媒体｜

苏志斌 @ 知乎｜SUiTHiNK @ 即刻 / 微博

苏志斌SUiTHiNK @ Bilibili / YouTube / 小红书

｜联络邮箱｜

suithink.su@gmail.com

欢迎在 小宇宙、Spotify、YouTube、Apple Podcast 收听本节目，期待你的留言。

💾

Apple has just released its regular weekly update to XProtect, bringing it to version 5336. As usual it doesn’t release information about what security issues this update might address.

This version adds two new rules for MACOS.WANNABEWALLABY.IMA and MACOS.WANNABEWALLABY.STA, amends rules for MACOS.TIMELYTURTLE.DYHEOC, MACOS.SOMA.MAENA, and MACOS.SOMA.MAENB, and changes some rule UUIDs. In the Osascript rules in XPScripts.yr, it amends the rule for MACOS.OSASCRIPT.SYPR.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5336

Sequoia and Tahoe systems only

This update hasn’t yet been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5336 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has just released its regular weekly update to XProtect, bringing it to version 5335. As usual it doesn’t release information about what security issues this update might address.

This version adds two new Yara rules for MACOS.TIMELYTURTLE.OBDR and MACOS.SOMA.MAENB, and amends the existing rule for MACOS.SOMA.BYTE.SEQUENCE.B. In the Osascript rules in XPScripts.yr, it relocates those for TABUPA, REBUPA, DUVAST, DUCUHA and DUSTCO.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5335

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5335 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

The update to bring macOS Tahoe up to version 26.4 is hefty at around 7.15 GB (more than double that if you’re unlucky), and reflects a great deal of bug fixes and improvements in almost every subsystem. Apple provides three good sets of release notes:

• General release notes include the addition of an option to use compact tabs in Safari, Freeform’s new Creator Studio enhancements, and a facility for Purchase Sharing in Family Sharing. Oh, and the requisite eight new emoji.
• Enterprise release notes are extensive, but contain little for the non-enterprise user.
• Security release notes list over 70 fixes, many of which are significant, but none are reported as being known to be exploited in the wild at present.

The new build number of 26.4 is 25E246. The Darwin Kernel version is 25.4.0, and XNU 12377.101.15~1.

Apple silicon firmware is updated to a completely different version numbering system, and is now reported as mBoot version 18000.101.7. If you’re running SilentKnight older than version 2.14 (71), then it’s likely that it will crash as a result of this change in firmware version. Please use version 2.14 from here.

Firmware in Intel Macs with T2 chips remains with the previous system, and is updated from 2094.80.5.0.0 (iBridge 23.16.13120.0.0,0) to 2103.100.6.0.0 (iBridge 23.16.14242.0.0,0).

Looking through the bundled apps and /System/Library, there are a great many increments in build numbers reflecting the extensive changes made. Here are a few of the more substantial changes found.

In bundled apps:

• Books goes from version 8.1 to 8.4
• Freeform, version 4.3 to 4.4
• iPhone Mirroring, version 1.5 to 1.6
• Music, version 1.6.3 to 1.6.4
• Safari, version 26.3.1 (21623.2.7.111.2) in BSI (a) to 26.4 (21624.1.16.11.4)
• TV, version 1.6.3 to 1.6.4
• Audio MIDI Setup, version 3.7 to 3.8
• Digital Color Meter, version 6.10 to 6.11
• Screen Sharing, version 6.2 (758.1) to 6.1 (760.4), note the reduction in version number.

In /System/Library:

• AGX kernel extensions all have build increments
• AppleDiskImages2 kext has a build increment
• AppleEmbeddedAudio kext and its plugin kexts have build increments
• AppleIntel Graphics kexts have version increments
• AppleStorageDrivers kext and its plugin kexts have build increments
• APFS is updated from 2632.80.1 to 2811.101.1, suggesting a substantial change has been made
• new private frameworks include ASMExclaveSupport, AccelerateOpt, AlwaysOnExclavesDaemon, AnteroAgent, AppRemoteAssets, AudioPasscodeDSP, BNNSOdieDelegate, CookingData, CoreTransparency, DynamicPrefetching, InAppFeedback, NanoPassKit, PartnerVisualSearch, a whole family of Unilog frameworks, and a group of iCloudWeb frameworks
• mdimporters updated include those for Application, CoreMedia, Mail, Office, iWork but not RichText.

After seeing the new CookingData private framework, I looked out for RecipeKit, but was disappointed not to see it.

This is probably going to be the last such substantial update to macOS Tahoe, as much of Apple’s engineering effort is transferring to make macOS 27 ready for release as a beta at WWDC in early June.

Apple has released the update to bring macOS Tahoe to version 26.4, and security updates for Sequoia and Sonoma to bring them to 15.7.5 and 14.8.5.

Download size for the 26.4 update on Apple silicon Mac is very large, at around 7.15 GB, but only about 4.14 GB on Intel Macs.

Release notes for 26.4 include:

• support for new AirPods Max 2
• compact tabs as an option in Safari
• Freeform joins Creator Studio, with advanced tools and a premium content library
• Purchase Sharing in Family Sharing

and eight new emoji.

Security release notes for 26.4 list over 70 fixes, those for Sequoia 15.7.5 list about 56, and those for Sonoma 14.8.5 list about 50. None are reported as being known to be exploited in the wild at present.

Enterprise release notes for 26.4 are here.

Firmware in Apple silicon Macs is updated to a new mBoot firmware version numbering system, with the current version given as 18000.101.7. The macOS build number is 25E246, and Safari is version 26.4 (21624.1.16.11.4). Firmware in Intel Macs with T2 chips is updated from 2094.80.5.0.0 (iBridge 23.16.13120.0.0,0) to 2103.100.6.0.0 (iBridge 23.16.14242.0.0,0).

If you’re running SilentKnight older than version 2.14 (71), then it’s likely that it will crash as a result of the change in firmware version. Please use version 2.14 from here.

I’ll be posting an analysis of what has changed later today.

Updated 09:15 25 March 2026 with firmware details for Intel Macs.

If there’s one thing I’ll remember macOS Tahoe for it’s brilliant engineering inside a shockingly flawed interface. Last week’s first Background Security Improvement was yet another example of that trend.

I had enthused about its predecessor the RSR three years ago, although it was sent to the naughty corner after an updated version of Safari told Facebook and other popular sites it wasn’t who they expected. After that trauma, most users shunned RSRs, and it seems engineers who dared mention them were strapped to the front of an F1 car and driven round until they recanted.

Thankfully, RSRs were only put on pause before being rebadged as Background Security Improvements or BSIs, an Orwellian turn of phrase that skilfully avoids the word update despite the fact that they’re still discovered, downloaded and installed by softwareupdated. Now I’ve had a chance to give a fair account of the first public BSI, I can consider what’s wrong with their current implementation.

Location

BSIs are controlled not in Software Update settings, but in their own section at the end of Privacy & Security. As such, they are the only macOS update there, and all others remain in Software Update where they belong. This misleads users, and Software Update reports that Your Mac is up to date when it isn’t, because there’s an outstanding BSI available.

Not only that, but users naturally assume that when Software Update settings have Install macOS updates disabled, no macOS updates will be installed automatically. Little do they realise they can still get a BSI without being asked.

BSIs are currently misplaced in System Settings, and their controls should be moved back to Software Update where RSRs were.

I fear the reasoning behind hiding BSIs among strangers in Privacy & Security was to ensure most Mac users would leave BSIs to be installed automatically. It’s no coincidence that, in addition to this hiding, the automatic installation of BSIs was enabled by default when upgrading to macOS Tahoe. This reeks of deliberate deception.

Control

There is a single on-off toggle provided, to Automatically Install BSIs. Apple explains that “if you choose to turn off this setting, your device will not receive these improvements until they’re included in a subsequent software update.” Thus the user is given a forced choice between macOS deciding when to install an available BSI, or not being notified about that BSI at all.

As with other macOS updates, the user must be given the option to be notified when a BSI is available, and to make their own choice whether and when to install it.

The alternative for users is to disable Automatically Install, watch for news of BSI releases, and, if they wish to receive one, to enable that setting, download and install the BSI, then disable the control again. For many Mac users, that appears to be the best option in the absence of better support.

Although the control is titled Automatically Install, its behaviour is different. When a BSI is found to be available, macOS doesn’t automatically download and install it, but waits for the user to click on the Install button, then to authenticate.

However, if the user isn’t aware that BSI is available, or chooses to ignore it, automatic installation does appear to occur without the user being informed until the Mac is just about to restart, and no authentication seems necessary after all.

This behaviour is the greatest deterrent to users, as it effectively means that their Macs could restart unpredictably with almost no warning, resulting in data loss and disruption to their work. That’s completely unacceptable, and will ensure many will disable BSIs as a precaution to avoid the possibility of data loss. This aversion could be addressed simply by allowing the user full manual control over whether and when a BSI will be installed.

Progress

Despite softwareupdated monitoring progress through the download and preparation phases, the user is shown an indeterminate progress spinner, rather than a progress bar, which would at least give better warning of the restart that is coming. Although much briefer than a full macOS update, a progress bar should be displayed for the download and preparation phases of a BSI.

Restart warning

All previous RSRs, and this first BSI, have required restarts to complete the update. Yet at no time during this BSI was the user told that would be necessary. A notification was displayed a few seconds before the restart, but gave insufficient notice for the user to make any preparations.

It’s essential that information given about the BSI states clearly if a restart will be necessary, and the user is given the same one-minute countdown provided in macOS updates. Bizarrely, the one place that a restart was mentioned is in the dialog to remove a BSI.

Information

Apple’s current support note on BSIs is woefully inadequate, as is obvious by the content of this article. What would appear to be additional information in the BSI settings, marked with the ⓘ Info button, isn’t informative at all, but provides the means to remove a BSI, which is at least an improvement on RSRs, which unaccountably hid removal in the About settings. A more appropriate button should be provided.

BSIs are also only currently covered in the US English version of Apple’s Platform Security Guide. All other localised versions, including British and Canadian English, still contain the outdated section on RSRs. Fortunately, as their content is almost identical, this is revealing rather than misleading.

Version numbering

Ignoring RSR and BSI version numbering, macOS has in recent years achieved clean and systematic version (and build) numbering, without the excesses of the past. By adopting a parenthesised letter as the identifier of a BSI, comparison is clumsy and prone to error. ProcessInfo.processInfo.operatingSystemVersion doesn’t contain a field for the BSI identifier, which is only offered as part of the full string in ProcessInfo.processInfo.operatingSystemVersionString. Version numbers like 26.3.1 (a) and build numbers of 25D771280a are irregular and unnecessary.

Recommendations

• BSI controls should be removed from their hiding place in Privacy & Security and put alongside all other macOS updates in Software Update settings.
• An option should be provided so that users are informed of the availability of BSIs without any obligation for them to be installed automatically.
• Behaviour of the Automatically Install button should be described explicitly to the user. Does it automatically install, and if so, in what circumstances will the user not be so informed?
• BSI download and preparation should be accompanied by a progress bar similar to that for a macOS update.
• When a BSI requires a restart to complete its installation, the user must be informed of that before they consent to the BSI being downloaded.
• When a BSI install is ready to restart the Mac, one minute’s warning notification should be given, just as in macOS updates.
• The BSI support note should provide full details, not a sketchy outline.
• The button to remove a BSI shouldn’t use the ⓘ Info symbol, but something more appropriate to its purpose.
• Apple’s Platform Security Guide should be updated in all its online versions. Is it really that hard to translate from US English to British English?
• Version and build numbering should be redesigned to be more consistent and better accessible in the API.
• Despite having over three years to get them right, BSIs are a worse mess than RSRs were in Ventura. This is a great shame as their technology is still brilliant, but their current interface is shockingly flawed in so many respects.

Reference

Support note about BSIs

Apple has just released its first public Background Security Improvement (BSI) for macOS 26.3.1 Tahoe, labelled as BSI (a)-25D771280a. Once installed, macOS will identify itself as version 26.3.1 (a), with a build number of 25D771280a.

You can install this through Privacy & Security Settings, in the Background Security Improvements section. It doesn’t appear listed in Software Update, although SilentKnight will offer it. Please don’t try to use SilentKnight to install this, though, as it will download successfully but fail to install unless you then use the BSI section in Privacy & Security settings, which will finish the job off.

Apple has now released details of the single vulnerability that this fixes, in WebKit. As a result it updates Safari from 26.3.1 (21623.2.7.11.7) to 26.3.1 (21623.2.7.111.2).

Following installation, your Mac will need to restart for the BSI to be applied.

Apple has just released its regular weekly update to XProtect, bringing it to version 5334. As usual it doesn’t release information about what security issues this update might address.

This version makes no changes to its main Yara rules. Changes to the OSASCRIPT rules in XPScripts.yr include amendments to more than a dozen of them, and two new rules are added for MACOS.OSASCRIPT.GEPEPA and MACOS.OSASCRIPT.TAPEPA. Several rules that previously added the property wide to their text now have wide ascii instead.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5334

Sequoia and Tahoe systems only

This update has now been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5334 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

我们还年轻，可不想看到这个世界处在毫无自由、隐私的边缘。

简单通过 iOS 自带的快捷指令，建立一套量身定制的“主动触发”机制。比如从任何设备发送一条指定短信，即可获取设备实时定位及正面照片。

此方案无需第三方应用，完全基于系统自带功能。

在脚本中按序添加以下动作，以维持设备在线并降低窃贼警惕：

如果不设置，任何自动化都可能被绕过：

窃贼都知道下滑呼出控制中心来开启“飞行模式”。
操作：设置 > 面容 ID 与密码 > 锁定访问时允许：关闭“控制中心”。

这是 iOS 17.3+ 引入的核心安全层，即使非本人掌握了开屏密码，也无法立即更改 Apple ID 或关闭“查找”。
操作：设置 > 面容 ID 与密码 > 开启“被盗设备保护”。

在国内多为物理双卡的背景下，窃贼可以通过拔卡使设备断网，但为了不扩大损失，我们可以禁止其他设备使用。
操作：设置 > 蜂窝网络 > 选择主号 > SIM 卡 PIN 码。
开启后，SIM 卡插入任何新设备均需密码，能有效防止短信验证码登录。

第一次运行会弹出【定位】和【相机】的权限申请，请务必点击【始终允许】。
只有这样，以后在锁屏静默状态下，它才能全自动跑完流程。

Click to view this post.

我们还年轻，可不想看到这个世界处在毫无自由、隐私的边缘。

在 iOS 26 中，Apple 终于引入了原生通话录音功能。出于隐私合规考虑，系统会在录音开始时强制播放 “This call is being recorded” 的语音提示。对于希望静默录音或自定义提示音的用户，目前唯一的解决方案是利用沙盒逃逸漏洞。

macOS：

https://github.com/34306/bl_sbx

Windows：

Use the bl_sbx exploit to hide the call-recording notification sound on iOS – YangJiiii/Disable-Call-Recording-BookRestore-

该方案并非传统的“越狱”，而是一种沙盒逃逸（Sandbox Escape）技术。它利用了 iOS 系统中两个守护进程之间的信任机制缺陷，实现对受限文件系统的写入。

在操作前，请务必备份数据，避免风险。

由于目前自动化工具（如 Misaka26）尚未完全适配，使用 Python 脚本进行手动替换是较为稳妥的方式。

你需要一台电脑，并配置好 Python 3 环境。

你需要准备一个用于替换系统原声的音频文件。

将 iPhone 连接至电脑，并确保已点击“信任此电脑”。

操作完成后，请按照以下步骤验证是否成功：

marin11:

虽然知道可能这个功能的设计哲学是让用户无感的自动功能 但是有没有办法全速度上传备份呢？

有的时候旅游的照片一天几百张，在酒店一晚上都备份不完。。。 还是说外区 apple id 会好一点？

zj9495:

已经用了 4 年的 21 款 MBP ，刚入手就买了 3 年的 ac+，去年到期又续了一年。

现在电池明显缩水，充电过程发热严重，电池电量低的时候还会明显卡顿，快要过保了到合肥直营店检测电池容量 81%，店员以系统检测为准拒绝质保更换电池，拨打 400 电话客服申请也是拒绝更换，一切以店里检测为准。

我是真的草了，用了 4 年的电池还给我说检测电池容量没到更换标准，使用第三方软件检测电池健康度已经到了 71%，4 年的 ac+钱白花了，下台 mac 再买 ac+ 我是🐶

我们还年轻，可不想看到这个世界处在毫无自由、隐私的边缘。

实际上，大多数 App 和服务定价并非全球统一。如 OpenAI 和许多跨国科技公司一样，会采用“购买力平价（Purchasing Power Parity, PPP）”策略，即根据不同国家和地区的经济水平、人均收入来调整产品价格。

这便在全球市场中形成了一些“价格洼地”，其中，尼日利亚正是全球订阅 ChatGPT Plus 最便宜的地区。

全球部分地区价格对比：

整个流程的核心是在尼日利亚区的数字生态内完成支付闭环。

我们还年轻，可不想看到这个世界处在毫无自由、隐私的边缘。

AI 搜索公司 Perplexity 与支付平台 PayPal 达成全球合作，为符合条件的 PayPal 用户提供为期一年的 Perplexity Pro 免费订阅资格，价值 200 美元（约人民币 1450 元），并包含其 AI 浏览器 Comet 的优先体验权。

Perplexity Pro 与 PayPal 合作

活动链接：https://www.perplexity.ai/join/p/paypal-subscription

为防止一年后产生 200 美元的年费，强烈建议领取成功后，立即通过以下任一方式取消自动续订。取消后，Pro 会员资格仍会完整保留一年。

在 Perplexity 官网取消

在 PayPal 后台取消

很多人把这次苹果 WWDC25 发布的液态玻璃界面，当作一次 UI 的新风格更新来看。界面变得更模糊了，更柔和了，也更「高科技感」了，但如果我们只是停留在它看起来好不好看，其实可能错过了一些更关键的东西。

因为这一次，苹果的改变并不仅仅发生在界面上，它背后所传递的，是一套新的交互前提。而这套前提，可能关系到未来十年我们如何使用手机，甚至 —— 我们是否还继续使用手机。

这期视频不是为了追热点，而是想带你冷静地拆解这套语言背后的逻辑：它是如何从视觉层出发，向平台层推进的？它和我们以为的「透明手机」之间，真的有联系吗？而眼镜设备仍未普及的这几年，我们到底应该关注什么？

如果这些问题你也在想，那就点进来看看吧。

播放地址：

https://youtu.be/WpljvdXmwvY

https://www.bilibili.com/video/BV1yz3Bz8Ev2/

本期关联播客：https://suithink.me/2025/07/07/13ylog/

既然这 10 年间的所有线索（等边三摄、Face ID、Lidar、Liquid Glass）都指向空间计算，那显然 iPhone 就是每一个人都可以接触到的第一台空间计算设备。最便捷最普及的空间计算设备，才是让 AI（不止LLM）真正普及到每一个人手上的基础设施。