fidzu : computers

Google is launching its first Gemini-powered smart glasses, with Samsung supplying the computing hardware. Given their built-in 12-megapixel camera, Google is emphasizing privacy protections, including a tamper-resistant recording light, automatic face redaction, and restrictions on real-time facial recognition and livestreaming. The company also promises not to use captured photos or videos for AI training or targeted advertising. Ars Technica reports: Google says the frames all weigh about 41 grams, which is not terrible but is definitely near the top for glasses generally. They will, naturally, weigh much more when you account for lenses. That will also determine the final pricing. So far, we only have the starting prices for these devices, including non-prescription lenses. The setup here is similar to the Ray-Ban Meta glasses we've seen for a few years. There are no screens in the lenses, but you can interact with the AI system via voice or by activating the integrated camera. The experience should be similar to using Gemini Live on your phone, but it will be a lot easier to fire up the AI. You can say "Hey Gemini" or tap a touch-sensitive area of the frame to start interacting with the robot. Since this is the same chatbot that operates across the Google ecosystem, it has access to your data and preferences. You can ask questions and get personalized answers, have Google Maps guide you by voice, or just talk with the AI to kill time. The glasses use custom open-ear speakers to limit distractions for those around you. Google notes the directional microphones should not pick up speech from other people, either. Adding the camera feed is where things get interesting. When the AI can see what you see, it has the potential to do more work on your behalf. Google suggests asking Gemini for recommendations when looking at a bookshelf or glancing at an event poster to have the AI add it to your calendar. The glasses will also support Gemini Guided Vision, which provides conversational audio descriptions for people who are visually impaired. The new frames are available for preorder today starting at $395.

Read more of this story at Slashdot.

12 Nov 2026 7:00pm GMT

An anonymous reader quotes a report from The Conversation: On April 10 2019, the Event Horizon Telescope (EHT) Collaboration revealed the first picture of a black hole. The object is at the centre of a galaxy known as M87, about 55 million light-years away. The iconic ring structure instantly became one of the most recognized scientific images of the modern era. It showed a black hole "shadow" outlined by light from swirling hot gas -- just as predicted by Einstein's theory of general relativity. The result supported the long-standing idea that the centers of galaxies house supermassive black holes. However, scientists have since had some disagreements on whether the details and structure of the ring in the original publication were accurate. Our new research, published today in Nature, used new techniques to investigate the original datasets. Not only do our results validate the original work, but they also provide a fresh perspective on the ring structure. Our independent results enhance confidence in one of the most significant modern scientific results. And we bring the image of a black hole millions of light-years away back into focus. [...] When compared directly to images from the EHT collaboration, our result is consistent in diameter and overall orientation. Naturally, there are some differences in the fine details of ring width and surface brightness along the circumference, but the overall structure matches. This provides a fresh perspective on the iconic black hole ring while also resolving previous discrepancies. To prove this success didn't depend solely on advanced machine learning, we also developed a complementary imaging method based on traditional statistical techniques. This entirely different method also validated our structure using the new closure invariant data we produced. Overall, our work delivers a strong independent validation of the supermassive black hole structure at the centre of galaxy M87. And it could do more in the future. Our technique could also be useful in other situations where data from multiple sensors are combined to map unknown structures -- such as medical imaging or mapping earthquakes.

Read more of this story at Slashdot.

12 Nov 2026 6:00pm GMT

A critical flaw in Apache HTTP Server's HTTP/2 module could allow unauthenticated attackers to remotely execute code and potentially take control of affected server processes. Tracked as CVE-2026-119618, the vulnerability affects Apache HTTP Server 2.4.55 through 2.4.70 when HTTP/2 is enabled and is fixed in version 2.4.71. The Hacker News reports: The vendor's assessment, published yesterday, also says "public research has demonstrated a reliable exploit" against a server in its default configuration with mod_http2 enabled. It does not name or link that research. Security company Wiz said later that day that no exploit was available and that no exploitation in the wild had been reported. HTTP/2 runs only where the Protocols directive turns it on, as the module documentation explains. The directive uses h2 for HTTP/2 over TLS and h2c for HTTP/2 over plain TCP. It can be set for the whole server or for a single virtual host, so admins should check the server-wide setting and every virtual host. Standalone builds of the module, released on GitHub as mod_h2, are affected from version 2.0.8 through 2.0.42. Admins who run the Apache HTTP Server project's own releases should move to version 2.4.71, the fixed release named in its security advisory. That release also fixes a crash in mod_md, rated important, and a one-byte overwrite of stack memory in mod_vhost_alias, rated low.

Read more of this story at Slashdot.

12 Nov 2026 5: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