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.