fidzu : geek

An anonymous reader quotes a report from the Hill: Elon Musk's SpaceX plans to invest more than $74 billion into building two data centers in Texas and Arizona, the company announced Thursday, marketing them as projects that will boost local communities amid backlash surrounding such facilities. "These investments will expand local tax bases, generate substantial new revenue for schools and public services, and create economic opportunities that extend far beyond the facilities themselves," the company said in a release. SpaceX said it will put more than $24 billion into a new project in Texas's Rio Grande Valley, expanding the company's headquarters in Starbase -- a coastal town the tech giant established in 2025 in a previously unincorporated area of Cameron County. In Arizona, SpaceX will invest around $50 billion in Cochise County, a rural area east of Tucson bordering Mexico and New Mexico. SpaceX pledged the new projects will be created cooperatively with the surrounding communities and will be environmentally conscious. The company said the project in Texas would generate its own power and invest $220 million to expand the water supply in nearby Brownsville. While in Arizona, it vowed to work with local electric cooperatives and "potentially" reduce electric bills, saying the site would use dry cooling without water consumption. "They require strong partnerships with local communities, responsible environmental stewardship, and stable, competitive policies that give companies the confidence to make long-term investments," the company said in a release. Both sites promise hundreds of permanent jobs even once construction is complete.

Read more of this story at Slashdot.

13 Nov 2026 3:30am GMT

Whoop has launched Humans, a social network built into its fitness app where every account is a real person with a "verified heartbeat." The wearable company claims its platform is "entirely human," unlike other social media platforms that are "saturated with artificial intelligence, automated accounts and bots, and manufactured content." The Verge reports: Starting Thursday, Whoop members can share their data from its wearables on the app's new Whoop Humans social network. Users can make their metrics, activities, and achievements visible to other Whoop wearers, post Story-like "Moments" with photos and captions, and add comments and reactions on other members' posts. [...] In the Community tab in Whoop's app, users can scroll through Moments from people they're following, like tapping through your Stories feed on Instagram but with your friends' fitness tracker data. In one of Whoop's examples, swiping up on a user's Moments post with a photo from their run shows a map with their route and details like their pace and distance. The Community tab also shows cards for people in your "community" with their sleep, recovery, and strain scores. Whoop says users choose which activities, achievements, and metrics they want to share on Humans, including Recovery, Strain, Sleep, HRV, and resting heart rate. Any activities marked as sensitive aren't shared by default. There's also an option to keep Moments posts private and a "Stealth Mode" for temporarily hiding health and performance data without changing your sharing settings.

Read more of this story at Slashdot.

13 Nov 2026 1:40am GMT

Nintendo has issued four DMCA takedown notices targeting two Nintendo Switch emulators, Yuzu and Citron Neo, along with mod chip firmware such as Picofly, SX Core and HWFLY. As a result, 144 repositories containing firmware used to circumvent the console's copy protections have been removed by GitHub and replaced by a DMCA takedown notice. IGN reports: GitHub has posted Nintendo's November 6 DMCA notice, which says, "The Nintendo Switch console and video games contain technological protection measures ('TPMs') that permit the Nintendo Switch console to interact only with legitimate Nintendo video game files. This process protects Nintendo's copyright-protected video games, (...) by preventing users from playing pirated copies of Nintendo's video games on the Nintendo Switch console and by preventing users from unlawfully copying and playing Nintendo's video games on unauthorized devices." However, while this takedown has effectively wiped out a ton of repositories with mod chip firmware, it seems like it's still being hosted elsewhere on the site, according to TorrentFreak. It's possible, though, that Nintendo isn't finished yet; back in 2024, Nintendo effectively took down 8,500 copies of Yuzu by issuing a takedown that targeted 12 different mirrors of the emulator. This particular takedown also comes a few days after emulators were able to run the remake of The Legend of Zelda: Ocarina of Time on PC, so this could be a sign that Nintendo is winding up its lawyers to crack down on emulation once again.

Read more of this story at Slashdot.

12 Nov 2026 11:00pm GMT

