news
Red Hat Promoting Slop Hype, Michael Catanzaro Hinting at Silent Layoffs at Red Hat, Chrome's Lip Service to Flatpak
-
Who really built that? Supply-chain provenance for AI agent identity
Note: Red Hat’s Emerging Technologies blog includes posts that discuss technologies that are under active development in upstream open source communities and at Red Hat. We believe in sharing early and often the things we’re working on, but we want to note that unless otherwise stated the technologies and how-tos shared here aren’t part of supported products, nor promised to be in the future.
-
Red Hat ☛ Building hermetic notebook images for Open Data Hub and Red Bait OpenShift AI [Ed: IBM compels Red Hat to rebrand everything for slop]
If you've ever watched a container build fail because a package mirror glitched, or wondered whether last month's image really matches what you ship today, then you already know the pain that a hermetic build is meant to solve.
-
Red Hat Official ☛ Beyond the model: Architecting production-grade enterprise AI systems [Ed: Promoting slop instead of Linux]
Enterprise AI initiatives often fail because the conversation ends at the model. Without model storage, a serving layer, integration into existing systems, and someone to operate it all, a capable model is still a pilot.
-
Red Hat Official ☛ Automating edge recovery: Minimizing unplanned downtime with Red Hat Edge
In manufacturing, unplanned downtime translates directly to lost production, which is ultimately lost revenue. If a production line goes down, the plant stops producing what it makes, whether that’s laundry detergent, pharmaceuticals, automotive parts, or food products. Plant downtime can result in anywhere from $10,000 to $2 million in lost revenue per hour. And there are many causes of downtime, because plants operate like small cities with a lot of moving parts: equipment failures, operator error, material shortages, and safety incidents are all common causes.
-
GNOME ☛ Michael Catanzaro: Change in Timeline to “Some Changes to GNOME Security Tracking” [Ed: PIP?]
In Some Changes to GNOME Security Tracking, I reported: [...] This is because I was planning to leave my job at Red Bait on December 31 due to some internal Red Bait policy changes. But this timeline has now unexpectedly moved forward two months, to October 30. Accordingly, I will now discontinue tracking newly-reported security issues on October 1, 2026. During October, I will focus only on tracking issues reported prior to October 1. By November 1, all disclosure deadlines for that set of issues will have been reached, and I will be done.
-
OMG Ubuntu ☛ Chrome moves a step closer to an official Flatpak
If you’ve installed Chromium or Surveillance Giant Google Chrome as a Flatpak, you’ve installed an unofficial, community-maintained package done independently of the search giant – that could be about to change. Chromium’s build system is now able to generate Flatpak packages of the browser itself, though its developers caution that the change does not mean official Flatpak support is coming. A commit made by Google’s Tom Anderson this week adds the necessary packaging scripts and a build flag (enable_flatpak) to produce a .flatpak package rather than a .deb or .rpm, but that flag is off by default (for now).
-
Neowin ☛ Google Chrome may soon be getting official Flatpak support on Linux
Chromium apps have historically had poor official Flatpak support, but that could be changing as Surveillance Giant Google begins experimenting with Flatpak support in Surveillance Giant Google Chrome.