Enlarge/ A movable robotic face covered with living human skin cells.
In a new study, researchers from the University of Tokyo, Harvard University, and the International Research Center for Neurointelligence have unveiled a technique for creating lifelike robotic skin using living human cells. As a proof of concept, the team engineered a small robotic face capable of smiling, covered entirely with a layer of pink living tissue.
The researchers note that using living skin tissue as a robot covering has benefits, as it’s flexible enough to convey emotions and can potentially repair itself. “As the role of robots continues to evolve, the materials used to cover social robots need to exhibit lifelike functions, such as self-healing,” wrote the researchers in the study.
The study describes a novel method for attaching cultured skin to robotic surfaces using “perforation-type anchors” inspired by natural skin ligaments. These tiny v-shaped cavities in the robot’s structure allow living tissue to infiltrate and create a secure bond, mimicking how human skin attaches to underlying tissues.
To demonstrate the skin’s capabilities, the team engineered a palm-sized robotic face able to form a convincing smile. Actuators connected to the base allowed the face to move, with the living skin flexing. The researchers also covered a static 3D-printed head shape with the engineered skin.
Enlarge/ “Demonstration of the perforation-type anchors to cover the facial device with skin equivalent.”
Takeuchi et al. created their robotic face by first 3D-printing a resin base embedded with the perforation-type anchors. They then applied a mixture of human skin cells in a collagen scaffold, allowing the living tissue to grow into the anchors.
Enlarge/ The logo for PaLM 2, a Google large language model.
Google
Google announced today that it has added support for 110 new languages to Google Translate, nearly doubling the number of languages that can be translated.
In a blog post, Google Senior Software Engineer Isaac Caswell claimed that the newly added languages are spoken by more than 614 million people, or about 8 percent of the global population.
He noted that about a quarter of the languages originate in Africa, “representing our largest expansion of African languages to date.”
The blog post also went into some light detail about Google’s philosophy for choosing languages and for deciding which dialects to support:
Languages have an immense amount of variation: regional varieties, dialects, different spelling standards. In fact, many languages have no one standard form, so it’s impossible to pick a “right” variety. Our approach has been to prioritize the most commonly used varieties of each language. For example, Romani is a language that has many dialects all throughout Europe. Our models produce text that is closest to Southern Vlax Romani, a commonly used variety online. But it also mixes in elements from others, like Northern Vlax and Balkan Romani.
This update brings the total number of languages supported by Google Translate to 243, which is just the beginning of its publicized initiative to ultimately support 1,000 languages through the use of AI. You can see the full list of languages added in a help page published by Google.
By contrast, Apple Translate supports 21 languages, though that number includes both US and UK English as distinct options. Apple recently announced plans to add Hindi to its Translate app. Of course, Apple and Google take very different approaches to—and have different levels of investment in—these tools.
Enlarge/ Apple has a lot to say about the third-party battery market in “Longevity, by Design,” specifically about how many batteries fail to meet testing standards.
Apple
Earlier this week, Apple published a whitepaper titled “Longevity by Design.” The purpose, Apple says, is to explain “the company’s principles for designing for longevity—a careful balance between product durability and repairability.” It also contains some notable changes to Apple’s parts pairing and repair technology.
Here is a summary of the action items in the document’s 24 pages:
True Tone, the color-balancing screen feature, can soon be activated on third-party screens, “to the best performance that can be provided.”
Battery statistics, like maximum capacity and cycle count, will be available “later in 2024” for third-party batteries, with a notice that “Apple cannot verify the information presented.”
Used Apple parts, transferred from one to another, will be “as easy to use as new Apple parts” in select products “later this year.”
Parts for “most repairs” from Apple’s Self Service Repair program will no longer require a device serial number to order.
Changes timed to “later this year” may well indicate their arrival with iOS 18 or a subsequent update.
Apple’s take on repair focuses on scale
To whom is Apple’s document explaining its principles? Apple might say it’s speaking to consumers and the public, but one might infer that the most coveted audience is elected representatives, or their staff, as they consider yet another state or federal bill aimed at regulating repair. Earlier this year, Oregon and Colorado passed repair bills that stop companies from halting repairs with software checks on parts, or “parts pairing.” Other recent bills and legal actions have targeted repair restrictions in Minnesota, Canada, and the European Union.
Apple came out in support of a repair bill in California and at the federal level, in large part because it allows for parts and tools pricing at “fair and reasonable terms” and requires non-affiliated vendors to disclose their independence and use of third-party parts to customers.
“Longevity, by Design” stakes out Apple’s position that there are things more important than repair. Due to what Apple says is its unique combination of software support, resale value, and a focus on preventing the most common device failures, the company “leads the industry in longevity” as measured in products’ value holding, lifespans, and service rates, Apple says. Hundreds of millions of iPhones more than five years old are in use, out-of-warranty service rates dropped 38 percent from 2015 to 2022, and initiatives like liquid ingress protection dropped repair rates on the iPhone 7 and 7 Plus by 75 percent.
“The reliability of our hardware will always be our top concern when seeking to maximize the lifespan of products,” the whitepaper states. “The reason is simple: the best repair is the one that’s never needed.”
Photos from Apple’s “Longevity, by Design” document showing the water ingress testing as part of its design.
Apple
Consider the charge port
Apple offers the charging port on iPhones as “an internal case study” to justify why it often bundles parts together rather than making them individually replaceable. From the independent repair shops and techs I’ve talked to in my career, iPhone charging ports, and the chips that control them, are not an uncommon failure point. “Cheap charging cables from 7-11 are serial killers,” one board-level repair shop once told me. Apple disagrees, saying it must consider the broader impact of its designs.
“Making the charging port individually replaceable would require additional components, including its own flexible printed circuit board, connector, and fasteners that increase the carbon emissions required to manufacture each device,” Apple states. This could be justified if 10 percent of iPhones required replacement, but Apple says “the actual service rate was below 0.1%.” As such, keeping the port integrated is a lower-carbon-emission choice.
The streaming-only Xbox would have looked like a smaller, squarer relative of the Series S.
Microsoft
The console had cutouts on the bottom and back, presumably for air cooling.
Microsoft
Front-mounted Xbox button and USB port, much like the Series S.
Microsoft
Rear-mounted Ethernet, HDMI, and power. The console would likely have worked over Wi-Fi, too, but wired Ethernet does help with latency and consistency when streaming games.
Microsoft
Controller sync button on the side.
Microsoft
There was a logo and a Series S-ish circle on the top of the Keystone Xbox, but there are no cutouts depicted, so this may have been a stylistic choice rather than a place for the console to vent hot air.
Microsoft
Microsoft’s mid-generation plans for the Xbox Series S and X consoles looked a whole lot different a couple of years ago than it does now. A leaked slide deck from the FTC v. Microsoft case last year outlined detailed plans for a spruced up Series S, an overhauled Series X, and even a redesigned controller. Another part of that roadmap included a streaming-only version of the Xbox, codenamed Keystone, that was designed to connect to Microsoft’s Xbox Cloud Gaming servers rather than rendering games locally.
Microsoft has talked openly about this version of the Xbox before. Microsoft Gaming CEO Phil Spencer told The Verge that the Keystone console was designed and fully functional, but that it wasn’t launched because Microsoft had a hard time getting the price down low enough that it made sense next to the $299 Series S (which already occasionally goes on sale in the $200 to $250 range).
We’ve already seen glimpses of Keystone—once on Spencer’s shelf, and again in the FTC v. Microsoft documents. Both of those depictions were partial, or seen from a distance. But a new design patent document (PDF) unearthed by Windows Central shows even more detailed renderings of what the cloud Xbox would have looked like.
Series S meets Apple TV
Keystone’s styling was strongly reminiscent of the disc-drive-less Series S, with the same boxy white design and front-mounted Xbox button and USB port. There’s also a similar circular cutout on top, though it may not be an air vent as it is in the Series S—all of the holes depicted in the patent are on the back and bottom, and a streaming box certainly wouldn’t have needed the same cooling capacity as the AMD-designed CPU and GPU in the Series S.
The console also would have been square-shaped and considerably smaller than a Series S—not quite as small as a dedicated video-streaming box like an Apple TV or Roku Ultra, but not too far off either (the patent document doesn’t list dimensions, but we’ve done a rough size comparison using the HDMI and Ethernet ports on the Keystone box and an Apple TV 4K). The console’s controller sync button would have been mounted on its side, rather than in front, as it is on the Series S.
Enlarge/ The cloud Xbox compared to a current-generation Apple TV 4K, with sizes roughly normalized based on the sizes of the HDMI and Ethernet ports. The Xbox console would have been a bit larger, but not dramatically so.
Apple/Microsoft/Andrew Cunningham
In the alternate reality of the FTC v. Microsoft slide deck, all of these new consoles and the new controller would have been announced or launched by now. But as Microsoft Gaming CEO Phil Spencer said shortly after those documents leaked, the company’s plans have changed substantially in the interim. A disc-less version of the Series X is coming, but it looks exactly like the current version of the console without a disc drive; Microsoft is also pursuing a strategy where it takes more of its internally developed games multi-platform, rather than restricting them to the Xbox and to Windows PCs. These moves are at least partially in response to sliding revenue from Microsoft’s console business, which has seen its revenue decline by double digits year over year for the last couple of years.
Neither Spencer nor Microsoft has ever said never about the Keystone console, leaving the door open to an eventual release if and when the price of manufacturing the console comes down. In the meantime, the streaming-only Xbox lives on as an app for newer Samsung smart TVs.
One of Windows 11’s more contentious changes is that, by default, both the Home and Pro editions of the operating system require users to sign in with a Microsoft account during setup. Signing in with an account does get you some benefits, at least if you’re a regular user of other Microsoft products like OneDrive, GamePass, or Microsoft 365 (aka Office). But if you don’t use those services, a lot of what a Microsoft account gets you in Windows 11 is repeated ads and reminders about signing up for those services. Using Windows with a traditional local account is still extremely possible, but it does require a small amount of know-how beyond just clicking the right buttons.
On the know-how front, Microsoft has taken one more minor, but nevertheless irritating, step away from allowing users to sign in with local accounts. This official Microsoft support page walks users with local accounts through the process of signing in to a Microsoft account. As recently as June 12, that page also included instructions for converting a Microsoft account into a local account. But according to Tom’s Hardware and the Internet Wayback Machine, those instructions disappeared on or around June 17 and haven’t been seen since.
Despite the documentation change, most of the workarounds for creating a local account still work in both Windows 11 23H2 (the publicly available version of Windows 11 for most PCs) and 24H2 (available now on Copilot+ PCs, later this fall for everyone else). The easiest way to do it on a PC you just took out of the box is to press Shift+F10 during the setup process to bring up a command prompt window, typing OOBEBYPASSNRO, rebooting, and then clicking the “I don’t have Internet” button when asked to connect to a Wi-Fi network.
Other workarounds include using the Rufus tool to create a USB installer that will automatically bypass the Microsoft account sign-in requirement, or (for Windows 11 Pro users) indicating that you want to join the PC to a corporate domain and then not actually joining it to a domain. Setting the PC up with a Microsoft account and then signing out afterward is also still an option.
There is one workaround that has allegedly stopped working—it used to be that trying to “sign in” with a nonexistent email account would get you a local sign-in option. But as of earlier this month, according to Windows Central editor Zac Bowden, it looks like the Windows 11 setup screen will just ask you to try another email address instead.
To be fair to Microsoft, all the big tech companies want you to sign in with an account before you can use all the features of the software, but neither Apple nor Google goes as far as to mandate account sign-in to access basic functionality. Macs, iPhones, and iPads will all let you complete the setup process without signing in, though you do have to know which buttons to click. Google will allow you to use Chromebooks in guest mode, and Android phones and tablets are still usable without signing in (though this does make it more difficult to find and install apps). Microsoft’s pushiness remains unique; there’s definitely a difference between a company that would really prefer that you sign in, and one that forces you to.
Linux and its code are made by people, and people are not with us forever. Over the weekend, a brief message on the Linux kernel mailing list reminded people of just how much one person can mean to a seemingly gargantuan project like Linux, and how quickly they can disappear:
Denise Finger, wife of the deceased, wrote to the Linux Wireless list on Friday evening:
This is to notify you that Larry Finger, one of your developers, passed away on June 21st.
LWN.net reckons that Finger, 84, contributed to 94 Linux kernel releases, or 1,464 commits total, at least since kernel 2.6.16 in 2006 (and when the kernel started using git to track changes). Given the sometimes precarious nature of contributing to the kernel, this is on its own an impressive achievement—especially for someone with no formal computer training, and who considered himself a scientist.
The deepest of trenches: Linux Wi-Fi in the 2000s
That kind of effort is worth celebrating, regardless. But it’s the space that Finger devoted himself to that makes him a notably patient, productive contributor.
Getting Wi-Fi to work on a device running Linux back when Finger started contributing was awful. The chances of your hardware being recognized, activated, and working properly right after install was akin to getting a straight flush in poker. If nobody had gotten around to your wireless chipset yet, you used NDISwrapper, a Windows-interfacing kludge tool that simultaneously made your Linux install less open and yet still painful to install and maintain.
Finger started fixing this with work on Broadcom’s BCM43XX drivers. Broadcom provided no code for its gear, so Finger helped reverse-engineer the necessary specs by manually dumping and reading hardware registers. Along with Broadcom drivers, Finger also provided Realtek drivers. Many commenters across blogs and message boards are noting that their systems are still using pieces of Finger’s code today.
Fixing mainframes, science gear, and RV resorts
Larry Finger, and fish, from his Quora profile.
Quora
Finger doesn’t have a large footprint on the web, outside of his hundreds of kernel commits. He has a page for DRAWxtl, for producing crystal-structure drawings, on his personal domain, but not a general personal page. He sometimes answered Quora questions. He had a GitHub profile, showing more than 100 contributions to projects in 2024.
Perhaps the biggest insight into Finger found in one place is a three-part series for Linux Journal, “Linux in a Windows Workstation Environment,” written in 2005, when he was roughly 65. He summarizes his background: Fortran programmer in 1963, PDP-11 interfaces to scientific instruments in the 1970s, VAX-11/780 work in the early 1980s, and then Unix/Linux systems, until retiring from the Carnegie Institution for Science in Washington, DC, in 1999. The mineral Fingerite is named for Finger, whose work in crystallography took him on a fellowship to northern Bavaria, as noted in one Quora answer about the Autobahn.
“At that time, I became a full-time RV resident, dedicated to the avoidance of cold weather,” Finger writes. He and his wife Denise arrived that year at a 55-plus RV community in Mesa, Arizona. He joined the computer club, which had a growing number of Windows PCs sharing a DSL connection through one of the systems running WinGate. A new RV resort owner wanted to expand to 22 workstations, but WinGate licenses for that many would have been expensive for the club. Finger, who was “highly distrustful of using Windows 98 in a mission-critical role,” set to work.
Finger goes on across the series to describe the various ways he upgraded the routing and server capacity of the network, which grew to 38 user stations, Samba shares, a membership database, VPN tunnels, several free RJ-45 ports, and “free Wi-Fi access… throughout the park.”
Lots of people have commented on the broad work Finger did to make Linux usable for more people. A few mention that Finger also mentored people, the kind of work that has exponential effects. “MB” wrote on LWN.net that Finger “mentored other people to get the Broadcom Open Source code into kernel. And I think it was a huge success. And that was only a small part of Larry’s success story.”
In a 2023 Quora response to someone asking if someone without “any formal training in computer science” can “contribute something substantial” to Linux, Finger writes, “I think that I have.” Finger links to the stats for the 6.4 kernel, showing 172,346 lines of his code in it, roughly 0.5% of the total.
I have never taken any courses in Computer Science; however, I have considerable experience in coding, much of which happened when computers were a lot less powerful than today, and it was critical to write code that ran efficiently.
Finger suggests in his response small patches, deep reading of the guidelines, and always using git’s send-email to send patches: “Nothing will get shot down more quickly than a patch submitted from a mailer such as Thunderbird.” Finding typos and errors in comments and text strings can help, especially after translation. Finger advises being patient, expecting criticism about following rules and formats, and to keep plugging away at it.
In another Quora response about kernel driver development, Finger says, “This activity can be highly rewarding, and also equally frustrating!” You should learn C, Finger suggested, and maybe start with analyzing USB drivers, and take your time learning about DMA.
“Do not lose hope,” Finger wrote. “It took me about 2 years before I could do anything more than tell the experts where my system was generating a fault.”
Enlarge/ Microsoft’s 11th-edition Surface Pro, as exploded by iFixit. Despite adhesive holding in the screen and the fact that you need to remove the heatsink to get at the battery, it’s still much more repairable than past Surfaces or competing tablets.
For a long time, Microsoft’s Surface hardware was difficult-to-impossible to open and repair, and devices as recent as 2019’s Surface Pro 7 still managed a repairability score of just 1 out of 10 on iFixit’s scale. 2017’s original Surface Laptop needed to be physically sliced apart to access its internals, making it essentially impossible to try to fix the machine without destroying it.
Now, iFixit has torn apart the most recent Snapdragon X-powered Surface Pro and Surface Laptop devices and has mostly high praise for both devices in its preliminary teardown video. Both devices earn an 8 out of 10 on iFixit’s repairability scale, thanks to Microsoft’s first-party service manuals, the relative ease with which both devices can be opened, and clearly labeled internal components.
Beneath the Surface
To open the Surface Laptop, iFixit says you only need to undo four screws, hidden beneath the laptop’s rubber feet; at that point, the bottom of the machine is only attached by magnets, rather than breakable retention clips. Opening the bottom of the laptop provides easy access to the battery and an M.2 2232 SSD. Labels inside the device indicate which screws need to be removed to replace which parts, and what kind of screwdriver you’ll need to do the job; scannable barcodes also make it easier to find repair manuals and parts on Microsoft’s site. Most other parts are easy to remove and replace once the bottom of the laptop is off.
The Surface Pro’s best repairability feature remains its easily accessible M.2 2232 SSD, present under a pop-off cover on the back of the tablet. From there, things get more difficult—accessing the battery and other components requires removing the screen, which is still held in place with adhesive rather than screws or magnets. This adhesive needs to be removed—iFixit cut it away with a thin plastic tool, and closing the tablet back up securely would likely require new adhesive to be applied. Once inside, the parts and screws are still labeled clearly, but you do need to remove the entire heatsink before you can replace the battery.
iFixit uses slightly different criteria for evaluating the repairability of laptops and tablets since tablets are more tightly integrated devices. So despite the identical repairability scores, the Surface Pro remains slightly more difficult to open and fix than the laptop; iFixit is just comparing it to devices like the iPad Air and Pro rather than other PC laptops, and the Surface Pro still looks better than other tablets by comparison despite the use of adhesive.
The teardown video didn’t detail exactly why iFixit knocked points off of each device’s repairability score, though iFixit took note of the soldered-down non-upgradeable RAM and Wi-Fi/Bluetooth modules. Both devices also use way more screws and clips than something like the Framework Laptop, which could also be a factor.
We’ve been using the new Snapdragon-powered Surface devices for a few days now, and we’ll have more thoughts to share about the hardware and its performance in the coming days.
The Pocket 386, a new-old laptop that can run MS-DOS, Windows 3.x, and (technically) Windows 95.
DZT’s Store
The Pocket 386 isn’t sleek, but it’s a lot smaller than an actual 386 laptop would be.
DZT’s Store
The system in clear, plus the included dongles for adding external ports.
DZT’s store
Of the many oddities you can buy from Aliexpress, some of the weirdest are the recreations of retro computer systems in semi-modern designs. We’re most intimately familiar with the Book 8088, a recreation of the original 1981 IBM PC inside a chunky clamshell laptop. The people behind the Book 8088 are also responsible for the Hand386, which is a bit like a late-80s PC stuck inside an old Palm Pilot or Blackberry, and a second revision of the Book 8088 with more built-in ports and a VGA-capable graphics adapter installed instead of a basic CGA adapter.
Whoever is selling these systems is now back with the Pocket 386, which combines Hand386-style internals with a clamshell design similar to the Book 8088. The result is the kind of IBM-compatible system that would have been common during the Windows 3.1 era, when MS-DOS still dominated (especially for games) but Windows was on the upswing.
The heart of the laptop isn’t a genuine retro 386 but an Ali M6117 embedded processor. This is a newer chip that integrates a 40 MHz 80386SX CPU core along with an ALi M1217B chipset. The system also includes 8MB of RAM, one of three different replaceable VGA adapters (either a Cirrus Logic CL-GD542X, a TVGA9000i, or a CHIPS F655x5), a Yamaha OPL3 sound card, an 800×480 IPS display panel, a 4,000 mAh battery, and a CompactFlash slot for storage. There’s no built-in trackpad, though the arrow keys can be used to simulate a mouse. The system also includes a USB port, though as with the Book 8088, it may be usable for mass storage but not for typical USB accessories.
Enlarge/ The Pocket 386 supports standard ports like PS/2 and VGA via a number of custom ports and external dongles.
DZT’s Store
For accessories, the laptop includes a few ports on the back that can be attached to external dongles; included dongles can be used to add PS/2, VGA, parallel, and serial ports to the system. The Pocket 386 is available in both a semi-translucent black finish and a clear finish, and though its normal list price is $300, it’s currently listed for $187. An adapter for adding external ISA expansion cards is sold separately.
This system could technically run Windows 95, and the seller will send you a working Windows 95 disk image (in the GHO format used by the ancient Norton Ghost backup and restore software, so you’ll need to figure that out). The Pocket 386 is just over the minimum requirements for Windows 95, which wanted a 20 MHz 386DX processor or better and at least 4MB of RAM. But even running off of a CompactFlash card instead of an ancient spinning HDD, expect Windows 95 support to be slow at best, particularly because of the technically inferior 386SX processor and the still-pretty-scanty 8MB of memory.
This system will work best if you stick to Windows 3.x and MS-DOS, though the extra CPU speed and RAM will make it infinitely more useful for retro apps and games than the Book 8088 running the same MS-DOS and early Windows software.
Often times, when I am researching something about computers or coding that has been around a very long while, I will come across a document on a university website that tells me more about that thing than any Wikipedia page or archive ever could.
It’s usually a PDF, though sometimes a plaintext file, on a .edu subdirectory that starts with a username preceded by a tilde (~) character. This is typically a document that a professor, faced with the same questions semester after semester, has put together to save the most time possible and get back to their work. I recently found such a document inside Princeton University’s astrophysics department: “An Introduction to the X Window System,” written by Robert Lupton.
X Window System, which turned 40 years old earlier this week, was something you had to know how to use to work with space-facing instruments back in the early 1980s, when VT100s, VAX-11/750s, and Sun Microsystems boxes would share space at college computer labs. As the member of the AstroPhysical Sciences Department at Princeton who knew the most about computers back then, it fell to Lupton to fix things and take questions.
“I first wrote X10r4 server code, which eventually became X11,” Lupton said in a phone interview. “Anything that needed graphics code, where you’d want a button or some kind of display for something, that was X… People would probably bug me when I was trying to get work done down in the basement, so I probably wrote this for that reason.”
Getty Images
Where X came from (after W)
Robert W. Scheifler and Jim Gettys at MIT spent “the last couple weeks writing a window system for the VS100” back in 1984. As part of Project Athena‘s goals to create campus-wide computing with distributed resources and multiple hardware platforms, X fit the bill, being independent of platforms and vendors and able to call on remote resources. Scheifler “stole a fair amount of code from W,” made its interface asynchronous and thereby much faster, and “called it X” (back when that was still a cool thing to do).
That kind of cross-platform compatibility made X work for Princeton, and thereby Lupton. He notes in his guide that X provides “tools not rules,” which allows for “a very large number of confusing guises.” After explaining the three-part nature of X—the server, the clients, and the window manager—he goes on to provide some tips:
Modifier keys are key to X; “this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive.”
“To start X, type xinit; do not type X unless you have defined an alias. X by itself starts the server but no clients, resulting in an empty screen.”
“All programmes running under X are equal, but one, the window manager, is more equal.”
Using the “--zaphod” flag prevents a mouse from going into a screen you can’t see; “Someone should be able to explain the etymology to you” (link mine).
“If you say kill 5 -9 12345 you will be sorry as the console will appear hopelessly confused. Return to your other terminal, say kbd mode -a, and make a note not to use -9 without due reason.”
I asked Lupton, whom I caught on the last day before he headed to Chile to help with a very big telescope, how he felt about X, 40 years later. Why had it survived?
“It worked, at least relative to the other options we had,” Lupton said. He noted that Princeton’s systems were not “heavily networked in those days,” such that the network traffic issues some had with X weren’t an issue then. “People weren’t expecting a lot of GUIs, either; they were expecting command lines, maybe a few buttons… it was the most portable version of a window system, running on both a VAX and the Suns at the time… it wasn’t bad.”
Enlarge/ Features like Image Playground won’t arrive in Europe at the same time as other regions.
Apple
Three major features in iOS 18 and macOS Sequoia will not be available to European users this fall, Apple says. They include iPhone screen mirroring on the Mac, SharePlay screen sharing, and the entire Apple Intelligence suite of generative AI features.
In a statement sent to Financial Times, The Verge, and others, Apple says this decision is related to the European Union’s Digital Markets Act (DMA). Here’s the full statement, which was attributed to Apple spokesperson Fred Sainz:
Two weeks ago, Apple unveiled hundreds of new features that we are excited to bring to our users around the world. We are highly motivated to make these technologies accessible to all users. However, due to the regulatory uncertainties brought about by the Digital Markets Act (DMA), we do not believe that we will be able to roll out three of these features — iPhone Mirroring, SharePlay Screen Sharing enhancements, and Apple Intelligence — to our EU users this year.
Specifically, we are concerned that the interoperability requirements of the DMA could force us to compromise the integrity of our products in ways that risk user privacy and data security. We are committed to collaborating with the European Commission in an attempt to find a solution that would enable us to deliver these features to our EU customers without compromising their safety.
It is unclear from Apple’s statement precisely which aspects of the DMA may have led to this decision. It could be that Apple is concerned that it would be required to give competitors like Microsoft or Google access to user data collected for Apple Intelligence features and beyond, but we’re not sure.
This is not the first recent and major divergence between functionality and features for Apple devices in the EU versus other regions. Because of EU regulations, Apple opened up iOS to third-party app stores in Europe, but not in other regions. However, critics argued its compliance with that requirement was lukewarm at best, as it came with a set of restrictions and changes to how app developers could monetize their apps on the platform should they use those other storefronts.
While Apple says in the statement it’s open to finding a solution, no timeline is given. All we know is that the features won’t be available on devices in the EU this year. They’re expected to launch in other regions in the fall.
Microsoft is all-in on its Copilot+ PC push right now, but the fact is that they’ll be an extremely small minority among the PC install base for the foreseeable future. The program’s stringent hardware requirements—16GB of RAM, at least 256GB of storage, and a fast neural processing unit (NPU)—disqualify all but new PCs, keeping features like Recall from running on all current Windows 11 PCs.
But the Copilot chatbot remains supported on all Windows 11 PCs (and most Windows 10 PCs), and a change Microsoft has made to recent Windows 11 Insider Preview builds is actually making the feature less useful and accessible than it is in the current publicly available versions of Windows. Copilot is being changed from a persistent sidebar into an app window that can be resized, minimized, and pinned and unpinned from the taskbar, just like any other app. But at least as of this writing, this version of Copilot can no longer adjust Windows’ settings, and it’s no longer possible to call it up with the Windows+C keyboard shortcut. Only newer keyboards with the dedicated Copilot key will have an easy built-in keyboard shortcut for summoning Copilot.
If Microsoft keeps these changes intact, they’ll hit Windows 11 PCs when the 24H2 update is released to the general public later this year; the changes are already present on Copilot+ PCs, which are running a version of Window 11 24H2 out of the box.
Changing how Copilot works is all well and good—despite how quickly Microsoft has pushed it out to every Windows PC in existence, it has been labeled a “preview” up until the 24H2 update, and some amount of change is to be expected. But discontinuing the just-introduced Win+C keyboard shortcut to launch Copilot feels pointless, especially since the Win+C shortcut isn’t being reassigned.
The Copilot assistant exists on the taskbar, so it’s not as though it’s difficult to access, but the feature is apparently important enough to merit the first major change to Windows keyboards in three decades. Surely it also justifies retaining a keyboard shortcut for the vast majority of PC keyboards without a dedicated Copilot key.
People who want to continue to use Win+C as a launch key for Copilot can do so with custom keyboard remappers like Microsoft’s own Keyboard Manager PowerToy. Simply set Win+C as a shortcut for the obscure Win+Shift+F23 shortcut that the hardware Copilot key is already mapped to and you’ll be back in business.
Win+C has a complicated history
Enlarge/ Win+C always seems to get associated with transient, unsuccessful Windows features like Charms and Cortana.
Andrew Cunningham
The Win+C keyboard shortcut actually has a bit of a checkered history, having been reassigned over the years to multiple less-than-successful Windows initiatives. In Windows 8, it made its debut as a shortcut for the “Charms” menu, part of the operating system’s tablet-oriented user interface that was designed to partially replace the old Start menu. But Windows 10 retreated from this new tablet UI, and the Charms bar was discontinued.
In Windows 10, Win+C was assigned to the Cortana voice assistant instead, Microsoft’s contribution to the early-2010s voice assistant boom kicked off by Apple’s Siri and refined by competitors like Amazon’s Alexa. But Cortana, like the Charms bar, never really took off, and Microsoft switched the voice assistant off in 2023 after a few years of steadily deprioritizing it in Windows 10 (and mostly hiding it in Windows 11).
Most older versions of Windows didn’t do anything with the Win+C, but if you go all the way back to the Windows 95 era, users of Microsoft Natural Keyboards who installed Microsoft’s IntelliType software could use Win+C to open the Control Panel. This shortcut apparently never made it into Windows itself, even as the Windows key became standard equipment on PCs in the late ’90s and early 2000s.
So pour one out for Win+C, the keyboard shortcut that is always trying to do something new and not quite catching on. We can’t wait to see what it does next.
The Biden administration will ban all sales of Kaspersky antivirus software in the US starting in July, according to reporting from Reuters and a filing from the US Department of Commerce (PDF).
The US believes that security software made by Moscow-based Kaspersky Lab represents a national security risk and that the Russian government could use Kaspersky’s software to install malware, block other security updates, and “collect and weaponize the personal information of Americans,” said US Commerce Secretary Gina Raimondo.
“When you think about national security, you may think about guns and tanks and missiles,” said Raimondo during a press briefing, as reported by Wired. “But the truth is, increasingly, it’s about technology, and it’s about dual-use technology, and it’s about data.”
US businesses and consumers will be blocked from buying new software from Kaspersky starting on or around July 24, 2024, 30 days after the restrictions are scheduled to be published in the federal register. Current users will still be able to download the software, resell it, and download new updates for 100 days, which Reuters says will give affected users and businesses time to find replacement software. Rebranded products that use Kaspersky’s software will also be affected.
Companies that continue to sell Kaspersky’s software in the US after the ban goes into effect could be subject to fines.
The ban follows a two-year national security probe of Kaspersky’s antivirus software by the Department of Commerce. It’s being implemented using authority that the government says it was given under a national defense authorization act signed during the Trump administration in 2018.
The ban is the culmination of long-running concern across multiple presidential administrations. Kaspersky’s software was banned from systems at US government agencies following allegations of the company’s links to Russian intelligence operations. A month after Russia began its invasion of Ukraine in early 2022, the US Federal Communications Commission went one step further, adding Kaspersky to a security threat list that included Chinese hardware makers Huawei and ZTE. Adding Kaspersky to that list didn’t ban consumer sales, but it did prevent Kaspersky from receiving funding from the FCC.
For its part, Kaspersky and its representatives have always denied the US government’s allegations. CEO Eugene Kaspersky called the 2017 reports “BS brewed on [a] political agenda,” and the company similarly accused the FCC in 2022 of making decisions “on political grounds” and “not based on any technical assessment of Kaspersky products.”
