Marcin Wichary (Hacker News): Half of my education in URLs as user interface came from Flickr in the late 2000s. […] This was incredible and a breath of fresh air. No redundant www. in front or awkward .php at the end. No parameters with their unpleasant ?&= syntax. No % signs partying with hex codes. […]

Tom Nichols, writing for The Atlantic:

When the 2003 war with Iraq ended, U.S. Ambassador Barbara Bodine said that when American diplomats embarked on reconstruction, they ruefully joked that “there were 500 ways to do it wrong and two or three ways to do it right. And what we didn’t understand is that we were going to go through all 500.”

Mike Masnick, writing for Techdirt:

Read that again. If West Virginia wins — if an actual court orders Apple to start scanning iCloud for CSAM — then every image flagged by those mandated scans becomes evidence obtained through a warrantless government search conducted without probable cause. The Fourth Amendment’s exclusionary rule means defense attorneys get to walk into court and demand that evidence be thrown out. And they’ll win that motion. It’s not even a particularly hard case to make.

Rob Griffiths, writing at The Robservatory:

So I have macOS Tahoe on my laptop, but I’m keeping my desktop Mac on macOS Sequoia for now. Which means I have the joy of seeing things like this wonderful notification on a regular basis. Or I did, until I found a way to block them, at least in 90 day chunks. [...]

The secret? Using device management profiles, which let you enforce policies on Macs in your organization, even if that “organization” is one Mac on your desk. One of the available policies is the ability to block activities related to major macOS updates for up to 90 days at a time (the max the policy allows), which seems like exactly what I needed.

I followed Griffiths’s instructions about a week or so ago, and I’ve been enjoying a no-red-badge System Settings icon ever since. And the Tahoe upgrade doesn’t even show up in General → Software Update. With this profile installed, the confusing interface presented after clicking the “ⓘ” button next to any available update cannot result in your upgrading to 26 Tahoe accidentally.

I waited to link to Griffiths’s post until I saw the pending update from Sequoia 15.7.3 to 15.7.4, just to make sure that was still working. And here it is. My Software Update panels makes it look like Tahoe doesn’t even exist. A delicious glass of ice water, without the visit to hell.

I have one small clarification to Griffiths’s instructions though. He writes:

4/. Optional step: I didn’t want to defer normal updates, just the major OS update, so I changed the Optional (set to your taste) section to look like this:

forceDelayedSoftwareUpdates

This way, I’ll still get notifications for updates other than the major OS update, in case Apple releases anything further for macOS Sequoia. Remember to save your changes, then quit the editor.

I was confused by this step, initially, and only edited the first line after <!-- Optional (set to your taste) -->, to change <true/> to <false/> in the next line. But what Griffiths means, and is necessary to get the behavior I wanted, requires deleting the other two lines in that section of the plist file. I don’t want to defer updates like going from 15.7.3 to 15.7.4.

Before editing:

<!-- Optional (set to your taste) -->
<key>forceDelayedSoftwareUpdates</key><true/>
<key>enforcedSoftwareUpdateMinorOSDeferredInstallDelay</key><integer>30</integer>
<key>enforcedSoftwareUpdateNonOSDeferredInstallDelay</key><integer>30</integer>

After:

<!-- Optional (set to your taste) -->
<key>forceDelayedSoftwareUpdates</key><false/>

I’ll bet that’s the behavior most of my fellow MacOS 15 Sequoia holdouts want too.

Apple’s solution to this dilemma — to show the “Tap Recents to Call” in Settings if, and only if, Unified is the current view option in the Phone app — is lazy. And as a result, it’s quite confusing.