fidzu : computers

A large Swedish study of 100,000 women found that using AI to assist radiologists reading mammograms reduced the rate of aggressive "interval" breast cancers by 12%. CBC News reports: For the study -- published in Thursday's issue of the medical journal The Lancet -- more than 100,000 women had mammography screenings. Half were supported by AI and the rest had their mammograms reviewed by two different radiologists, a standard practice in much of Europe known as double reading. It is not typically used in Canada, where usually one radiologist checks mammograms. The study looked at the rates of interval cancer, the term doctors use for invasive tumors that appear between routine mammograms. They can be harder to detect and studies have shown that they are more likely to be aggressive with a poorer prognosis. The rate of interval cancers decreased by 12 percent in the groups where the AI screening was implemented, the study showed. [...] Throughout the two-year study, the mammograms that were supported by AI were triaged into two different groups. Those that were determined to be low risk needed only one radiologist to examine them, while those that were considered high risk required two. The researchers reported that numerically, the AI-supported screening resulted in 11 fewer interval cancers than standard screening (82 versus 93, or 12 per cent). "This is really a way to improve an overall screening test," [said lead author, Dr. Kristina Lang]. She acknowledged that while the study found a decrease in interval cancer, longer-term studies are needed to find out how AI-supported screening might impact mortality rates. The screenings for the study all took place at one centre in Sweden, which the researchers acknowledged is a limitation. Another is that the race and ethnicity of the participants were not recorded. The next step, Lang said, will be for Swedish researchers to determine cost-effectiveness.

Read more of this story at Slashdot.

30 Jan 2026 7:00am GMT

An anonymous reader quotes a report from the Guardian: The UK could introduce a universal basic income (UBI) to protect workers in industries that are being disrupted by AI, the investment minister Jason Stockwood has said. "Bumpy" changes to society caused by the introduction of the technology would mean there would have to be "some sort of concessionary arrangement with jobs that go immediately", Lord Stockwood said. The Labour peer told the Financial Times: "Undoubtedly we're going to have to think really carefully about how we soft-land those industries that go away, so some sort of [universal basic income], some sort of lifelong mechanism as well so people can retrain." A universal basic income is not part of official government policy, but when asked whether people in government were considering the need for UBI, Stockwood told the FT: "People are definitely talking about it." [...] While he has previously been a vocal proponent of a wealth tax in the UK, Stockwood told the FT he had not repeated his calls for the government to go further on taxing the rich. However, he added: "If you make your money and the first thing you do is you speak to a tax adviser to ask: 'Where can we pay the lowest tax?' we don't want those people in this country, I'd suggest, because you're not committed to your communities and the long-term success in this country."

Read more of this story at Slashdot.

30 Jan 2026 3:30am GMT

