fidzu : geek

New York Governor Kathy Hochul has dropped a proposal that would have allowed limited commercial robotaxi deployments outside New York City, citing a lack of support among state legislators. "The move is a blow to Waymo and other robotaxi companies who saw New York, and especially New York City, as a potential goldmine," reports The Verge. From the report: The plan, which was introduced by Hochul as part of the state's budget proposal last month, would have allowed limited robotaxi deployment in cities other than the Big Apple -- while leaving whether New York City would get autonomous vehicles up to the mayor and the City Council. But now that plan is DOA, as support in the legislature never materialized. "Based on conversations with stakeholders, including in the legislature, it was clear that the support was not there to advance this proposal," Sean Butler, a Hochul spokesperson, said in a statement. "While we are disappointed by the Governor's decision, we're committed to bringing our service to New York and will work with the State Legislature to advance this issue," Waymo spokesperson Ethan Teicher said in a statement. "The path forward requires a collaborative approach that prioritizes transparency and public safety."

Read more of this story at Slashdot.

20 Feb 2026 10:00am GMT

NASA has officially classified Boeing Starliner's 2024 crewed flight as a "Type A" mishap, acknowledging serious technical failures and leadership shortcomings that nearly left astronauts unable to safely return. Administrator Jared Isaacman released (PDF) a 311-page internal report citing flawed decision-making and cultural issues, with the next Starliner flight now planned as uncrewed pending major fixes. Ars Technica reports: As part of the announcement, NASA Administrator Jared Isaacman sent an agency-wide letter that recognized the shortcomings of both Starliner's developer, Boeing, as well as the space agency itself. Starliner flew under the auspices of NASA's Commercial Crew Program, in which the agency procures astronaut transportation services to the International Space Station. "We are taking ownership of our shortcomings," Isaacman said. "Starliner has design and engineering deficiencies that must be corrected, but the most troubling failure revealed by this investigation is not hardware," Isaacman wrote in his letter to the NASA workforce. "It is decision-making and leadership that, if left unchecked, could create a culture incompatible with human spaceflight." Isaacman said there would be "leadership accountability" as a result of the decisions surrounding the Starliner program, but did not say which actions would be taken.

Read more of this story at Slashdot.

20 Feb 2026 7:00am GMT

US President Donald Trump says he will direct US agencies, including the defence department, to "begin the process of identifying and releasing" government files on aliens and extraterrestrial life. From a report: Trump made the declaration in a post on Truth Social, after he accused Barack Obama earlier in the day of revealing classified information when the former president said "aliens are real" on a podcast last week. "He's not supposed to be doing that," Trump told reporters aboard Air Force One, adding: "He made a big mistake." Asked if he also thinks aliens are real, Trump answered: "Well, I don't know if they're real or not." Former US President Obama told podcast host Brian Tyler Cohen that he thinks aliens are real in an interview released last Saturday. "They're real, but I haven't seen them, and they're not being kept in Area 51," Obama said. "There's no underground facility unless there's this enormous conspiracy and they hid it from the president of the United States."

Read more of this story at Slashdot.

20 Feb 2026 5:00am GMT

"AI Injury Attorneys" target the chatbot design itself.

19 Feb 2026 10:44pm GMT

"The most troubling failure revealed by this investigation is not hardware."

19 Feb 2026 9:59pm GMT

Technology is a double-edged sword in the $399 Rubik's Cube-inspired toy.

19 Feb 2026 9:30pm GMT

As if keeping track of whatever counts as a release schedule for Windows wasn't complicated enough - don't lie, you don't know when that feature they announced is actually being released either - Microsoft is making everything even more complicated. Soon, Microsoft will be releasing Windows 11 26H1, but you most likely won't be getting it because it's strictly limited to devices with Qualcomm's new Snapdragon X2 Series processors. The only way to get this version of Windows is to go out and buy a device with a Snapdragon X2 Series processor. Windows 11 26H1 will not be made available to any other Windows 11 users, so nobody will be able to upgrade to it. Furthermore, users of Windows 11 26H1 will not be able to update to the "feature update" for users of Windows 11 24H2 and 25H2, the regular Windows versions, planned for late 2026. Instead, Microsoft promises there will be an upgrade path for 26H1 users in a "future" release of Windows. Why? Devices running Windows 11, version 26H1 will not be able to update to the next annual feature update in the second half of 2026. This is because Windows 11, version 26H1 is based on a different Windows core than Windows 11, versions 24H2 and 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release. ↫ AriaUpdated at the Windows IT Pro Blog The same thing happened when Qualcomm releases its first round of Snapdragon processors for Windows, as Windows 24H2 was also tied to this specific platform. It seems Microsoft is forced to have entirely separate and partially incompatible codebases just to support Snapdragon processors, which must be a major pain in the ass to deal with. Considering Windows on ARM hasn't exactly been a smashing success, one may wonder how long Microsoft remains willing to make such exceptions for a singular chip.

19 Feb 2026 9:27pm GMT

So vi only has one level of undo, which is simply no longer fit for the times we live in now, and also wholly unnecessary given even the least powerful devices that might need to run vi probably have more than enough resources to give at least a few more levels of undo. What I didn't know, however, is that vi's limited undo behaviour is actually part of POSIX, and for full compliance, you're going to need it. As Chris Siebenmann notes, vim and its derivatives ignore this POSIX requirement and implement multiple levels of undo in the obviously correct way. What about nvi, the default on the BSD variants? I didn't know this, but it has a convoluted workaround to both maintain POSIX compatibility and offer multiple levels of undo, and it's definitely something. Nvi has opted to remain POSIX compliant and operate in the traditional vi way, while still supporting multi-level undo. To get multi-level undo in nvi, you extend the first 'u' with '.' commands, so 'u..' undoes the most recent three changes. The 'u' command can be extended with '.' in either of its modes (undo'ing or redo'ing), so 'u..u..' is a no-op. The '.' operation doesn't appear to take a count in nvi, so there is no way to do multiple undos (or redos) in one action; you have to step through them by hand. I'm not sure how nvi reacts if you want do things like move your cursor position during an undo or redo sequence (my limited testing suggests that it can perturb the sequence, so that '.' now doesn't continue undoing or redoing the way vim will continue if you use 'u' or Ctrl-r again). ↫ Chris Siebenmann Siebenmann lists a few other implementations and how they work with undo, and it's interesting to see how all of them try to solve the problem in slightly different ways.

19 Feb 2026 1:06am GMT

F9 is an L4-inspired microkernel designed for ARM Cortex-M, targeting real-time embedded systems with hard determinism requirements. It implements the fundamental microkernel principles-address spaces, threads, and IPC, while adding advanced features from industrial RTOSes. ↫ F9 kernel GitHub page For once, not written in Rust, and comes with both an L4-style native API and a userspace POSIX API, and there's a ton of documentation to get you started.

18 Feb 2026 10:08pm GMT

On Friday, July 18th, 2025, the Arch Linux team was notified that three AUR packages had been uploaded that contained malware. A few maintainers including myself took care of deleting these packages, removing all traces of the malicious code, and protecting against future malicious uploads.

30 Jan 2026 12:00am 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