There are many problems in this world - some big, some small, some so minute nobody ought to put them to paper at all. The problem I'm going to highlight here is even smaller than that. This literally - the actual literally - does not matter and absolutely nobody should care about it, let alone put any work into changing it or addressing it some other way. I want to talk about the iconography GNOME's Disks utility uses to symbolise "mount" and "unmount". No, I'm not descending into madness. GNOME's Disks utility uses the "play" symbol on the mount button, and the "stop" symbol on the unmount button. Inexplicably, considering the state of the world in general and the rapidly deteriorating quality of software specifically, this bothers me. Out in the real world, built on decades of consistent use, these symbols have gained clearly defined meanings, and mounting and unmounting disks definitely isn't one of them. In fact, the meaning of these symbols isn't mere convention; they're defined in a variety of international standards for symbols for use in software and on equipment, such as ISO/IEC 18035 (which you need to buy to read; my copy fell of a truck): ISO/IEC 18035:2002 defines a consistent set of icons and related functions that are represented by multimedia applications on a computer screen and that users interact with to control such applications. It describes controls applying to such functions as: Play, Pause, Stop, Rewind, Scan forward, Scan backward, Replay backward, Loop, Go to beginning, Go to previous, Go to next, Go to end, Set volume and Mute. ↫ ISO/IEC 18035:2003 They're also part of ISO 7000/IEC 60417, a much larger, more encompassing standard that also contains things like the various symbols used on laundry machines, tumble dryers, in cars, and so on. The symbols themselves are much older than the standards, of course, with many of them dating back to the 1960s and possibly even 1950s. The point remains, though: the play and stop symbols have clearly defined meanings, and I don't think they are at all a good fit for mount and unmount. The function of the "play" symbol according to ISO/IEC 18035: To enable the user to start the presentation of dynamic media, except where the task requires automatic playing of that media. ↫ ISO/IEC 18035:2003 And of the "stop" symbol: To enable the user to stop the presentation of dynamic media. ↫ ISO/IEC 18035:2003 Neither of these descriptions match what mounting and unmounting mean or do. Mounting a drive or partition doesn't present any media at all; it merely makes the drive or partition in question accessible. Unmounting also doesn't eject anything; it merely makes the drive or partition inaccessible. I would argue that play and pause act upon contents of a drive or volume, and not upon the drive or volume itself. As it stands right now, you "play" a drive" to "play" a video stored on said drive. Madness. I already know what you're thinking, and yes, I agree that the Disks utility is a tool aimed at more advanced use cases and users, and most normal, average users will never even know it exists, let alone open it at all. Very few people get to see these symbols, and those that do already know full well what mounting and unmounting mean, reducing the importance of said symbols considerably. But now it's time for the big surprise, the twist in the story that turns this entire thing on its head. Files, GNOME's file manager, uses an entirely different symbol for unmounting! Instead of the "stop" symbol, Files uses the "eject" symbol. You may think this is a more accurate visual representation of what unmounting means, but I strongly disagree. Let's turn to ISO/IEC 18035:2003 once again: To enable the user to eject the current physical media from the appropriate drive. ↫ ISO/IEC 18035:2003 Unmounting doesn't eject anything! If you unmount a USB stick, the stick doesn't get fired out of the USB port. If you unmount a volume, it doesn't get removed from the SSD. Hell, if you unmount a CD-ROM, it doesn't even eject it! Ejecting a CD-ROM - opening the drive's tray or spitting the CD-ROM out of a slot-loader - is an entirely different act! Are we really "ejecting" a CD-ROM twice? Are we "mounting" a CD-ROM when we merely close the tray? No! Madness! The real underlying problem here is, of course, that mounting and unmounting are deeply weird and confusing concepts, bordering on the esoteric, that simply do not have physical equivalents to fall back on. Using symbols and iconography designed in the 1960s explicitly for playing music or stopping a video or ejecting a cassette tape are not a good fit for something as difficult to explain to most people as mounting and unmounting. It's like putting an eject symbol on a car's door handle or a play symbol on a soap dispenser. Should GNOME developers waste any time or resources to address this? No, of course not, that would be stupid. Nobody should care about this but me. I should suffer in silence, every time I need to mount or unmount something, forced to look for an eject or stop symbol in whatever user interface I happen to be using. Every time, I should die a little inside. Please, don't be like me and waste precious resources thinking about this. I'm not descending into madness. I just want mount and unmount symbols that make sense. I'm not descending into madness.

12 Nov 2026 10:13am GMT

We're almost halfway through November, but we hadn't seen Haiku's monthly activity report for October yet. It's here now, and there's quite a few good things in here, like support for two and three-finger tap gestures on touchpads for right and middle-click, a new driver that adds Universal Flash Storage support, and even some build fixes for Haiku's SPARC port as well as some fixes on the RISC-V side. Of course, that's just a selection, as there's the usual long list of smaller changes, bugfixes, and improvements as well.

11 Nov 2026 3:22pm GMT

Today, we're excited to announce the release of .NET 11! This year's release makes building modern applications faster, more productive, and has improvements across C# 15, ASP.NET Core, .NET MAUI, and Windows development. With hundreds of runtime optimizations, more responsive SDK tooling, and less overhead in everyday commands, you can spend less time waiting and more time creating. Build richer web and cross-platform applications, take advantage of new C# language features, and explore AI-powered development with improved tools and agentic capabilities. ↫ .NET Team I'm not going to pretend to care about .NET, but I know many of you have to care on a professional level, because .NET is remarkably popular in places where the spotlights don't often shine.

11 Nov 2026 3:13pm GMT

This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …

08 Oct 2026 12:00am GMT

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT