computers

09 Jul 2026

Ars Technica

Free Waymo rides in California? You can thank a regulatory quirk.

State agency's delay could mean free robotaxi rides in company's new Ojai vehicle for a few months.

09 Jul 2026 1:31pm GMT

The newest entrant in the military’s launch competition isn't actually a launch company

"I think it's fair to say that Phase 3 did not contemplate this."

09 Jul 2026 1:08pm GMT

Payloads used to dictate the terms of launch. That's finally changing.

"The Starship Pez dispenser demonstrates very smart industrial design and scale."

09 Jul 2026 11:00am GMT

Meta will build its first Canadian data center in Alberta, investing $9 billion in a 1-gigawatt facility that can scale to 1.8 gigawatts to support its AI infrastructure needs. The project will rely on new generation and grid infrastructure funded by Meta, including a long-term agreement tied to a new natural gas power facility. The company says it will offset electricity use with clean and renewable energy investments. Reuters reports: Meta has doubled down on AI, pledging hundreds of billions of dollars to build large AI data centers in the U.S. The Alberta announcement represents the company's 33rd data center globally. Executives made the announcement in Calgary alongside Premier Danielle Smith and other Alberta government officials, who have spent several years courting Silicon Valley tech giants with the aim of spurring a large-scale investment in the oil-and-gas province. Alberta's technology minister, Nate Glubish, told reporters there are currently several other gigawatt-scale data center proposals in various stages of development in the province. "This is the first of its kind, the first of its size, the first of its scale, but it won't be the last," Glubish said. Meta, like other tech giants, is facing rapidly expanding power needs due to the growth of AI, and Alberta is rich in natural gas which sells at a significant discount to the U.S. benchmark. The province's cold climate also makes cooling the massive super-computers and related data center infrastructure more cost-efficient. The 20 existing small- to mid-scale data centers in Alberta already pull from the province's energy grid, which is 60% powered by natural gas. The provincial government is giving new proponents the option to build their own power sources to avoid limits on power capacity. Meta said Wednesday it will fully fund new generation and grid infrastructure for its Alberta data center, which will consume about as much electricity as 800,000 homes. Gary Demasi, Meta's vice president for data center development, said the company will offset that electricity use by investing in clean and renewable energy. He also said the data center will use a closed-loop liquid cooling system, meaning its total water use will be less than that of a typical golf course. [...] The company has partnered with Alberta-based Pembina Pipeline , which announced last week it will go ahead with its Greenlight Electricity Centre, a new natural gas-fired power-generation facility in Sturgeon County which will be in service in late 2030 and with which Meta has a long-term tolling agreement. Until that project is operational and for the next decade, Alberta-based power producer Capital Power will provide 250 megawatts of electricity for the site using its existing natural gas-fired fleet. The project will require approximately 150 million cubic feet per day of natural gas, according to Pembina, helping to create demand for Western Canadian natural gas producers.

Shoebox-Sized 'Detector Satellites' Could Sniff Out a Nuclear Bomb In Space

A new study proposes using shoebox-sized detector satellites to sniff out nuclear weapons launched by adversary nations. The idea is aimed at addressing fears that a space-based nuclear detonation could destroy satellites across low Earth orbit and make some orbits unusable for years. Space.com shares the findings from a new paper authored by Areg Danagoulian, an associate professor of nuclear science and engineering at the Massachusetts Institute of Technology: No reliable way currently exists to detect and defuse a nuclear bomb in space. Danagoulian proposes a constellation of small "9U" cubesats, each one about the size of a large shoebox and each carrying a special detector capable of sensing radiation emitted by unexploded nuclear bombs. He explores a scenario in which Russia launches a suspected space nuke into an orbit with an altitude of 1,200 miles (2,000 km). That number is not random. In 2022, Russia's Kosmos 2553 satellite, orbiting at that exact altitude, triggered suspicions it might be testing components for a future orbital nuclear weapon. Russia claims the satellite just observes Earth. At that altitude, the satellite passes through the Van Allen belt, a region of intense cosmic radiation trapped by Earth's magnetic field. Most of the belt stretches between altitudes of around 600 miles (1,000 km) to tens of thousands of miles, but in some areas the radiation can reach much closer to Earth's surface. The interaction between the fissile material inside the nuke and the energetic particles from the radiation belt would create distinct signatures, Danagoulian said, which could help confirm whether a suspicious satellite carries a nuke or not. "The thermonuclear weapon would contain a significant amount of uranium," Danagoulian said. "The high-energy protons [in the uranium] would break up when another proton is coming in and shred the nuclei. That would knock out a large number of neutrons. This interaction turns that device into a very intense neutron source that otherwise would not be there." he process is known as proton-induced neutron spallation, which essentially means the ejection of fragments from material triggered by impacts of protons. The detector satellite Danagoulian proposes would have to be able to get quite close to the suspect spacecraft -- a few kilometers. The inspector spacecraft would carry a sensor combining two types of detectors. At the heart of the device is a neutron scintillator, which detects all incoming neutrons and protons. Around it is a "cage of diamond" detector that detects only neutrons -- not protons. Such a set-up helps filter out the particles present in the environment naturally, said Danagoulian. In addition, by using two "planes of neutron detectors," the sensor can determine the direction from which the neutrons arrived. "If the external diamond detector triggers and gives a signal, you can ignore the particle, because it's most likely a proton and not a neutron," said Danagoulian. "Once you identify those neutrons, by having those two detections, you can back project and find out where the neutron came from." Danagoulian says such a nuke sniffer would have to be launched into an orbit aligned with that of the suspicious satellite and creep up as close as 2.5 miles (4 km) from it. It would then take about a week to gather enough measurements to confirm whether the object is hiding a nuke or not. A constellation of 10 such satellites could reduce the process to mere hours, Danagoulian said. If a nuke were detected, the military could then try to jam the satellite's communications link from the ground, making it impossible for the adversary to remotely detonate the bomb. There is currently no technology available to safely defuse a nuclear weapon in space. [...] Danagoulian also suggests that high-grade radiation hardening could improve satellites' chances of surviving a nuclear winter in space. The paper has been published in the journal Nature.

US Food and Drug Administration Rejects Petition To Set PFAS Limits In Food

An anonymous reader quotes a report from The Guardian: The US Food and Drug Administration has rejected a legal petition demanding it set limits on toxic Pfas "forever chemicals" in food, marking another setback for public health advocates' push to limit exposures to the dangerous compounds. The agency is refusing to set limits despite a growing body of science and the Environmental Protection Agency (EPA) finding food is the biggest source of Pfas exposure. Testing has found the levels of Pfas in single servings of some contaminated foods to be equivalent to drinking many glasses of contaminated water. While regulators have focused on reining in Pfas in water, the chemicals are widely used throughout the food system, and there was hope that the agency under Robert F Kennedy Jr would take the threat more seriously. Kennedy leads the "make America healthy again" (Maha) movement, of which eliminating toxic chemicals from food is a cornerstone. [...] The November 2023 petition called on the FDA to check for up to 30 Pfas compounds in a range of produce, fish, eggs, milk and bread. The agency did not respond within the six-month timeframe required by law, but TEJTF scaled back its petition in 2025 to ask the agency to set advisory thresholds for PFOA and Pfos, two of the most common and dangerous Pfas compounds, in seafood and milk. Recent FDA testing found 70% of seafood samples contain the chemicals, while independent milk testing found it in 12% of 50 samples, including extremely high levels in Whole Foods and Kirkland Signature brands. The FDA rejected the revised petition, stating it plans to take action on setting standards for Pfas, and there is "insufficient evidence to support [TEJTF's] request." The agency said it plans to set less non-binding "action levels" that do not require contaminated food to be removed from shelves. "Tolerance levels," or limits, make it illegal to sell food contaminated beyond a set threshold.

08 Jul 2026

OSnews

You paid me, a long-time Linux user, to use Windows 11 exclusively for a month: here’s how it went

