geek

26 Jul 2026

Slashdot

Three Astronauts Safely Return from Space Station, Landing in Kazakhstan Steppe

"Welcome home!" NASA posted on X.com, sharing footage of a successful "parachute-assisted" landing on a Kazakhstan steppe for the Soyuz MS-28, carrying three astronauts who'd spent 241 days on the International Space Station. (And YouTube has a full two-hour video with NASA's coverage of the landing.) A NASA web page notes they orbited Earth 3,856 times and traveling more than 102 million miles after docking with the Space Station on November 27. It was the first mission for NASA astronaut Chris Williams and Roscosmos cosmonaut Sergei Mikaev (and the second mission for Roscosmos cosmonaut Sergey Kud-Sverchkov). "After routine post-landing medical checks, recovery teams will fly the crew by helicopter to Karaganda, Kazakhstan. Williams then will board a NASA aircraft bound for the agency's Johnson Space Center in Houston."

Typo-Squatting Scammers Con South Carolina Town Out of $545K

It started with some underground utility work for the South Carolina town of Surfside Beach (population: 4,155). "Public records confirm that a payment of $545,598.30 was issued," according to a local news station - but the CEO of Wildcat Contractors "stated that the account that received the money is a scammer account and that his company has an overdue invoice for underground utility work completed in Surfside Beach." Yahoo picks up the story: After the payment issue surfaced, Wildcat said Surfside Beach sent over the email thread containing the payment confirmation. The company told WMBF it noticed multiple red flags in the chain. One involved an email address where "Wildcat" appeared with an extra "i." Another involved documents that the company said included a forged signature taken from a prior notarized document. Wildcat said the money was sent to a spoofing account claiming to be the contractor. More local reports are unraveling what happened: According to the Wall Street Journal, the town's finance director said a town employee called Wildcat's project manager on March 13, the day the payment was sent. The project manager referred the caller to [Wildcat CEO] Bowker. The town then called Bowker's mobile phone and left a voicemail about the ACH transfer. Bowker told the Wall Street Journal she does not recall the voicemail but acknowledged she may have missed it. Now a new report released by a law firm hired by the town to investigate "shows it did make an attempt to verify before sending $545,000 to a fraudulent bank account," according to local news reports: According to the report, the town sent an email to Wildcat's legitimate email domain on March 13 requesting a callback for verbal verification before sending the payment. Surfside received a response to that email with a phone number, though it remains unclear whether that response came from a real Wildcat employee or from the scammers. The report found that the fake town domain was used in communications between both parties throughout the process, which the law firm overseeing the investigation said was likely created to facilitate the fraud and delay its discovery. That seems to be the case in a nutshell: Investigators determined the fraudsters used spoofed and typo-squatted email domains, including surfsidesbeach.org, to impersonate town officials and redirect the payment. The fraudulent domain was created March 9 and was used to help conceal the scheme, according to investigators. Town officials said they are continuing to work with the FBI, South Carolina Law Enforcement Division, and their insurance partners to recover the funds. "The town has also implemented additional security measures to strengthen payment verification procedures and reduce the risk of similar incidents."

A Promising Process For Nuclear Fuel Re-use and Disposal?

A Canadian lab has run a chemical process on real spent nuclear fuel "and pulled out 90% of the long-lived danger in 24 hours, the part that forces a burial site to last 100,000 years," notes the blog Autonocio, "with the leftovers meant to fuel a reactor." The standard plan for spent nuclear fuel is to wait it out. You pull the used bundles from a reactor, sit them in a pool of water for seven to ten years while the heat and radiation come down, seal them in concrete casks, and look for somewhere deep and geologically dull to leave them for the next hundred thousand years. Canada has been hunting for that burial site since the 1980s and still doesn't have one in the ground. A company in Saint John, New Brunswick thinks most of what makes that waste dangerous never needed to go in the ground at all. Moltex Energy Canada says a chemical process it calls WATSS can strip 90% of the long-lived material out of used Canada Deuterium Uranium [CANDU] fuel in 24 hours, and that the concentrated leftovers become fuel for a reactor it wants to build on the same site. The recovery step isn't a slide in a pitch deck anymore. In 2025, World Nuclear News reported that Canadian Nuclear Laboratories ran the process on real used fuel from a commercial Canadian reactor and confirmed the 90% figure. None of it is generating power yet. What exists is a validated chemical step and a reactor design waiting in line at a regulator. The rest is a 2030s problem. "The chemistry has a lab result behind it. The reactor does not exist..." the article points out. "Moltex is aiming to have its first WATSS and SSR-W units running at Point Lepreau by the early-to-mid 2030s... Not everyone buys the pitch. Critics have argued the reprocessing creates its own stream of byproducts, that the economics are unproven, and that a single site's stockpile is finite." But Moltex "isn't alone in trying to burn nuclear waste instead of bury it," the article notes, with Switzerland and Denmark "chasing the same goal a different way." Switzerland's Transmutex drives a subcritical reactor with a particle accelerator, feeding it spent fuel alongside thorium... Denmark's Copenhagen Atomics is building a thorium molten-salt reactor that fits inside a shipping container and runs on the leftovers from conventional plants. Thanks to long-time Slashdot reader kwelch007 for sharing the article.

25 Jul 2026

Ars Technica

SDCC teaser gives us our first good look at Blade Runner 2099

Also: Forging the One Ring in Rings of Power S3 teaser; new Lanterns trailer; Spaceballs: The New One panel.

25 Jul 2026 8:52pm GMT

SpaceX eyes tower catch for next Starship after auspicious end to 13th flight

SpaceX will likely attempt to catch Starship back at the launch pad on its next flight.

25 Jul 2026 5:47pm GMT

With help from data, art museums are reframing the visitor experience

Museums are embracing data-driven curation and a shifting technology landscape.

25 Jul 2026 11:00am GMT

24 Jul 2026

OSnews

The Hurd gets 9pfs, OpenNTPD, dynamic /dev/ entries, and more

The hottest and most promising operating system kernel in development, the GNU Hurd, has published another summary of its most recent quarter of development. Hurd has experimental support for 9pfs now, a work-in-progress port of OpenNTPD, the NTP daemon from OpenBSD, a port of Neovim, and a few more ports here and there. Diving deeper into the actual kernel itself, there's a major improvement to how the Hurd handles entries in /dev/: Mikhail Karpov added some checks for mmap in several places. He also worked on adding storeio to the bootstrap chain. This is actually quite interesting. Currently the Hurd sets device entries in /dev/ statically. For example, I am writing this qoth on a Hurd machine that is using two /dev/ entries for my filesystem: /dev/wd0s1 for swap and /dev/wd0s5 for my root filesystem. However, /dev/wd0s1 through /dev/wd0s16 exist on my computer! Once Mikhail's project is done, then the Hurd will dynamically populate SATA devices at boot time! No more need for static translators! ↫ The Hurd's quartely report The dhcpcd port we talked about earlier this year keeps improving too, which is quite important for future IPv6 support. Of course, there's way more to dive into, and reading about a bunch of people developing their own thing without any regard for or interest in the mainstream always feels a little bit like a cold glass of tonic - the best soft drink - in the depths of hell. Keep at it.

24 Jul 2026 10:44pm GMT

Google Play Services drops support for Android 6.0

Given that Android phones have been around for nearly two decades now, there comes a time when Google has to end support for one of its older software versions. For a couple of years now, Google Play services has been supported on devices running Android 6.0 Marshmallow or newer. That has changed over the past few weeks, with Google deciding to retire this software version after a nearly 11-year run. ↫ Chethan Rao at Android Authority At some point, an operating system version needs to be left behind - and I don't think it's entirely unreasonable to no longer support Google Play Services on an operating system version that's 11 years old. However, this is Android we're talking about, and devices running Android 6.0 were probably sold much more recently than 11 years ago, when the operating system version was new. Hell, I wouldn't be surprised if devices running Android 6.0 are still being sold today. I doubt this is something that will affect many people who read OSNews, but there's bound to be edge cases - Android 6.0 devices silently doing their job that are now just a little less useful. I'm thinking of really cheap tablets that can still play video just fine, retro gaming handhelds that don't magically lose the ability to emulate SNES games, that sort of stuff. The numbers will be small, but if you happen to be among them, this can be a really annoying deprecation.

24 Jul 2026 10:22pm GMT

23 Jul 2026

OSnews

FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary

A rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here's why. A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. ↫ Kyle Evans in freebsd-announce While FreeBSD's ports tree is not hosted by GitHub - it's merely mirrored there - the FreeBSD team believes the community values the GitHub mirror too much, and as such, steps had to be taken to fix this. Ports has not been compromised and users' systems do not appear to be at risk in any way due to this occurrence, which is good news. Curiously, the official announcement makes no mention of which 150MB file, exactly, was committed to ports, but it didn't take for people long to pinpoint the offending commit (screenshot). It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. This FreeBSD port is effectively a way to easily install and run this tool on FreeBSD using Linuxulator, FreeBSD's Linux compatibility layer that allows you to run unmodified Linux binaries on FreeBSD. It's important to note this FreeBSD port is not actually a port of the Linux version of github-copilot-cli to FreeBSD; the FreeBSD "port" merely acts as a setup script to run the unmodified Linux binary using Linuxulator. It's not a "real" port because the tool isn't open source and its license doesn't allow for modifications. That's why the announcement specifically mentions "questionable licensing" - github-copilot-cli is licensed under some custom license specifically made for this tool, and is not open source. Anyway, for whatever reason, the maintainer of this FreeBSD port accidentally made a commit that added the actual, full 150MB Linux binary to FreeBSD ports. I'm assuming that under normal circumstances, building and installing the github-copilot-cli FreeBSD port would merely download the binary off GitHub and set Linuxulator up so that it could run it. Mistakes happen, and since there's clearly nothing malicious going on, there's not much to worry about. In fact, this may lead to new checks and balances to prevent this from happening in the future, which would be good news. The FreeBSD team is working on rolling back, fixing the issue, and investigating how this could have happened. Ports is still frozen at the time of writing, but I'm sure we'll have a more detailed account soon.

23 Jul 2026 8:33pm GMT