Comcast's attempt to slow broadband customer losses still isn't stopping the bleeding as fiber and fixed wireless competition intensifies. In Q4 2025 alone, Comcast lost 181,000 broadband subscribers, even as it leans harder into wireless bundling and other business lines like Peacock and theme parks. Ars Technica reports: The Q4 net loss is more than the 176,000 loss predicted by analysts, although not as bad as the 199,000-customer loss that spurred [Comcast President Mike Cavanagh's] comment about Comcast "not winning in the marketplace" nine months ago. The Q4 2025 loss reported today is also worse than the 139,000-customer loss in Q4 2024 and the 34,000-customer loss in Q4 2023. "Subscriber losses were 181,000, as the early traction we are seeing from our new initiatives was more than offset by continued competitive intensity," Comcast CFO Jason Armstrong said during an earnings call today, according to a Motley Fool transcript. Comcast's residential broadband customers dropped to 28.72 million, while business broadband customers dropped to 2.54 million, for a total of 31.26 million. Armstrong said that average revenue per user grew 1.1 percent, "consistent with the deceleration that we had previewed reflecting our new go-to-market pricing, including lower everyday pricing and strong adoption of free wireless lines." Armstrong expects average revenue per user to continue growing slowly "for the next couple of quarters, driven by the absence of a rate increase, the impact from free wireless lines, and the ongoing migration of our base to simplified pricing." Comcast Connectivity & Platforms chief Steve Croney said the firm is facing "a more competitive environment from fiber" and continued competition from fixed wireless. "The market is going to remain intensely competitive," he said.

Read more of this story at Slashdot.

30 Jan 2026 2:02am GMT

As most of you will know, Mac OS X (or Rhapsody if you count the developer releases) wasn't Apple's first foray into the world of UNIX. The company sold its own UNIX variant, A/UX, from 1988 to 1995, which combined a System V-based UNIX with a System 7.0.1 desktop environment and application compatibility, before it acquired NeXT and started working on Rhapsody/Mac OS X. As a sidenote, I don't know if the application compatibility layer was related to the Macintosh Application Environment for UNIX, which I have running on my HP-UX machines. That's not the only time Apple dabbled with UNIX, though - Apple's unique Apple Network Server product from 1996 also came with UNIX, but time it wasn't one from Apple itself, but rather from its enemy-turned-friend IBM: AIX. The Network Server shipped with a slightly customised version of IBM's AIX operating system; regular AIX straight from IBM wouldn't work. The more things change, the more they stay the same I guess. Since the Apple Network Server was built around a modified Power Macintosh 9500 - there's much more to the hardware, but that's the short of it - so you would expect the Network Server to also be able to run regular Mac OS for PowerPC, right? Apple even sold server products running plain Mac OS at the time, so it'd make sense, but nothing about Apple in the '90s made any sense whatsoever, so no, use of plain Mac OS was locked out through the ROM. And let's not even get started about other PowerPC operating systems of the time, like, of all things, Windows NT - something Apple supposedly demonstrated at some point. But was that always the case? Well, we've got new ROMs straight from a former Apple employee, and after flashing them to a supported ROM chip, the Apple Network Sever can now run classic Mac OS. On top of that, and even more miraculous, the Windows NT-capable ROMs have also been discovered. I'll give you a spoiler now: it turns out the NT ROM isn't enough to install Windows NT by itself, even though it has some interesting attributes. Sadly this was not unexpected. But the pre-production ROM does work to boot Mac OS, albeit with apparent bugs and an injection of extra hardware. Let's get the 700 running again (call it a Refurb Weekend) and show the process. ↫ Cameron Kaiser While it's great news to see that Mac OS can now be run on the Network Server, I'm personally much more interested in the story behind the Windows NT ROMs. The idea that Apple would sell a computer running Windows NT out of the box is wild to think about now, but considering the desperate state the company was in at the time, all options must've been on the table. Sadly, as Kaiser discovered, the Windows NT ROMs in and of themselves are not enough to run Windows NT. However, they appear to be much farther along in the development process than even the Mac OS-capable ROMs, which is fascinating. When Jobs talked Gil Amelio into canning the ANS as well, the ROM initiative naturally went out the window with it. However, while the existing 2.0 Mac OS ROMs are only known on an unmarked development flash stick similar to mine, these final 2.26NT ROMs appear almost production-ready with fully printed labels, suggesting they had reached a very late stage of development. ↫ Cameron Kaiser Despite not being able to boot Windows NT for PowerPC as-is, most likely because there's no compatible ARC or HAL, Kaiser did discover a ton of interesting details, like how this ROM configures the Network Server to run in little endian mode, which is all Windows NT for PowerPC ever supported, making this the very first time a PowerPC machine did so. I'm hoping Kaiser manages to track down the necessary components to make Windows NT bootable on the ANS, as one of the most unique curiosities in Apple history. There's a ton more details in the article, as per usual Kaiser standards, and it's an absolute joy to read.

29 Jan 2026 11:50pm GMT

With ACA tax credits gone, more people are turning to high-deductible plans.

29 Jan 2026 11:22pm GMT

The JUMPSEAT satellites loitered over the North Pole to spy on the Soviet Union.

29 Jan 2026 11:07pm GMT

Windows 11 clears a milestone as Windows 10 continues its slow fade.

29 Jan 2026 10:46pm GMT

While the two major open source desktop environments get most of the airtime - and for good reason, since they're both exceptionally good - there's a long tail of other desktop environments out there catering to all kinds of special workflows and weird niches. I think we can all agree that Xfce leads this long tail of more niche desktop environments, without really being niche itself. Xfce may not be as popular as KDE or GNOME, but it's an amazing full-featured desktop environment that offers a slightly more traditional, less fast-paced desktop for those that desire so. Xfce, too, is moving to Wayland, which can mean significant efforts in certain places, not the least of which is the window manager. Xfce originally planned to adapt its venerable xfwm4 to support both X11 and Wayland at the same time, but this turned out to be too complex for a variety of reasons, all more or less caused by differences between X11 and Wayland. On top of that, this approach would risk introducing new bugs to the X11 side of things, and the Xfce project does not want to subject its X11 users to that. As such, they've decided to develop a Wayland compositor from scratch: xfwl4. The goal is, that xfwl4 will offer the same functionality and behavior as xfwm4 does, or as much as possible considering the differences between X11 and Wayland. Using xfwl4 should feel just like using xfwm4 on X11. We even plan to reuse the existing xfwm4 configuration dialogs and xfconf settings to ensure a seamless transition. Xfwl4 will not be based on the existing xfwm4 code. Instead, it will be written from scratch in rust, using smithay building blocks. ↫ The Xfce development team This project also includes related tasks like rearchitecting session-startup to support Wayland, implementing support for the xdg-session-management protocol, and adding support for XWayland. This is obviously anything but a small effort, but it seems like a practical solution. Xfce users generally seem to choose Xfce exactly because it's a stable environment that does not move fast(er) and break (some) things. As such, keeping the X11 window manager separate and stable, without Wayland work possibly breaking it, seems like the kind of thing the average Xfce user can get behind. Personally, I can't wait for Xfce to become a full Wayland desktop, as dealing with X11's nonsense feels decidedly retro to me now, and I don't see Xfce as a retro environment at all. It's going to take some time, of course, but thanks to countless generous donations to Xfce, longtime Xfce core developer Brian Tarricone will be paid to work on this project. Excellent news for everyone involved.

29 Jan 2026 10:17am GMT

Since I have no qualms about kicking a proprietary software product while it's down, let's now switch to NTDEV's thoughts on the state of Windows 11. Unfortunately, the issue that plagued Windows since the dawn of time has only aggravated recently. Windows 11 is a mixture of old and new technologies that are glued together, with decades of legacy code that simply refuses to die (because if it did a lot of corporate costumers would complain, and whether we like it or not they are paying big cash for support to Microsoft). Also, it tries to have a "modern" UI that unfortunately not only is inconsistent, but also it's too heavy for its own good, being just a lipstick on a bloated old pig. Last, but certainly not least, it is full of AI features that most people didn't ask for, some are even actively feared (see Recall) and are also quite lacking in polish and usefulness. Until Microsoft stops treating Windows as an "AI innovation platform" of sorts and starts treating it as the stable, reliable tool it was always meant to be, the user experience will continue to feel like a battle between the person sitting at the desk and the company that built the desk. ↫ NETDEV When even some of the most knowledgeable and respected Windows/Windows NT developers and experts are this down on the current state of Windows, you know things are way worse than we even know from just following the news and our own experiences. Back in 2024, I stated that I firmly believe we will see Windows - or at least, huge, crucial chunks of it - shift to an open source development model, as it's the only way for Windows to move forward without crumbling into itself. It would also be a massive cost-cutting and personnel-culling step for Microsoft, something that seems to become ever more relevant now that the company bet massively on "AI", without any of it paying off. They're going to need to do some serious cost-cutting once the "AI" bubble bursts, and Windows will definitely be the first on the chopping block. As a side note, the step to release Windows as open source won't be nearly as difficult or problematic as people think. In fact, Microsoft has provided access to the source code behind Windows and various other products for decades, and countless governments and organisations have access to said source code. On top of that, the source code to Windows XP and Server 2003 is out there, hosted on GitHub, and various other leaks have occurred as well over the years. While I'm sure a large clean-up effort would still be required, and while it surely will be a big engineering effort, if there were any truly shocking things in the code Microsoft wouldn't want the world to see we'd already know by now. I'm getting the strong feeling Microsoft is trying to squeeze every last drop of revenue out of Windows before it ends up on the chopping block. Windows will definitely not be axed, but cost-cutting is inevitable.

28 Jan 2026 8:51pm GMT

While starting this post I realized I have been maintaining personal infrastructure for over a decade! Most of the things I've self-hosted is been for personal uses. Email server, a blog, an IRC server, image hosting, RSS reader and so on. All of these things has all been a bit all over the place and never properly streamlined. Some has been in containers, some has just been flat files with a nginx service in front and some has been a random installed Debian package from somewhere I just forgot.

19 Jan 2026 12:00am GMT

In the recent blog post on the work funded by Sovereign Tech Fund (STF), we provided an overview of the "File Hierarchy for the Verification of OS Artifacts" (VOA) and the voa project as its reference implementation. VOA is a generic framework for verifying any kind of distribution artifacts (i.e. files) using arbitrary signature verification technologies. The voa CLI ⌨️ The voa project offers the voa(1) command line interface (CLI) which makes use of the voa(5) configuration file format for technology backends. It is recommended to read the respective man pages to get …

11 Jan 2026 12:00am GMT

In 2024 the Sovereign Tech Fund (STF) started funding work on the ALPM project, which provides a Rust-based framework for Arch Linux Package Management. Refer to the project's FAQ and mission statement to learn more about the relation to the tooling currently in use on Arch Linux. The funding has now concluded, but over the time of 15 months allowed us to create various tools and integrations that we will highlight in the following sections. We have worked on six milestones with focus on various aspects of the package management ecosystem, ranging from formalizing, parsing and writing of …

10 Jan 2026 12:00am GMT