fidzu : geek

U.S. battery storage installations hit a record 57.6 GWh in 2025, and Texas is now poised to surpass California as the nationâ(TM)s largest storage market in 2026. Electrek reports: According to the US Energy Storage Market Outlook Q1 2026 from the Solar Energy Industries Association (SEIA) and Benchmark Mineral Intelligence, installations are now four times higher than totals from just three years ago. The US had a total of 137 GWh of utility-scale storage installed as of 2025, plus 19 GWh of commercial and industrial systems and 9 GWh of residential storage. Analysts expect the growth streak to continue. More than 600 GWh of energy storage is projected to be deployed nationwide by 2030, even as the Trump administration targets clean energy industries. Two-thirds of utility-scale storage installed in 2025 was built in red states, including nine of the top 15 states for new installations. Texas is projected to surpass California as the countryâ(TM)s largest battery storage market in 2026. Standalone battery projects accounted for nearly 30 GWh of new capacity in 2025, while solar-plus-storage installations made up about 20 GWh. Residential storage deployments reached 3.1 GWh last year, a 51% increase year-over-year. Analysts say virtual power plant programs in states such as Massachusetts, Texas, Arizona, and Illinois are helping drive adoption by reducing costs and easing strain during peak demand periods. The supply chain is shifting to support the boom. In 2025, some battery cell manufacturers pivoted production from EV batteries to dedicated stationary storage cells, converting existing lines and adjusting future plans. Lithium-ion cell manufacturing for stationary storage reached more than 21 GWh in 2025, enough to power Houston overnight, according to SEIAâ(TM)s Solar and Storage Supply Chain Dashboard. Meanwhile, US factories now have the capacity to manufacture 69.4 GWh of battery energy storage systems annually.

Read more of this story at Slashdot.

24 Feb 2026 7:00am GMT

An anonymous reader quotes a report from the Guardian: When two men knocked on Ida Huddleston's door last May, they carried a contract worth more than $33m in exchange for the Kentucky farm that had fed her family for centuries. According to Huddleston, the men's client, an unnamed "Fortune 100 company," sought her 650 acres (260 hectares) in Mason county for an unspecified industrial development. Finding out any more would require signing a non-disclosure agreement. More than a dozen of her neighbors received the same knock. Searching public records for answers, they discovered that a new customer (PDF) had applied for a 2.2 gigawatt project from the local power plant, nearly double its annual generation capacity. The unknown company was building a datacenter. "You don't have enough to buy me out. I'm not for sale. Leave me alone, I'm satisfied," Huddleston, 82, later told the men. As tech companies race to build the massive datacenters needed to power artificial intelligence across the US and the world, bids like the one for Huddleston's land are appearing on rural doorsteps nationwide. Globally, 40,000 acres of powered land - real estate prepped for datacenter development -- are projected to be needed for new projects over the next five years, double the amount currently in use. Yet despite sums that often dwarf the land's recent value, farmers are increasingly shutting the door. At least five of Huddleston's neighbors gave similar categorical rejections, including one who was told he could name any price. In Pennsylvania, a farmer rejected $15m in January for land he'd worked for 50 years. A Wisconsin farmer turned down $80m the same month. Other landowners have declined offers exceeding $120,000 per acre -- prices unimaginable just a few years ago. The rebuffs are a jarring reminder of AI's physical bounds, and limits of the dollars behind the technology. [...] As AI promises to transcend corporeal fallibility, these standoffs reveal its very physical constraints -- and Wall Street's miscalculation of what some people value most. In the rolling hills of Mason county and farmland across America, that gap is measured not in dollars but in something harder to price: identity.

Read more of this story at Slashdot.

24 Feb 2026 3:30am GMT

In her first major interview as Microsoft's new gaming chief, Asha Sharma said that "great games" must deliver emotional resonance and a distinct creative voice, while making clear that she has "no tolerance for bad AI." Stepping in after Phil Spencer's retirement, she's pledging consistency, community trust, and a human-first approach to storytelling as Xbox enters a new era. Variety reports: Sharma was quick in laying out her top priorities for Microsoft Gaming in an internal memo announcing her promotion, noting "great games," "the return of Xbox" and the "future of play" as her three main commitments to the gaming community. So first, what makes a great game for Sharma, whose roles prior to CoreAI include top positions at Instacart and Meta? The new Microsoft Gaming CEO tells Variety it's all about games with "deep emotional resonance" and "a distinct point of view." She wants to develop stories that make players "feel something," like the kind of feelings Campo Santo's 2016 first-person mystery "Firewatch" elicited in her. Sharma takes on the mantle as head of the leading competitor to Sony's PlayStation and Nintendo knowing full well she's entering the role as an outsider to the larger gaming community and has "a lot to learn" still. But Sharma says she's got a commitment to "being grounded in what the community is telling us." "I'm coming into gaming as a platform builder," Sharma said, adding that her goal is to "earn the right to be trusted by players and developers" and show the fanbase that "consistency" over time. In her interview with Variety, Sharma acknowledged the tumultuous state of the gaming industry, referencing Matthew Ball's recent State of Video Gaming in 2026 report as evidence that the larger "transformation" of the sector is "protecting what we believe in while remaining open-minded about the future." Due to her strong background in AI, initial reactions to Sharma's appointment have raised concerns about what her specific views are on the use of generative AI in game development. Sharma says her stance is simple: she has "no tolerance for bad AI." "AI has long been part of gaming and will continue to be," Sharma said, noting that gaming needs new "growth engines," but that "great stories are created by humans."

