Let’s try this again. Apple has rereleased Rapid Security Response updates for iOS 16.5.1 (c), iPadOS 16.5.1 (c), and macOS Ventura 13.4.1 (c) to fix a WebKit vulnerability that could allow malicious Web content to execute arbitrary code. The vulnerability is being actively exploited, and despite the website loading issues with Safari in the previous versions, I encourage you to install these updates as soon as feasible. They loaded quickly, in under 4 minutes on each of my devices, including the necessary restart.

In the event of problems, remember that you can uninstall Rapid Security Responses (but not regular updates) just as quickly as you install them (see “What Are Rapid Security Responses and Why Are They Important?” 2 May 2023).

• iPhone or iPad: Navigate to Settings > General > About > iOS Version, and then tap Remove Security Response. Tap Remove to confirm.
• Mac: Go to System Settings > General > About, click the ⓘ next to the macOS version, click Remove & Restart, and confirm the action.

The new versions fix an issue that prevented a few websites from displaying properly in Safari by changing its user agent identifier to remove the parenthetical letter that seems to have confused sites like Facebook and Instagram. Apple also incremented Safari’s build number.

While Apple’s choice of letters for Rapid Security Response version numbers is questionable, Meta and other companies whose websites were affected also bear responsibility for not failing gracefully when encountering unexpected user agent identifiers.

Let us know in the comments if you experience any other issues associated with the Rapid Security Response updates.

When we covered the update to macOS 13.3 Ventura in “Apple Releases iOS 16.4, iPadOS 16.4, macOS 13.3 Ventura, watchOS 9.4, tvOS 16.4, and HomePod Software 16.4” (27 March 2023), Howard Rosenman commented that the Aerial screen saver would no longer show on both of the displays attached to his M2 Mac mini. He was right, and others confirmed that the problem afflicted both Apple and third-party screen savers, such as Aerial and Electric Sheep.

I don’t know when Apple fixed the bug because the company didn’t see fit to mention it in any release notes. Regardless, in macOS 13.4.1, the screen saver again works properly with multiple displays. If, like me, you switched your screen saver module because it wouldn’t show on all your displays, you can now return to your preferred approach in System Settings > Screen Saver.

Alas, Apple didn’t tackle the more complex problem of getting the screen saver to display edited or rotated photos rather than the original image (see “macOS Photo Screen Savers Still Don’t Properly Display Rotated or Edited Images,” 5 March 2023).

Want to help Apple find bugs and get a glimpse of the future in the process? You can now install public betas of Apple’s forthcoming 2023 operating systems: macOS 14 Sonoma, iOS 17, iPadOS 17, watchOS 10, tvOS 17, and HomePod Software 17. For our favorite features, see “12 Compelling Features Coming to Apple’s Operating Systems in 2023” (5 June 2023) and “Another Dozen Compelling Features Coming to Apple’s Operating Systems in 2023” (7 June 2023).

You will need compatible hardware; for the specifics, see “The Real System Requirements for Apple’s 2023 Operating Systems” (19 June 2023). I strongly recommend installing only on dedicated test hardware. You would be nuts to run one of these betas on a device you rely on for, well, anything. You’re likely to run into incompatibilities and bugs—that’s the entire point of a beta program.

Although I always recommend making a backup before installing an update to any operating system, you shouldn’t install these betas on anything you can’t erase at the drop of a hat without fear of data loss.

To be safe, avoid connecting your primary iCloud account with the betas to avoid a bug causing an upstream problem. You wouldn’t want beta iCloud Drive code to corrupt important data you use on your everyday devices.

If it sounds like I’m trying to dissuade you from installing the public betas, I am. If you don’t know what you’re getting yourself into, you could lose data or waste a lot of time recovering from problems. Conversely, if you’ve done this before and are comfortable with the technical implications, have fun! I certainly intend to.

To try one or more of the betas, go to Apple’s public beta page, read the FAQ, and sign up for the beta program. Once you’re in, you enroll your devices, after which the betas appear in Software Update.

Finally, remember that the main reason to test public betas is so you can report bugs, so revisit David Shayer’s advice in “How to Report Bugs to Apple So They Get Fixed” (17 June 2020).

Book reviews are unusual for TidBITS, and I don’t intend to share my Libby activity with you regularly. But Cory Doctorow’s novel Red Team Blues merits mention. In part, that’s because the fictional world it depicts could be pulled from Silicon Valley headlines and backchannel forums of today. But I also found it intriguing based on some things that Cory has written about the role of fiction in the modern world.

I’m not close friends with Cory, and we’ve met in person only a handful of times. Nor have we exchanged significant amounts of email or interacted much in online communities. But we have orbited similar spaces in the Internet world for decades, him with Boing Boing, the Electronic Frontier Foundation, and his books, and me with TidBITS, Info-Mac, the Internet Starter Kit, and Take Control. He’s one of those people who has long been a fixture of my Internet firmament, even if that means exchanging email only every 5 or 10 years.

Our last exchange came in 2020 after I read a piece he’d written for Slate titled “The Dangers of Cynical Sci-Fi Disaster Stories.” I was drawn in by the subtitle: “I’m changing how I write fiction—for the benefit of the real world.” I’m suspicious that our shared fictions subtly affect our responses to real-world problems, and that was the focus of Cory’s piece.

Made-up stories, even stories of impossible things, are ways for us to mentally rehearse our responses to different social outcomes. Philosopher Daniel Dennett’s conception of an intuition pump—“a thought experiment structured to allow the thinker to use their intuition to develop an answer to a problem”—suggests that fiction (which is, after all, an elaborate thought experiment) isn’t merely entertainment.

