17 Nov 2026
Slashdot
'123456' Has Been the World's Most Popular Password for 7 of the Last 8 Years
"123456" is once again the world's most commonly used password, topping NordPass's annual ranking for the seventh time in eight years. The Register reports: Even when 123456 wasn't number one, it was still near the top of the heap, as the top three passwords in the list remain unchanged in the eight years NordPass has published its list: 123456, admin, and 12345678. It's not like the rest of the most common passwords are showing any variety either. According to NordPass, the only real shuffling among the 10 most popular passwords was the entry of the worryingly short 1234 into the top ten and the migration of the ever-popular password "password" down slightly in the top 10 from 6th to 7th place.
Read more of this story at Slashdot.
17 Nov 2026 11:00am GMT
California Sues OpenAI Over Hugging Face, Other AI Model Loss of Control
"California's attorney general just sued OpenAI," writes longtime Slashdot reader destinyland. "The action accuses OpenAI of putting public safety at risk, reports CNBC, specifically by its past failures to contain its AI models within their testing environments." From the report: [California Attorney General Rob Bonta] cited the "infamous" incident in July, where two OpenAI models broke out of a testing environment, gained unauthorized access to the open internet, and breached the internal systems of open-source developer platform Hugging Face. OpenAI said the models were trying to find information that they could use to cheat on an evaluation, and succeeded. The break-in at Hugging Face, which Nvidia acquired for roughly $13 billion in September, rattled industry researchers and prompted government officials to call for more stringent oversight of the AI industry. On Monday, Bonta said that OpenAI later disclosed to his investigators that it was aware of 80 incidents "involving loss of control and access to third-party networks and websites." "But the company failed to provide the detailed information we requested to evaluate these incidents; this is concerning, and it puts the public at risk," he said. Bonta's suit, filed in state Superior Court in San Francisco, alleges OpenAI violated California's Unfair Competition Law and accuses the company of being a public nuisance as defined by state law. The attorney general told reporters he believed in AI's technological power, and the potential of AI models to "achieve scientific breakthroughs, boost economic growth, guard against cyber attacks, and benefit all Californians." "But AI systems must be developed and designed safely," he said. "The companies that develop these models have a moral and yes, a legal responsibility to keep public safety at the forefront." The lawsuit can be found here (PDF).
Read more of this story at Slashdot.
17 Nov 2026 7:00am GMT
Just 400 US Data Centers Use More Electricity Than Michigan
An anonymous reader quotes a report from Wired: Just 400 hyperscale data centers connected in the US used as much electricity as the state of Michigan in a single year, new Harvard research has found. The study, published Monday in Nature Sustainability, also finds that the majority of that electricity was generated using fossil fuels, and data center emissions are three times higher than they were before the AI boom. Federal and state governments do not track data center use separate from the rest of the power sector, despite mounting projections that data centers are putting serious strain on the American power grid. Individual data centers' power use is often considered proprietary business information, and data center operators and utilities do not have to disclose specific numbers to the public. The Harvard study specifically focuses on hyperscale data centers -- the largest types of facilities, which have become flashpoints in community opposition across the country. While often used for AI inference or training, not all of the hyperscalers surveyed in this study are being used for AI. [...] To assemble their dataset, the Harvard researchers put together a list of 403 hyperscale data centers around the country that were operational between May 2024 and April 2025 using a mix of industry research and satellite data. The team then modeled these facilities' energy use in a variety of scenarios and calculated the energy mix of the regional grids to estimate individual facilities' carbon emissions. Not all regions were created equal: Data centers in Virginia, Oregon, Ohio, and Iowa -- the first of which is home to Data Center Alley -- were responsible for more than 50 percent of the energy use in the study. The report notes that these findings may already be outdated. "Some of the massive campuses being proposed today are substantially larger than the typical facility in our dataset," says Gianluca Guidi, a postdoctoral research fellow at Harvard's T. H. Chan School of Public Health and the lead author of the study. The study also excludes onsite power generation, a rapidly growing trend that BloombergNEF estimates could increase overall U.S. emissions by 10% if all proposed projects are built.
Read more of this story at Slashdot.
17 Nov 2026 3:30am GMT
16 Nov 2026
OSnews
Finally, a truly premium Linux laptop: Star Labs’ StarFighter Ultra
Many popular Linux laptops are not designed from the ground-up for Linux. Often, they are machines designed and assembled by companies like Clevo, with parts and options picked by the Linux OEM to optimise them for Linux to make sure the hardware is optimally compatible. While there's nothing wrong with this approach - there are countless great Linux laptops available that are made this way - there's also something to be said for starting with a blank slate, and designing, developing, building, and assembling a Linux laptop entirely from scratch. One such laptop is Star Labs' brand new StarFighter, which I've been using and testing over the last little while since it was launched. The StarFighter is an entirely custom powerhouse of a laptop, designed exclusively for Linux, both inside and out. Let's talk about what it's like to use the StarFighter, and if it's worth considering when looking for a new laptop. The hardware The Starfighter comes in three flavours: Standard, Ultra, and AMD. I opted for the Ultra model, which comes with an Intel Core Ultra 9 285H, an Intel Arc 140T integrated GPU, 64GB of LPDDR5X RAM, and a 16″ 3840×2400 120Hz matte display. The standard model steps these specs down to an Intel Core Ultra 5 125H, 32GB of LPDDR5X RAM, and a 16″ 2560×1600 165Hz display, while the AMD model maintains the specifications of the Ultra, but with an AMD Ryzen 7 8845HS processor paired with a Radeon 780M integrated GPU. All three models share the same Intel AX210 Wi-Fi 6E chip, soldered RAM, and port configuration: 2 USB-C ports (Thunderbolt 4 on the Intel models), 3 USB-A ports, an HDMI 2.0 port, a microSD reader, a combined audio jack, and two PCIe Gen 4 NVMe slots on the motherboard. All three models run coreboot firmware, and come with a hardware kill switch for the wireless radios. Another really interesting security and privacy feature is how the Starfighter handles its webcam. Instead of being integrated into the display bezel, the webcam is a separate module that snaps onto the display lid magnetically, connecting through a few pogo pins (which form a USB 2.0 port, which I'm sure intrepid hardware hackers could do fun stuff with). When not in use, the webcam module is stored in its own little metal tray that slides out of the side of the laptop, securing itself in place magnetically. Neat. The webcam quality itself is decidedly average. I personally don't ever use a webcam, but if you do, don't expect miracles. It does its job, no more, no less. The StarFighter has a custom chassis made out of magnesium, with the only plastic part of the casing being the display inner hinge cover where I assume the antennas are integrated. It's an incredibly sturdy device, with very little flex in the display cover, and zero flex in the keyboard deck. Thanks to the properties of magnesium, it's quite lightweight at a mere 1.6kg. The bottom cover is easily removable, but the two screws in the middle of that cover are ever so slightly longer than all the other screws - ask me how I know. Star Labs opted for an understated, unobtrusive design. There's no weird flourishes, no garish RGB lighting, no childish font on the keyboard - it's all business, and I really like that. The dark finish feels incredibly nice, and despite the colour doesn't seem to catch too many fingerprints. The speaker grills next to the keyboard look nice too, as does the keyboard itself - I especially appreciate that the the various modifier and non-character keys use text labels instead of symbols. Of course, since this is a Linux laptop, the super key is properly labelled. No Windows logo here, but no silly penguin either. The keyboard is backlit, of course, with several light levels, with a keyboard backlight timeout adjustable in coreboot. Using it The feel of the keyboard could use some work, however, at least for me. In particular, the key stability feels a bit off to me, meaning that unless you strike a key right in the middle, it might not register properly, as the keys wobble more than I would expect. A workaround, of sorts, is to strike the keys a bit harder than you normally would, but I've found this to be more difficult to adapt to than I initially expected. That being said, if you already have a more solid strike, it's possible you won't notice anything wrong with the keyboard at all. The trackpad, though, is basically perfect. Star Labs pulled out all the stops here, and went for a large haptic trackpad that feels absolutely incredible. I greatly prefer haptic trackpads, and have been puzzled for years now why Linux laptop OEMs continue to opt for wobbly diving board-style trackpads instead. It has a glass surface which hits the perfect middle-ground between smooth and textured, and it never seems to pick up any smudges or grease. Several of the parameters of the haptic trackpad can be configured in coreboot and supposedly from within Linux itself, but I haven't figured that part out yet as the patches for it were only accepted very recently. It is the perfect trackpad. Zero complaints. Every single click, every single gesture, every single swoosh feels perfect. I don't like being this ecstatic about something - there's usually flaws in everything - but it's really just that good. While testing the StarFighter, I used some other laptops with the old diving board design, and they're all ruined for me now. I'm usually a fan of smaller laptops, with 14″ being my upper bound. However, laptops have gotten so light, and bezels so thin, that the 16″ of today is the 14″ of several years ago - not exactly, but you get my point. I definitely had to get used to this larger laptop, but now that I have acclimatised, having 3840×2400 pixels spread out across a 16″ canvas is honestly kind of amazing. I
16 Nov 2026 9:12pm GMT
Planet Arch Linux
Mutex poisoning is not for everyone
After some recent discussion on the topic of mutex poisoning and notably a blog post that I thought was interesting, thoughtful, exhaustive, yet completely disagreed with, I wanted to comment on the debate myself. To me, poisoning-by-default is one of biggest mistakes that were made in the language, next to some others that are a story for a different time.
16 Nov 2026 12:00am GMT
15 Nov 2026
OSnews
KDE will now load XWayland on demand
When running KDE, the X11 compatibility layer for Wayland, XWayland, always runs, even if there isn't anything on the system still requiring the legacy X server to work. In the next step towards a Wayland-only world, the KDE people have reached a major milestone: XWayland now only runs when actually needed. This week a significant technical milestone was achieved: the XWayland compatibility layer is now loaded only when needed. Previously it had always been running even when no apps were using it, and fixing this required porting various system services away from legacy X11 code paths. This work was done by Vlad Zahorodnii, David Edmundson, and David Redondo, and will ship in Plasma 6.9. ↫ Nate Graham This frees up some system resources, which is always a welcome improvement. I do wonder how this might impact the load times of legacy X applications, but I have a feeling it's close to immeasurable.
15 Nov 2026 11:41pm GMT
Redox gets Go, GIMP, and more
I love and admire the Redox project, but their insistence on fudging the publication dates of their monthly progress reports really bothers me, for some reason. No, I'm not 16 days late - the report covering October was published only yesterday evening, and not on 31 October as the website claims. None of this matters to anyone but weird people such as myself, but I still want to get it off my chest. Don't bother any Redox people about this. Anyway, the big news for the month of October is the port of the official Go programming language compiler, allowing for cross-compilation and self-hosted compilation using relibc. Another major port also made its way to Redox in October: GIMP now runs on Redox, using the Orbital backend of the GTK port. The work to make Redox compatible with Cloud Hypervisor is also complete, with more information in its own dedicated article. Video playback in WebKitGTK3 has been fixed as well, and even YouTube works now which is quite neat. There's a ton more in this report, like an updated Servo port, NUMA support has been tested on real hardware for the first time and seems to work, work on rootless package installation has begun, and much more.
15 Nov 2026 11:31pm GMT
08 Oct 2026
Planet Arch Linux
Writing parsers is hard
This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …
08 Oct 2026 12:00am GMT
09 Aug 2026
Planet Arch Linux
On scripts and hooks
Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …
09 Aug 2026 12:00am GMT