fidzu : geek

The IRS's IT division has reportedly lost 40% of its staff and nearly 80% of its tech leadership amid a federal "efficiency" overhaul, the agency's CIO revealed yesterday. The Register reports: Kaschit Pandya detailed the extent of the tech reorganization during a panel at the Association of Government Accountants yesterday, describing it as the biggest in two decades. ... The IRS lost a quarter of its workforce overall in 2025. But the tech team was clearly affected more deeply. At the start of the year, the team encompassed around 8,500 employees. As reported by Federal News Network (FNN), Pandya said: "Last year, we lost approximately 40 percent of the IT staff and nearly 80 percent of the execs." "So clearly there was an opportunity, and I thought the opportunity that we needed to really execute was reorganizing." That included breaking up silos within the organization, he said. "Everyone was operating in their own department or area." It is not entirely clear where all those staff have gone. According to a report by the US Treasury Inspector General for Tax Administration, the IT department had 8,504 workers as of October 2024. As of October 2025, it had 7,135. However, reports say that as part of the reorganization, 1,000 techies were detailed to work on delivering frontline services during the US tax season. According to FNN, those employees have questioned the wisdom of this move and its implementation.

Read more of this story at Slashdot.

19 Feb 2026 10:40pm GMT

An anonymous reader quotes a report from the Wall Street Journal: Meta Chief Executive Mark Zuckerberg faced a barrage of questions about his social-media company's efforts to secure ever more of its users' time and attention at a landmark trial in Los Angeles on Wednesday. In sworn testimony, Zuckerberg said Meta's growth targets reflect an aim to give users something useful, not addict them, and that the company doesn't seek to attract children as users. [...] Mark Lanier, a lawyer for the plaintiff, repeatedly asked Zuckerberg about internal company communications discussing targets for how much time users spend with Meta's products. Lanier showed an email from 2015 in which the CEO stated his goal for 2016 was to increase users' time spent by 12%. "We used to give teams goals on time spent and we don't do that anymore because I don't think that's the best way to do it," Zuckerberg said on the witness stand in sworn testimony. Lanier also asked Zuckerberg about documents showing Meta employees were aware of children under 13 using Meta's apps. Zuckerberg said the company's policy was that children under 13 aren't allowed on the platform and that they are removed when identified. Lanier showed an internal Meta email from 2015 that estimated 4 million children under 13 were using Instagram. He estimated that figure would represent approximately 30% of all kids aged 10 to 12 in the U.S. In response to a question about his ownership stake in Meta, which amounts to roughly more than $200 billion, Zuckerberg said he has pledged to donate most of his money to charity. "The better that Meta does, the more money I will be able to invest in science research," he said. [...] On the stand, Zuckerberg was also asked about his decision to continue to allow beauty filters on the apps after 18 experts said they were harmful to teenage girls. The company temporarily banned the filters on Instagram in 2019 and commissioned a panel of experts to review the feature. All 18 said they were damaging. Meta later lifted the ban but said it didn't create any filters of its own or recommend the filters to users on Instagram after that. "We shouldn't create that content ourselves and we shouldn't recommend it to people," Zuckerberg said. But at the same time, he continued, "I think oftentimes telling people that they can't express themselves like that is overbearing." He also argued that other experts had thought such bans were a suppression of free speech. By focusing on the design of Meta's apps rather than the content posted in them, the case seeks to get around longstanding legal doctrine that largely shields social-media companies from litigation. At times, the case has veered into questions of content, prompting Meta's lawyers to object.

Read more of this story at Slashdot.

19 Feb 2026 10:02pm 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

A bare-bones Chinese app called "Are You Dead?" -- whose entire premise is that solo-living users tap daily to confirm they're still alive, triggering an alert to an emergency contact after two missed check-ins -- has rocketed to the top of China's app store charts and gone viral globally without spending a dime on advertising. The app wasn't built for the elderly, as many assumed; its creators are Gen-Z developers who said they were inspired by the isolation of urban life in a country where one-person households are expected to hit 200 million by 2030. Its rise coincided with China's birth rate plunging to a record low. Beijing quietly removed the app from Chinese stores last month, and the developers are now crowdsourcing a new name on social media after their first rebrand attempt, "Demumu," failed to catch on.

Read more of this story at Slashdot.

19 Feb 2026 9:21pm 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

Report: Verizon's goal is "immediate unlock for all payment methods really soon."

18 Feb 2026 8:58pm GMT

Two of Ars' favorite electric vehicles are now available for not very much money.

18 Feb 2026 8:22pm GMT

EPA sued for abandoning its mission to protect public health.

18 Feb 2026 7:48pm 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