#macos

The interaction of these two features can seem a little complicated, too, depending on how they’re enabled:

Forwarding off, Messages in iCloud off: SMS/MMS messages appear only on your iPhone. iMessages appear on any device logged into the same iCloud account, as long as they are available on a network. Some devices may miss some messages.
Forwarding on, Messages in iCloud off: SMS/MMS messages and iMessages are delivered to your iPhone and any other devices logged into the same iCloud account and currently online. Some devices may miss some messages.
Forwarding off, Messages in iCloud on: SMS/MMS message notifications appear only on your iPhone, but are synced to other devices via iCloud. iMessage notifications appear on all connected devices and are synced among those that are offline when a message comes in.
Forwarding on, Messages in iCloud on: Notifications for SMS/MMS messages and iMessages appear on all connected devices that are available on a network. All text and iMessages are synced to all connected devices.

patch intel macs to get them working with newer OS versions.

Ghostty is a fast, feature-rich, and cross-platform terminal emulator that uses platform-native UI and GPU acceleration.

This also happens with Visual Studio Code. I think I denied it the other day in a bit of haste because I didn't realize why code was asking for permissions, but in hindsight I think I was using something in Visual Studio Code's terminal that triggered it. :/

Apple brought Local Network privacy permissions from iOS to macOS — but they’re not working as intended here. Every time Chrome updates (which happens silently in the background), macOS may treat it like a brand-new app, generating yet another permissions entry.

Worse, if you click “Don’t Allow” once, macOS may permanently block access, and toggling it back on in Settings doesn’t fix it. Several AppleCare technicians have confirmed this is a macOS-level bug, not a Chrome issue.

Method 1: Reset Permissions Without Deleting Chrome Dat This option resets the network permissions without touching your Chrome profile (bookmarks, extensions, saved passwords, etc.).

Steps:

Boot your Mac into Safe Mode Move Google Chrome from /Applications to the Trash (We previously explained how you can delete Chrome from your Mac.) Don’t touch your user data in ~/Library/Application Support/Google/Chrome Open Terminal (use Spotlight: Cmd + Space → type “Terminal”) Run this command: sudo tccutil reset SystemPolicyNetworkVolumes Enter your Mac password and hit Enter Open System Settings > Privacy & Security > Local Network — Chrome should be gone Restart your Mac normally Download and reinstall Google Chrome Open Chrome and try visiting a local IP (e.g. 192.168.1.1) When prompted, click Allow for local network access Chrome should now show up once in the list — and local access should work Method 2: Full Clean Reset (Best for Persistent Issues) If Method 1 doesn’t work, this more thorough approach almost always does — but it fully resets Chrome, including removing stored data unless you’re syncing with a Google account.

Steps:

Shut down your Mac and uncheck “Reopen windows” Boot into Safe Mode Move Google Chrome to Trash and empty the Trash Open Terminal and run: sudo tccutil reset SystemPolicyNetworkVolumes Open System Settings > Privacy & Security > Local Network to confirm Chrome is gone Restart your Mac normally Reinstall Chrome Launch Chrome and access a local IP When prompted, click Allow Chrome should appear only once in the settings, with full local access Important: If you miss or decline the permission prompt, you’ll need to redo the entire process.

Apple’s release notes detail that RDMA integrates with the Thunderbolt framework to enable zero-copy data transfers, meaning data moves directly from one device’s memory to another’s without intermediate buffering. This eliminates bottlenecks associated with TCP/IP protocols, which Thunderbolt previously emulated. Insiders note that while Thunderbolt 5 offers peak speeds, real-world performance depends on factors like cable quality and device compatibility—only M4 and later chips fully support this enhanced mode.

Diving deeper into the technical specifics, Apple’s developer documentation explains that RDMA over Thunderbolt is exposed through new APIs in the macOS networking stack. Developers can initialize clusters using Swift or Objective-C calls that negotiate memory mappings directly over the Thunderbolt bus. This is a departure from traditional Ethernet-based RDMA, which relies on Infiniband or RoCE (RDMA over Converged Ethernet), adapting instead to Thunderbolt’s point-to-point topology.

For those building apps, the update introduces protocols for fault-tolerant clustering. If a device drops out—say, due to a disconnected cable—the system can redistribute workloads dynamically, minimizing disruptions. Testing scenarios outlined in the notes suggest latency as low as microseconds for small transfers, rivaling dedicated high-performance computing setups.

Security is paramount in such a powerful feature. Apple’s notes emphasize built-in encryption for RDMA transfers, preventing unauthorized memory access. A separate 9to5Mac report on the update’s patches reveals fixes for kernel vulnerabilities that could have been exploited in clustered environments, ensuring that the feature doesn’t become a vector for attacks.

Looking at adoption, early sentiment on X suggests enthusiasm among AI researchers. One thread discussed collaborative model training, where multiple users contribute compute power via clustered Macs, democratizing access to high-end AI tools. This could disrupt markets dominated by cloud providers, offering cost savings for startups avoiding subscription fees.

However, if you have enabled Automatically hide and show the Dock in System Preferences → Dock, the app switcher will appear on the display which has last shown the Dock.