In response to that, I emailed Cory, writing:

I’ve long been uncomfortable with a great deal of mainstream entertainment, whether we’re talking about science fiction books, movies, TV shows, or video games. It’s easy to brush aside concerns by saying that people can tell the difference between fact and fiction, but I think our fiction has gotten so good and so compelling—and in the case of visual genres, so realistic—that at some low level, we really are having trouble separating what’s real from what’s imagined. The intuition pump is a nice way to encapsulate that. The stories may be compelling, but they seldom resonate with how I see real people acting in everyday life or address the messiness of the real-world issues we have to deal with.

His reply drew a fine-line distinction between how we act and how we expect others to act. We know we’re good people because we’re in our own heads. But we’re not in other people’s heads, so their actions are often mysterious, allowing the fiction we consume a stronger vote in how we imagine others might behave. He said:

I think there’s a subtle, crucial difference between the idea that fiction inspires us to violence and the idea that it makes us anticipate violence on the part of others.

In the Slate piece, he explains that he realized this after moving to California from firearm-free London, where he lived after growing up in Toronto. Initially, he was shocked by the prevalence of gun stores—did all his neighbors really possess lethal weapons? The gun stores faded into the background until the pandemic hit and people lined up around the block to buy handguns. Why? To protect themselves once civilization broke down. He writes in the article:

I think that our pulp fiction has done us a disservice, creating a commonsense assumption that we are one power failure away from Mad Max: Fury Road. The reality is ever so much messier, full of people trying to do the right thing—which still causes high-stakes, serious conflicts, but they’re conflicts of good faith and sincere disagreement.

The conflicts in Red Team Blues aren’t so much good faith and sincere disagreement, but each of the main parties acts rationally within its worldview, lending a frustrating sense of “Well, of course they’re going to do that” to the plot while leaving our hero to navigate the rocky rapids of a situation beyond his direct control.

Red Team Blues is the present-day story of Martin Hench, a 67-year-old “digital forensic accountant” who specializes in recovering money squirreled away by modern-day thieves in cryptocurrencies, holding companies, and offshore accounts. He’s called in by Danny Lazer, a long-time friend who spent decades writing cryptographic code and battling with the NSA before hitting it big with a company that sold crypto libraries and workflows to the tech world. Lazer has leveraged his fortune to create Trustlesscoin, a new cryptocurrency that avoids the environmentally damaging proof-of-work approach by—with some poetic license—running code on the secure enclaves embedded in iPhones and other smartphones.

To have the option of rolling back an early mistake, something that’s generally impossible with a blockchain, Lazer has illicitly acquired the signing keys for the secure enclaves. The laptop containing those keys was stolen and Lazer’s hardware key was pickpocketed, meaning that the keys used by Apple, Samsung, and other manufacturers are in the wind, and the billion dollars in Trustlesscoin is at risk. Given that Hench’s fee is a flat 25% of the value of the recovered assets, $250 million is impossible to turn down.

Getting the MacGuffin laptop back is the first order of business, but Hench’s success there lands him in a war between a Mexican drug cartel and a powerful Azerbaijani family bent on revenge for the killing of a member who participated in the laptop theft. An ethically dubious Department of Homeland Security seems happy to let it all continue in the name of the status quo. Leads crop up, friends weave in and out of the plot, and Hench motors around northern California in the Unsalted Hash, a very slightly used forty-foot touring bus acquired in lieu of payment from a rock star whose manager absconded with $2 million. At 67, Hench avoids physical confrontation but isn’t above going to ground—literally—in a homeless camp when he needs to lie low for a few days.

I haven’t spent much time in San Francisco since Macworld Expo ended in 2014, but the Bay Area of Red Team Blues feels real, and I can’t help but wonder if Cory had first-person sources for his gut-wrenching depictions of homelessness. What felt the most real, however, were the characters. Not the specific people in the book, but the old tech world types. The aging crypto hacker, the data center security guy, the early-days secretary who works her way up through customer service and documentation to retire as a VP. (Whose finances Hench rescues from a grifter ex-husband, triggering a romance subplot.) I don’t know these people, but I know people like them, and Cory’s characters rang true. They’re part of that tech world orbit I was talking about, the outer rings of which contain those of us who connected via UUCP, harangued against DRM and shrink-wrap licenses, tilted at the windmill of digital identity, and worried that AOL would be the end of the Internet. Our lives aren’t as interesting as Martin Hench’s or his friends, but that’s merely because we don’t have Cory Doctorow scripting them. And the world of Red Team Blues may be more exciting than ours, but its solutions still prime your intuition pump with well-intentioned people trying to do the right thing rather than copping out with a hail of bullets.

If you have memories of that 1990s tech universe, you’ll enjoy Red Team Blues. Like all of Cory’s books, you can buy it direct as a DRM-free EPUB or MobiPocket. It’s $15, or $20 for an audiobook version read by (of course) Wil Wheaton, or a bit more if you want a dead-tree hardcover copy.

Oh, and the title? In the security world, red teams play offense—they attack systems and look for holes that will grant them entry. Blue teams are defensive; they design and maintain internal defenses and react to red team attacks. As Martin Hench—a lifelong red team guy—says, when you’re on the blue team, you have to be perfect, whereas the red team merely has to find a single mistake. Once you’ve finished the book, you may gain a better appreciation for what it’s like for companies like Apple that are stuck playing on the blue team.