Read more of this story at Slashdot.

24 Feb 2026 2:02am GMT

While Libadwaita applications running in a GNOME desktop environment look great and nicely consistent, they look utterly out of place and jarring when run in Xfce, Pantheon, KDE, and others. The biggest reason for this is GNOME's insistence on using client-side decorations, which feel at home inside a GNOME environment, but out of place in environments that otherwise do not use them. On top of that, Libadwaita's/GNOME's CSDs can interfere with non-GNOME window managers and their functionality, causing a whole host of problems. But what if you could turn CSDs off? GTK-NoCSD is an LD_PRELOAD library to disable CSD in GTK3/4, LibHandy, and LibAdwaita apps. CSD is client side decoration, there is also server side decoration, SSD, both serving as the titlebar of windows. GTK3 adopted CSD, where this thick headerbar is used with application controls embedded.This continued into the platform library, LibHandy, then into GTK4 and the platform library of that, LibAdwaita. This looks good on Gnome and makes these applications alike, but looks off everywhere else and can potentially break window managers and remove window manager provided functionality. This library restores the server side decoration, getting back the window manager titlebar, and moves the controls from the CSD to under it, into the window content. ↫ GTK-NoCSD's Codeberg page This isn't the first attempt at such a solution, and certainly won't be the last, and I'm glad they exist. Do note that if you decide to use this library, any problems or bugs you run into in an application 'modified' by it should never be reported to the application's developer, but to the developer of this library. If you encounter a bug in an application modified by this library, test the application in its unmodified state to ensure it's actually a bug in the application before reporting it to the application's developer. Developers who choose to use client-side decorations are not responsible for bugs and issues arising from you removing the CSD. Keep that in mind. That being said, whatever pixels appear on your screen is entirely up to you as a user, and you have the right to theme, alter, butcher, or mangle whatever application is running on your computer. If you dislike the way CSDs look and feel on your computer, you can opt to resort to a solution like this one, and that's entirely fair game. There's packages for Arch, Fedora, and Gentoo, and of course, you can build it yourself. As for my personal opinion - well, let's just say I prefer KDE for many, many reasons, and my disdain for CSDs is certainly one of them. Call me old-fashioned and out-of-touch, but I like the classic distinction between titlebar, menubar, and toolbar.

23 Feb 2026 11:25pm GMT

"The point is to get missions out the door as fast as possible. Two to three years is too slow."

23 Feb 2026 10:14pm GMT

Even in a fragile farm economy, million-dollar offers can't sway dedicated farmers.

23 Feb 2026 9:48pm GMT

Every OpenBSD admin has booted bsd.rd at least once - to install, upgrade, or rescue a broken system. But few people stop to look at what's actually inside that file. It turns out bsd.rd is a set of nested layers, and you can take it apart on a running system without rebooting anything. That's what we'll do here. We'll go from the raw gzip file all the way down to the miniroot filesystem, exploring each layer with standard tools. Everything is documented in the man pages - we're just following the trail. ↫ Wesley Mouedine Assaby What am I supposed to add here?

23 Feb 2026 9:46pm GMT

Panasonic was one of the last Japanese companies still manufacturing TVs.

23 Feb 2026 9:16pm GMT

The regular, consumer version of Windows 10 isn't the only Windows release reaching or having reached end-of-life, now middling on under the Extended Security Updates program for the many people sticking with the venerable release. Windows 10 Enterprise LTSB 2016 (October 13, 2026), Windows 10 IoT Enterprise 2016 LTSB (October 13, 2026), and Windows Server 2016 (January 12, 2027) are all reaching end-of-life soon, too. On the listed dates, these versions of Windows will receive their final monthly security updates. As with Windows 10 for consumers, however, there's a way out: the Extended Security Updates program will also kick in for these versions, offering critical and important security updates, and support relating to just those. The program will be offered for up to three years after official support ends, and won't be free. For Server 2016 and and Enterprise LTSB 2016, pricing will be $61 per year, but it would double for every year after the first. Pricing for IoT Enterprise 2016 LTSB is available upon request. Of course, Microsoft urges you to upgrade to newer versions - Windows Server 2025, Windows 11 Enterprise LTSC 2024, and Windows 11 IoT Enterprise LTSC 2024 - but if you're happy with your current version, you can at least get a three-year reprieve, for a price.

21 Feb 2026 1:59pm 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