You all donated en masse to have me use Windows 11 for a month, and so I did. What was it like for a long-time Linux user to go back and experience Windows as it exists now? Is it really as bad as we've collectively made it out to be? Did my month with Windows 11 consist of nothing but pain and misery, or are there good things to say, too? Or, was it an unexpected pleasant surprise? And ultimately, did I stay with Windows 11, or move back to the Linux world? ➡️ Donate through Ko-Fi ➡️ Donate through SEPA transfer* ➡️ Buy merch from our store ➡️ Why a fundraiser? *Name: Thom Holwerda - IBAN: SE08 8000 0820 1684 4657 8414 - BIC: SWEDSESS This year, I'm celebrating the milestone of having posted 20000 stories on OSNews during my 21 years as managing editor of OSNews. This is my full-time job, and since nobody is going to give me any bonuses, stock options, or golden pens, we're running a big fundraiser to keep OSNews going. To add some spice to the whole thing, I added some incentives, with the first being using Windows 11 for a month. We're slowly but steadily approaching the next incentive, too, which is a proper video tour of my office, (unique) computers, and massive devices collection. There's a similar incentive to this Windows 11 one, but for macOS. Yikes. The rules for the Windows 11 incentive are simple: use stock Windows 11 for a month for my computing tasks (with the exception of gaming - converting my Linux gaming PC to Windows just to play the same games seemed silly). I wasn't allowed to use any debloating tools, but as an EU citizen, I do have the ability to remove a ton of Windows stuff thanks to the success of the Digital Markets Act. I also tried to stick to Microsoft's own applications as much as possible, for that true "ecosystem experience", and wasn't allowed to hack my way into a normal local user account. I was all-in. So what was it like? Setting it all up The installation process posed a number of challenges and issues. First and foremost, the Windows 11 installation process is incredibly barebones, and basically assumes no other operating system exists in the world. It has no clue anything other than Windows' filesystems exist, making it dangerously easy to accidentally damage or outright delete any other operating systems you might have installed. My laptop happens to have two M.2 SSDs in, so I could safely dedicate one of them to Windows 11 without interfering with the other SSD with Fedora installed on it, but if you're experimenting with Windows 11 on your Linux machine with just one drive, you might want to reconsider. I also had to perform the first portion of the installation process - the WinPE section - with just my keyboard, since apparently, my trackpad was not supported and did not work at all. Once the system went through its first of what would be many reboots to come and loaded into the phase of the installation where you're actually already running Windows 11, my trackpad came to life, but without any gestures support - so no scrolling. Not a gamebreaker or anything, but definitely annoying. A bigger issue was that the Wi-Fi 7 Intel BE200 chip in my laptop was not supported out of the box by Windows 11. This meant that I had to install these drivers during the installation process, which involves going to the Intel website and finding the correct drivers to use. To make this process more obtuse and less intuitive, you can't use the normal driver installer; you have to specifically opt for the "Intel® PROSet/Wireless Software and Wi-Fi Drivers for IT Administrators", download the ZIP, unpack it on a different computer, put the unpacked drivers on a USB stick, and point the Windows 11 installer to this USB stick. Mind you, the BE200 chip was launched almost three years ago, and there's no excuse for Windows 11 not supporting this chip out of the box - like Linux does. The remainder of the installation process involved dodging a lot of tracking and telemetry prompts, reboots, a lot of waiting, setting up the dreaded online account, waiting some more, and then finally ending up at the desktop. I then set out to enjoy my EU privileges by removing whatever applications I didn't need and turning off features I didn't want, as well as making sure all the drivers were up to date. This mostly involved installing the Intel Driver & Support Assistant and the Intel graphics drivers. Curiously, this is where I hit a returning issue: after installing the Intel GPU drivers for the first time, as well as after every subsequent update, the screen would go black and stay that way, forcing a reboot. Windows' graphics stack is supposed to be able to gracefully handle driver updates, but clearly, some bug or problem was preventing the updated Intel driver from being reinitialised. Once those initial setup tasks were behind me, I experienced two more problems. First, sleep/wake was entirely broken and simply did not work. It turns out Windows 11 really doesn't like S3 sleep, and I had to specifically go into my laptop's Dasharo Coreboot firmware to switch to S0ix get sleep/wake to work on Windows 11. Windows defaults to something it calls "Modern Standby", which requires the S0ix state to be enabled. You can also disable Modern Standby which would presumably make sleep/wake work with S3 (?), but this is a whole ordeal and clearly not something Microsoft wants you to do. Of course, the correct way of handling this would be for Windows 11 to adapt its sleep/wake settings to what the firmware reports, but alas. Another problem were the laptop's cooling fans seemingly leading lives of their own, spinning up loudly at entirely random times, irrespective of use. It was so bad and loud

08 Jul 2026 10:27pm GMT

The state of accessibility in GNOME

With July being Disability Pride Month, GNOME's Sophie Herold published a blog post taking stock of where GNOME stands on this front, progress that's been made, as well as areas where the project comes short. One particular paragraph from her introduction really hits the nail on the head about accessibility discussions in tech circles: The reality of tech communities is that they are often ableist and elitist. Probably more so than the average population. If a user or contributor struggles with a tool, blame is shifted to a "skill issue," if an interface is simplified to make it accessible to more people, it's "dumbed down". Assistive technologies are often developed by abled people, without involving and paying disabled people. This also leads to an attitude where contributors expect gratefulness from disabled people for providing them with the most basic needs. All these issues are also not absent from the GNOME community. ↫ Sophie Herold Even as someone who isn't disabled and doesn't use any tools classically shelved under the "accessibility" moniker, I encounter the attitudes she mentions in the quoted paragraph basically every day. While we can have normal, productive discussions and differences of opinion about accessibility - for instance, I strongly believe robust theming support is absolutely crucial to accessibility, while the wider GNOME community does not - the dismissive attitudes towards people with accessibility needs in the software world is shameful. Even if you don't have accessibility needs today, you will definitely be needing them at some point in your life. If accessibility isn't one of the first words you jot down on your mood board or whatever when you start a new software project, you've already done millions of people a massive disservice. Get educated, learn what you can about accessibility, listen to people with accessibility needs, and make your software better for everyone. You'll thank yourself one day.

08 Jul 2026 10:23pm GMT

Next release of Cinnamon finally supports Wayland

Linux Mint's Cinnamon is one of the last desktops to still not support Wayland, and is relegated to only being compatible with legacy X11 environments. With the next release of Cinnamon, however, this is finally going to change. We worked really hard on Wayland and we got to the point where it feels solid and the experience is almost on par with X11. Wayland support will no longer be considered "experimental". In the next version of Cinnamon, both X11 and Wayland will be fully supported. ↫ Clement Lefebvre on the Linux Mint blog The next release of Cinnamon, version 6.8, will be part of the next release of Linux Mint, scheduled for Christmas of this year.

08 Jul 2026 10:07pm GMT