22 Nov 2026

feedUbuntu blog

15 years of long term support for bare metal automation with MAAS

Building modern AI supercomputing clusters, deploying 5G telecommunications networks, or operating High Performance Computing (HPC) data centers requires significant capital investment (CapEx). These investments are planned with a long-term horizon in mind, and the infrastructure management platforms supporting them often need to operate across multiple hardware generations. However, the software used to provision and manage […]

22 Nov 2026 10:30am GMT

feedLinuxiac

Libreboot Reverses AI Code Ban, Adopts Reduction Policy

Libreboot Reverses AI Code Ban, Adopts Reduction Policy

Libreboot reverses its total AI code ban, introducing a policy to reduce AI-generated contributions while allowing exceptions when necessary.

22 Nov 2026 10:25am GMT

feedHacker News

Harsher on Male? Evaluating LLMs on Gender-Asymmetric Moral Framing in Conflicts

Comments

22 Nov 2026 9:18am GMT

87% of the Anthropic power will come from gas and 11% from coal in 2028

Comments

22 Nov 2026 8:57am GMT

Notes on the discrete Fourier transform (DFT)

Comments

22 Nov 2026 6:52am GMT

21 Nov 2026

feedLinuxiac

DietPi 10.9 Released with Support for Five New Single-Board Computers

DietPi 10.9 Released with Support for Five New Single-Board Computers

DietPi 10.9 adds support for new Odroid and Orange Pi boards, expands its software catalog, and improves Raspberry Pi management.

21 Nov 2026 11:42pm GMT

KDE Releases Kwi 0.1, Its New GPU-Accelerated Terminal Emulator

KDE Releases Kwi 0.1, Its New GPU-Accelerated Terminal Emulator

KDE's new Kwi terminal emulator reaches version 0.1 with improved tabs, global menu support, interface refinements, and a Flatpak release.

21 Nov 2026 11:26pm GMT

feedOMG! Ubuntu

Kessler is an open-source, zine-style music player (with iPod support)

kessler is a new, open-source music player with a zine-style design, dithered album artwork and iPod support. It was also made with AI coding tools. Kessler's developer, Felix, an artist and designer from Germany, told me this upfront in an email, saying "like everyone on the internet right now i started making an application with the help of a coding assistant". He inherited an old iPod and found modern music player support for it was lacking I get a lot of software pitches now (more than at any point in my 16 years of blogging). AI agents don't sleep and […]

You're reading Kessler is an open-source, zine-style music player (with iPod support), a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

21 Nov 2026 5:30am GMT

20 Nov 2026

feedOMG! Ubuntu

Linux 7.3 is likely to be the next LTS kernel

The word LTS with Linux penguin mascot peeking outLinux 7.3 is looking like it'll be the new long-term support (LTS) kernel. Greg Kroah-Hartman, one of the kernels' key maintainers, intimated this in early November in a reply on the Linux Kernel Mailing List, discussing the status of Linux 7.4 and when it's likely to be released. In a reply to Linus Torvalds, who'd noted people were expecting Linux 7.4 to be designated an LTS (since it's shaping up to a big release and longterm kernels are picked, partly, based on being a feature-filled one) he said he planned for 7.3 to be LTS. "If people are trying to […]

You're reading Linux 7.3 is likely to be the next LTS kernel, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

20 Nov 2026 5:37pm GMT

19 Nov 2026

feedOMG! Ubuntu

Check if that bargain SD card or USB drive is fake on Ubuntu

Check if a bargain SD card or USB drive has fake capacity on Ubuntu using F3 (Fight Flash Fraud), an open-source Linux alternative to h2testw.

You're reading Check if that bargain SD card or USB drive is fake on Ubuntu, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

19 Nov 2026 11:54pm GMT

18 Nov 2026

feedUbuntu blog

Automating bare metal infrastructure in FIPS-regulated environments with MAAS

Organizations operating sensitive infrastructure, particularly in the government, defense, and financial services sectors, often face strict security and compliance requirements. These requirements extend beyond applications and operating systems (OSs) to the tools responsible for provisioning and managing the underlying physical infrastructure. The Federal Information Processing Standard (FIPS) 140-3 defines security requirements for cryptographic modules used […]

18 Nov 2026 10:26pm GMT

17 Nov 2026

feedJavaScript Weekly

The top 10 things AI gets wrong in web development

#​811 - November 17, 2026

Read on the Web

JavaScript Weekly

npkill 1.0: Not Just for node_modules Anymore - npx npkill has long offered a way to find and remove waste from node_modules folders. Its first release in two years now also hunts down caches and build outputs like .next and .turbo, with 'profiles' for 20 ecosystems. If you're new to the tool, its homepage provides a good introduction.

Juan Torres

Agents Didn't Clear Your Plate. They Dumped Reviews on It - Your agents write PRs in minutes, then eat your afternoon in review. When did 'saving time' start to mean babysitting agents' work? Meticulous shows the exhaustive impact of every PR, with no developer effort. Devs at Dropbox & ElevenLabs have their afternoons back. You can too.

Meticulous sponsor

UI SDK: Headless UI Behaviors for React, Vue, Svelte, & Solid - A new library from shadcn and Vercel that provides 50+ accessible, low-level behaviors, like roving focus, typeahead, popups, and drag and drop, that you compose into components (for several frameworks, plus Web Components).

Vercel

💡 𝕏 As shadcn says: "You and I don't need the same interfaces. We need the same interface behaviors." The idea is an agent, say, can generate whatever UI suits a task, with reusable focus, keyboard, and accessibility behaviors built in.

IN BRIEF:

RELEASES:

  • Prettier 3.10 - The code formatter now supports the latest JavaScript proposals and new Flow syntax, and adds an opt-in plugin that swaps in the Zig-based Yuku's JS/TS parsers for speed.

  • 🎨 p5.js 2.4 - The creative coding library expands its SVG and 3D model support. Here's a starter sketch if you want to play quickly.

  • 🔒 Node.js v26.13.1 (LTS), v24.22.3 and v22.23.5 - The security releases we mentioned last week fix an HTTP/2 flaw that lets clients crash a server and an HTTPS bug that can leak other connections' memory.

  • PixiJS 3D - The popular 2D rendering library's official 3D engine is now in open beta. It's WebGPU-first, with a WebGL 2 fallback.

📖 Articles and Videos

📊 e18e's Ongoing Benchmarks of JavaScript Meta-Frameworks - The e18e performance initiative tracks releases of frameworks across the ecosystem (e.g. Nuxt, Astro, SvelteKit, SolidStart, and more), measuring everything from install size and build times to rendering speed. This dashboard is the place to dive in.

e18e

🤖 The Top 10 Things AI Gets Wrong in Web Development - The Chrome team examines where coding agents fall back on dated techniques, like hand-rolled focus traps instead of inert and JS overlays instead of popover, alongside gaps in passkey implementations and XSS defenses. A handy checklist for humans too.

Philip Walton (Google)

AI Security for Modern JavaScript & TypeScript - Traditional tools miss logic gaps. SonarQube Hunter Agent catches broken access control in your JS/TS CI/CD pipeline.

SonarSource sponsor

How a Third-Party Script Turned Malicious on Major Sites - An attacker exploited a flaw in Optimizely's A/B testing platform to inject a (now removed) malicious script into pages served to end users. Scott's analysis found it on sites including Zoom, the BBC, and GitLab, and shows how CSP can, and did, help.

Scott Helme (Report URI)

💡 Third-party scripts are an increasingly common attack vector, as Polymarket's users recently found. If you load any, brush up on CSP and Subresource Integrity, and if you provide them, see how Fathom secures theirs.

How Promises Really Resolve, Explained via a WebKit Bug - A contrived promise that should have thrown instead caused Bun and Safari (both of which use JavaScriptCore) to hang. Alistair fixed the bug and uses it to explain what resolve() actually does and why resolved isn't 'a real promise state'.

Alistair Smith

The Web Is More Than Enough - A reminder of how the vast array of powerful web platform APIs enables the development of complex apps in the browser, particularly as AI reduces the headaches involved in tying them together.

Paul Ford

Your JS Error Is Lying to You - Why can JSON.stringify(err) unexpectedly leave you with {}? Gabor presents a tour of what an Error holds, and how much of that makes it through stack traces, cause chains, worker boundaries, and loggers like Pino and Winston.

Gabor Koos

📄 How 13,000 Local Variables in a Function Overflowed V8's Stack - And why would that ever happen? It was the output of an OCaml to JS transpiler… :-) Jérôme Vouillon

📄 A Universal XSS in uBlock Origin via Its Element Picker - Leans on an interesting (and now fixed) postMessage and iframe exploit chain. Smitty van Bodegom

📄 Migrating 10,144 Tests from Jest to Vitest in Three Weeks Daniele Rossino

🛠 Code & Tools

BrowserPod 4.0: A Linux-Like MicroVM for the Browser - A WASM-powered sandbox that runs Node, npm, git, and bash in the browser. Previously a metered service, v4.0 is free for any use, though it's not open source, and you must load it via their CDN (but no account or API key is needed).

Leaning Technologies

💡 Going somewhat deeper, Nitro creator Pooya Parsa has compiled the actual Linux kernel to WebAssembly (repo). It boots to a shell in under a second in modern browsers, or via npx unkernel (tip: use halt to exit!).

Debug Errors and Agents Faster: Sentry Changelog Live - A walkthrough of what's new in debugging, from fixing prod bugs with Seer to tracing your agents. Register today.

Sentry sponsor

Kitesurf: Cloudflare's Browser Engine Now Open Source - An experimental browser for agents we featured in August. Mostly written in TypeScript and runs JavaScript in V8 isolates on Workers, with Rust compiled to WASM for layout and painting. There's no Chromium, and Puppeteer can drive it.

Cloudflare

File Viewer: A Multi-Format File Viewer for Internal Apps - Read-only views for Office, PDF/OFD, CAD, archives, email and other complex formats, with integrations for React, Vue, and Svelte. The docs site has demos showing off the formats covered.

Flyfish Dev

Flashwright: A Faster, API-Compatible Playwright Fork - Keeps Playwright's API and test runner, but reuses a browser context per worker and doesn't wait for animations to settle, plus similar tricks. Benchmarks show a ~2-4x speedup, while this post explains how it works.

Codebeast

React Flow 13: The Node-Based UI Library Gets Faster - The first major release in two years cuts re-renders in large flows, with new useNode and useEdge hooks. Vue Flow has joined the xyflow family too.

xyflow

  • SlickGrid 6.0 (above) - Long-standing data grid component. Now with zero dependencies, plus pinning on all four sides and sticky rows and columns. Examples and introductions on the project homepage.

  • XState v6 Beta - First beta of the state machine/actor library's next major version. The core API is considered stable and you can try it with xstate@beta.

  • 🕹️ Excalibur 1.0 - After 13 years, the 2D TypeScript game engine reaches v1 with 2D lighting, a plugin API, and a rebuilt Web Audio mixer. Sample games here.

  • 🕹️ JSNES 3.0 - JavaScript NES emulator. Now has a cycle-accurate core that passes all 134 'AccuracyCoin' tests. There are playable demos here.

  • type-fest 6.0 - Popular collection of essential TypeScript types (listed here). v6.0 adds 120 new types and requires TypeScript 6.

  • Fontkit 3.0 - Advanced font engine for Node and the browser. Now ESM-only, with a new core export so you can ship only the formats needed.

  • dts-bundle-generator 10.0 - A tool to tree-shake and bundle a project's TypeScript declarations into one file.

📰 Classifieds

📄 Parsing PDFs for a RAG or invoice pipeline? Foxit compares 10 document parsing APIs on output format, billing units and accuracy claims.

🌙 Agents can test mobile code at 3am. Expo Simulators gives them cloud simulators, so the loop runs while you sleep.

Stop being the middle manager for your coding agents. CodeAF runs the org, and only what no manager can settle reaches you. #1 on DeepSWE.

📢 Elsewhere in the ecosystem

  • You Don't Need jQuery, the long-standing guide to replacing jQuery methods with plain JavaScript, has had a big v3.0 update. Internet Explorer fallbacks are out in favor of modern one-liners like el.replaceChildren(), structuredClone(), and Promise.withResolvers().

  • Adam Argyle shares PropFLIP, a take on FLIP (First, Last, Invert, Play) animations where four @property custom properties do the inverting and a CSS transition does the playing.

  • AWS has released AWS Emulator, an official local emulator you can point your AWS SDK or CLI at, covering hundreds of its service interfaces. It's largely aimed at agents, and was built with them too.

  • 🎂 Happy birthday to Svelte! Svelte turned ten years old on Monday (Rich Harris made its first commit on November 16, 2016).

17 Nov 2026 12:00am GMT

16 Nov 2026

feedKubernetes Blog

Scheduling the removal of the kube-proxy IPVS backend

The ipvs backend for kube-proxy was an experiment in providing a service proxy implementation with better performance than the iptables backend. While it succeeded in that goal, the kernel IPVS API has turned out to be a bad match for the Kubernetes Services API, and the ipvs backend was never able to implement all of the edge cases of Kubernetes Service functionality correctly.

In Kubernetes 1.29, the project introduced the nftables backend for kube-proxy, which became GA in 1.33. Part of the plan behind adding the nftables backend was the idea that it would eventually replace both the iptables and ipvs backends. Because the ipvs backend in particular is complex, not 100% feature complete, and architecturally quite different from the other two backends (and thus more work to maintain), Kubernetes SIG Network decided to officially deprecate it as of Kubernetes 1.35. Although it currently remains available in kube-proxy (with a warning about its deprecation), we (Kubernetes SIG Network) now plan to remove it in Kubernetes 1.40. All ipvs users should therefore be planning to migrate to either the nftables or iptables backends.

Why was the ipvs backend written?

The ipvs backend was originally designed to fix two different kinds of performance problems in the iptables backend:

The ipvs backend solved both of these scaling problems. The data plane problem was solved mostly automatically, because the kernel IPVS subsystem uses hash tables rather than linear lookup. The control-plane problem was solved by not rewriting the entire ruleset on every update. (The kernel IPVS API doesn't have a way of doing batch updates anyway, so this was essentially forced.)

Why is the ipvs backend now being deprecated?

Almost from the start, the ipvs backend also had problems.

The first version didn't have 100% compatibility with the iptables backend, but it was assumed that this would be fixed over time. Unfortunately, the original authors moved on to other things outside the Kubernetes ecosystem (as inevitably sometimes happens in open source), and it took a while to find new people interested in maintaining the code.

Meanwhile, as people began using the ipvs backend in larger and larger clusters, its own scaling problems started to emerge. In particular, the lack of batch update operations in the IPVS API meant that while the ipvs backend was faster than iptables when making a few small changes, it was potentially slower when making a large number of changes at once. And because the IPVS API is fairly limited in what it can do, kube-proxy's ipvs backend needed to fall back to using iptables to implement various features of Kubernetes Services beyond basic "load balancing", making it run into some of the same scaling problems the iptables backend has. While the ipvs backend tried to mitigate this by using ipset for some of its rules, this again ran into the problem of not having a batch update API. Additionally, the fact that the ipvs backend uses iptables means that it has the same long-term support problem as the iptables backend: Red Hat's plan to remove the iptables API entirely from Red Hat Enterprise Linux means the ipvs kube-proxy backend will also no longer be available to Kubernetes users on RHEL.

What about IPVS schedulers?

Beyond performance, the other reason some users were excited about the ipvs backend was the ability to pick from among various IPVS "schedulers" for distributing traffic to endpoints, rather than relying on the simple random selection used by iptables (and nftables).

Unfortunately, the way IPVS is used by kube-proxy prevents it from being able to use most of the IPVS schedulers in a useful way. The problem is that kube-proxy is a distributed service that runs on all nodes in the cluster, but the kube-proxy processes on different nodes do not share their IPVS scheduler state, so each node picks endpoints without knowing what is happening with clients on any other node. Even the schedulers that are designed to work in a distributed way generally don't work better than random selection in the context of kube-proxy. For example, the mh scheduler uses Maglev Hashing to select endpoints, which theoretically allows for extremely efficient distributed load balancing. But that efficiency is only in the context of a specific sort of two-layer load-balancer design, and kube-proxy does not have the right architecture to be able to act as either of the two layers in that design.

Switching away from ipvs

Switching to nftables

If you are running Kubernetes 1.36 or later, and your nodes are running a Linux distribution with kernel 5.13 or later, and you use the ipvs proxy mode, then Kubernetes recommends switching to the nftables mode of kube-proxy. (Although the nftables backend is GA -and fully usable-as of Kubernetes 1.33, there have been some performance- and scaling-related fixes since then that that weren't backported to releases earlier than 1.36.)

The nftables backend is fully supported, feature-complete, and even has very slightly better performance than ipvs:

kube-proxy ipvs-vs-nftables first packet latency, at various percentiles, in clusters of various sizes

(Taller bars represent longer latency. The "p50" group is the average connection establishment latency. Note that even the largest numbers in this graph are quite tiny; the point is not to claim that nftables is (noticeably) faster than ipvs, just to show that, unlike iptables, it's not slower.)

Switching is as easy as changing the kube-proxy configuration and restarting kube-proxy. For example, in clusters deployed via kubeadm, change mode: ipvs to mode: nftables in the kube-proxy ConfigMap and then restart the kube-proxy pods, as described in the documentation on reconfiguring a kubeadm cluster. (If you are overriding other ipvs-specific kube-proxy configuration, you will also need to change those options to the corresponding nftables ones.)

Switching to iptables: "It's Not As Slow As You Think!"

If you can't switch to nftables, either because you are on an older version of Kubernetes, or because your cluster runs on an older Linux distribution that isn't new enough to support the nftables backend, you may be able to just switch to the iptables backend, which has improved greatly since the original creation of the ipvs backend in 2017:

The net result of this is that the iptables backend of 2026, while still not as good as the ipvs backend, is at least much better than the iptables backend of 2017 was, and many people who found iptables unusable in the past would not have problems with it now.

As with switching to nftables, switching to iptables is mostly just a matter of updating your kube-proxy configuration, although for technical reasons, in this case we recommend that you reboot each node after changing the kube-proxy configuration, rather than merely restarting kube-proxy.

Learn more

16 Nov 2026 6:35pm GMT

13 Nov 2026

feedUbuntu blog

From desktop to cloud to road

In an era where software defines vehicle value, engineering teams face a friction bottleneck. They spend hours fighting dependency conflicts, toolchain mismatches, and integration failures instead of writing vehicle features. As vehicles effectively become data centers, teams waste hours resolving dependency conflicts across desktop workstations, cloud, and physical targets. This article explores how establishing consistency […]

13 Nov 2026 9:31am GMT

10 Nov 2026

feedJavaScript Weekly

How X (Twitter) is rebuilding its web app

#​810 - November 10, 2026

Read on the Web

JavaScript Weekly

How X (Twitter) is Rebuilding Its Web App - X is replacing 3 servers with one app built on React, Vite and Fastify. Yagiz, famed for his performance work on Node, explains the streaming architecture behind it, along with some bottlenecks they had to fix, like how hundreds of tiny JavaScript files slowed startup.

Yagiz Nizipli (X Engineering Blog)

Why Standard Webhooks Hit 118m npm Downloads a Month - OpenAI, Anthropic, and Gemini all sign webhooks with Standard Webhooks, the open spec Svix started. That's one finding in the State of Webhooks 2027, where we scored 489 API companies on retries and signatures. Immediate download, no email required.

Svix sponsor

Parcel 3 Alpha: The Bundler Rewritten in Rust - A ground-up Rust rewrite of the popular bundler that the team reports is up to 100x faster than Parcel 2 at cold builds of React Spectrum. It runs as a standalone binary without Node, with support for native plugins written in Rust, Go or Swift, while JavaScript plugins run on an embedded QuickJS runtime.

The Parcel Team

IN BRIEF:

RELEASES:

📖 Articles and Videos

Experiments with Multithreaded JavaScript - What would JavaScript look like if threads could share objects directly? Former TC39 delegate Erik Arvidsson explores three approaches: in a Porffor fork, as a TypeScript library with an ownership checker, and as an implementation of the TC39 structs proposal. Each has a playground to try.

Erik Arvidsson

The New JavaScript Features Between V8 14.6 and 15.6 - Node 27, released in alpha recently, is built on V8 15.6, and Joyee tours what that brings to developers, including Math.sumPrecise, new iterator methods, and some behavior changes in sorting, dates and promises, all with sample code.

Joyee Cheung

How to Build Your Own Automated Debugging Workflow - Connect your coding agent to Sentry and turn errors into fix PRs. See the guides and recipes in the resource hub.

Sentry sponsor

Spreading Liquid with three.js - A technical explanation of a 'liquid-spreading' effect originally built for a cosmetics site. The in-page demo is fun to play with and this could be handy if you want to create paint-like effects.

Misaki Nakano

Reviving Facebook's Abandoned JavaScript Optimizer - Prettier creator James Long put agents to work resurrecting Prepack, Facebook's attempt to make JavaScript faster by running it ahead of time. There's an experimental demo that shows off the gains on a sample React app.

James Long

Yavashark: Building a JavaScript Engine for 950 Days Straight - A solo developer's progress report on a Rust-based engine they're building that passes around 82% of test262 and can server-render a React app. There's a playground to try it for yourself.

Sharktheone

📄 A Fifth Object Shape Made the Same Loop Twice as Slow - V8's hidden classes and inline caches in action. Mohsen Fallahnejad

📺 ReactiveScript: Early Findings - A lengthy stream by Solid's creator on ReactiveScript, his experimental reactive UI language he first shared in 2021. Ryan Carniato

🛠 Code & Tools

EmbedPDF 3.0: A PDF Viewer for Any JavaScript App - An open-source PDF viewer for vanilla JavaScript, React, Vue, Svelte and Angular. The v3 rebuild offers a ready-made viewer, headless components for custom UIs, and a standalone PDF engine. Try the demo.

EmbedPDF

Embed an Office Editor Your App's AI Agent Can Use - DOCX/XLSX/PPTX editing in your app with your model and workflow. Agents make targeted edits, and users refine the file.

Thinkfree sponsor

chrome-capture: Record a Chrome Tab at 60-120fps to an MP4 File - It's been three years since we've linked to Paul Irish (once a frequent fixture in JavaScript Weekly!) but he's back with a neat, compact tool you can run with npx to record a Chrome tab at high quality including audio to an MP4 video.

Paul Irish

Text.js: React Apps That Render in the Browser Console - Really! A React 19 framework whose 'screen' is the DevTools console, with routing, keyboard input, layout primitives and ASCII fonts. Open the console on the homepage to try it, then bunx create-text-app if you're tempted. GitHub repo.

Anomaly

Jeasx 3.0: Server-Rendered JSX, Now Streaming - A minimal framework that uses JSX purely as a server-side templating language (with no React and no hydration) on top of Fastify and esbuild. v3 streams pages while async components are still loading and renders ~2x faster. Live examples.

Jeasx

  • Rolldown 1.3 - The Rust-powered bundler adds experimental support for import attributes, but there are breaking changes to be aware of.

  • jsdom 31.0 - The pure JS implementation of DOM/HTML standards adds a new CSS engine and switches to a Skia-backed canvas backend.

  • Remix 3.2 - The full-stack framework adds nonce-based Content Security Policy middleware.

  • Wiki.js 3.3 - Open source JavaScript and Node.js-powered wiki app.

📰 Classifieds

📺 JetBrains AI.js Day 2026: Frontend's scariest AI questions answered live on channel 13, Nov 13. Register now!

🔑 One subscription, a dozen people. Fingerprint shows how many devices are really behind each account. Try it free.

📢 Elsewhere in the ecosystem

10 Nov 2026 12:00am GMT

03 Nov 2026

feedJavaScript Weekly

What Claude spends building with 12 JavaScript stacks

#​809 - November 3, 2026

Read on the Web

JavaScript Weekly

The AI Cost of JavaScript Frameworks

Nolan Lawson had Claude build the same app five times in each of twelve JS stacks to test common "X is better for agents" claims. Costs varied significantly between runs, and Gautam Parab found that the observed cost ranges overlapped or touched for most pairs of frameworks.

But a clearer difference was in the median amount of JavaScript sent to browsers: 0KB for Astro, 18K for Hono+htmx, 36K for SvelteKit, and 115-142K for React Router, TanStack Start and Next.js. If you've gone "hands-free", Nolan asks, why stick to a particular stack you chose when you wrote all the code? His benchmark is on GitHub to try for yourself.

Nolan Lawson

Run AI Coding Models on Your Own Machine - Local models are now good enough for everyday coding. Learn to run them on your own Mac or GPU, wire them into your editor and terminal agents, and keep your code private with no per-token bill.

Master.dev sponsor

Why Is This Fingerprinting Script 'Creating Bioweapons'? - A crawl of sites to collect canvas fingerprinting examples (which you can see, visually, at fingerprint.garden) found an anti-analysis technique where JavaScript identifiers were named after… taboo topics, with a prompt hidden in invisible Unicode, all designed to make LLMs refuse to work on the code!

Veritas

💡 Canvas fingerprinting is a technique that uses quirks of how different clients render canvas elements, in order to distinguish browser environments.

IN BRIEF:

RELEASES:

📖 Articles and Videos

"No, npm, 'estee' is not a typo of 'testem'" - Shane tried to publish a CLI called estee and hit npm's typosquatting filter, which (as best as we can tell) rejects names within a small Levenshtein distance of popular packages' names.

Shane Friedman

Shrinking clarity.js: When Cleaner Code Gzips Worse - Microsoft let an agent run 50+ size experiments on its analytics script. A big win came from dropping import * namespace objects, while good-practice refactors like extracting helpers actually made the gzipped output bigger.

Manu Nair (Microsoft)

Workshop: How to Implement Session Replay - Filters, custom tags, and sampling settings for finding the sessions that matter. Nov 5, 10am PT.

Sentry sponsor

'Nothing Installs at Our Company Until It's a Week Old' - Many recent package hijacks were caught within hours, so Bruno's company now makes new releases wait a week. He explains what this approach broke, what cooldowns don't stop, and settings for popular package managers.

Bruno Jurković

Timing Ten Design Systems, Then Fixing the Slow Ones - Den timed ten design systems (MUI, Ant Design, and Ionic among them) opening a 249-option select and ticking 100 checkboxes, then profiled the slow ones to find out why.

Den Odell

Using Bun? Dependabot Can't See Most of Your Dependencies - GitHub's dependency graph doesn't parse bun.lock, so Dependabot alerts cover only direct dependencies. Nicolas has some tips for improving matters.

Nicolas Charpentier (Shortcut)

📄 How Hard Is It to Check for Whitespace? - Why Java, Python and JavaScript disagree on what counts as whitespace. Sergey Tselovalnikov

📄 A Proposal: How to Hire Junior Engineers in the Age of AI - The npm co-founder thinks traditional coding interviews are dead. Laurie Voss

📄 How to Make postMessage Type-Safe in Under 350 Bytes Pavel Grinchenko (Evil Martians)

📄 The Web Can't Afford a JavaScript Runtime Monoculture Kate Holterhoff (RedMonk)

🛠 Code & Tools

Handwired: Compile Regular JavaScript into a Neural Net - A new mind-bender from Pretext's creator: a compiler that turns JavaScript into an exact network of ReLUs and matrix multiplies that run on the GPU. Demos include a 130-layer 'mini desktop' and a WebGPU search over 100K JSON documents.

Cheng Lou

Build Smarter JavaScript Applications With Live Search Data - Add search, shopping, maps, news, trends, flights and hotels results with a single developer-friendly JavaScript SDK.

SerpApi sponsor

🌐 x18n: Lint and Maintain i18n Files for Any Framework - Anthony Fu's successor to i18n-ally scans locale files and translation calls and reports missing, unused and broken keys (like how tsc --noEmit reports type errors).

Anthony Fu

djs: A New 'Suspend Anywhere' JavaScript Engine - Armin (of Flask fame) built an engine to run scripts in WebAssembly that can snapshot the VM's state and resume elsewhere, even mid-await.

Armin Ronacher

webframe: Run a Web Page Like a Command-Line Program - Point it at a URL or HTML file and it runs the page in a hidden system web view, piping console.log() to stdout and exceptions to stderr. No bundled browser or Playwright needed.

Jeff Lindsay

phoria2: A Small WebGL 2 Library for 3D Charts - A dependency-free 3D library aimed at dashboards and product viewers, with an API you can 'learn in an afternoon'. Plenty of live demos on the page.

Kevin Roast

  • Shiki 4.6 - Powerful code syntax highlighter, now with faster decoration handling and compressed Oniguruma WASM binary.

  • Preact 11.1 - A new preact/compat/compiler-runtime entry point lets code compiled by React Compiler run on Preact too.

  • Postgres.js 4.0 - The popular Postgres client for Node, Bun and Cloudflare Workers gets a rewrite and goes ESM-only.

📰 Classifieds

💸 Every OTP you send costs money. Fraudsters trigger them by the thousands. Fingerprint recognizes the device before you text. Learn how.

Your coding agent can write the app. Expo is the agentic mobile infrastructure that takes it from a repo to the App Store.

CodeAF fixed 2x OpenCode's issues and nearly 4x Claude Code's on the same open model, at up to 4.8x less per fix. Open source, Apache 2.0.

📢 Elsewhere in the ecosystem

03 Nov 2026 12:00am GMT

29 Oct 2026

feedKubernetes Blog

From Working Group to SIG Architecture: spotlight on AI Conformance

In this SIG Architecture spotlight we talked with Janet Kuo (Google) and Yuan Tang (TensorScale AI) about the journey of AI Conformance in Kubernetes, from the initial Working Group to the integration SIG Architecture as a subproject.

Introductions

Frederico Muñoz and Kirti Goyal (FK): Hi Janet, Yuan, and thank you for the opportunity to learn a bit more about AI Conformance. Can you tell us a bit about yourselves and how you got involved in Kubernetes?

Janet Kuo: I'm a Senior Staff Software Engineer at Google and have been a Kubernetes maintainer since 2015, joining the community just as we were racing toward the 1.0 launch. I started my journey writing the core workload controllers that standardized how applications are orchestrated on Kubernetes. Today, I lead SIG Apps as a Co-chair & TL, and also lead the AI Conformance program. My current focus is to ensure Kubernetes remains the best platform for the next generation of workloads, such as AI.

Yuan Tang: I'm a co-founder of TensorScale AI where we build AI infrastructure for world models. Prior to that, I was a Senior Principal Software Engineer at Red Hat, where I led the development of Red Hat AI platform and upstream open source strategy. I became involved in Kubernetes early on by fostering collaborations between the Kubernetes community and projects I was leading, including Kubeflow, Argo, and KServe. I later helped found and lead WG Serving and the AI Conformance program, advancing innovation and strengthening community collaboration around running AI workloads on Kubernetes.

Program, Working Group, Subproject: the many shapes of AI Conformance

FK: AI Conformance started as a CNCF Program, was it then you got involved?

Janet Kuo: I was actually involved from day one since I pitched the original idea. It became obvious then that everyone was starting to run AI on Kubernetes, but vendors were building their infrastructure stacks in different ways. I got worried about ecosystem fragmentation. So I wrote up the initial Kubernetes AI Conformance Proposal, took it to the CNCF leadership to get their buy-in, and started the AI Conformance Program. Once we had the green light, I reached out to my fellow co-chairs Yuan Tang, Rita Zhang, and Mario Fahlandt to get the community rallied around it.

Yuan Tang: Yes. I was a co-chair of WG Serving at that time and some of the initiatives such as the Gateway AI Inference Extension quickly gained traction. There was a strong interest among the community to include inference-related requirements in the Kubernetes AI Conformance program.

FK: How would you describe the motivation behind the creation of the AI Conformance Working Group?

Janet and Yuan: The motivation behind creating the Kubernetes AI Conformance Working Group (AI WG) was to address the rapid convergence of AI workloads onto Kubernetes while preventing ecosystem fragmentation.

As AI adoption accelerated, organizations began running increasingly complex workloads, including distributed training, large-scale inference, GPU-intensive pipelines, and emerging agentic AI systems across many different Kubernetes platforms. However, vendors were implementing AI infrastructure capabilities differently, especially around GPUs, networking, scheduling, and inference orchestration. That created portability challenges, operational inconsistency, and growing vendor lock-in concerns.

The AI WG was formed to bring the community together around:

FK: WGs are temporary by nature, based on outcomes: would you say the main goals of the WG were achieved?

Janet and Yuan: Yes, the WG achieved its primary initial goals.

The WG has succeeded in moving the ecosystem from: fragmented, vendor-specific AI infrastructure approaches to a shared, community-defined baseline for AI workloads on Kubernetes.

Some concrete indicators of success include:

Most importantly, the WG created consensus that AI workloads are now a first-class Kubernetes use case.

KubeCon stage with 4 persons in it, one of them talking.

FK: AI Conformance was specifically highlighted at the latest KubeCon: is this a reflection of the growing importance of AI throughout the project?

Janet and Yuan: Yes, the prominence of AI Conformance at the latest KubeCon + CloudNativeCon is a strong reflection of how central AI has become to the Kubernetes ecosystem overall.

A few years ago, AI workloads on Kubernetes were still viewed as somewhat specialized, mostly tied to ML platforms or GPU-heavy research environments. What's changed is that AI is now becoming a mainstream infrastructure concern for nearly every large-scale platform operator.

That shift naturally elevates AI from an application running on Kubernetes to a core workload category Kubernetes must optimize for.

The AI Conformance initiative reflects that evolution. It signals that the community now sees AI infrastructure requirements, things like accelerator scheduling, high-performance networking, workload-aware orchestration, and low-latency inference, as important enough to standardize at the ecosystem level.

Its visibility at KubeCon also shows a broader strategic realization: if Kubernetes is going to remain the universal control plane for modern infrastructure, it needs to provide a consistent foundation for AI workloads across clouds, on-prem, and edge environments.

So the emphasis on AI Conformance is not just about chasing AI hype; it's about Kubernetes adapting to a major shift in workload patterns and ensuring the ecosystem evolves cohesively rather than fragmenting into vendor-specific AI stacks.

(slide) Initial adopters and major contributors: Akamai (logo), Alibaba Cloud (logo), AWS (logo), Broadcom (logo), CoreWeave (logo), DaoCloud (logo), Google Cloud (logo), Kubermatic (logo), Microsoft Azure (logo), NVIDIA (logo), Oracle (logo), SUSE (logo), Red Hat (logo), SAP (logo)

From Working Group to SIG Architecture subproject

FK: How would you describe the change from WG to SIG? Is it a reflection of AI as something that requires ongoing architectural governance?

Janet and Yuan: In Kubernetes, Working Groups are meant to be temporary. Our WG had a specific goal to get the initial Kubernetes AI Conformance requirements published and get the certification process off the ground. Once we hit those milestones, we archived the WG and moved AI Conformance to be a permanent subproject under SIG Architecture.

Moving to SIG Architecture definitely proves that AI needs ongoing governance. AI isn't just a passing trend or a one-off workload. It has become a core part of what Kubernetes runs every day. Because SIG Architecture already owns overall Kubernetes Conformance and API design principles, housing the AI Conformance subproject there makes perfect sense. It makes sure our AI Conformance requirements stay aligned with the rest of the Kubernetes ecosystem for the long haul.

FK: And with that change, how would you describe the main goals and areas of intervention of the subproject?

Janet and Yuan: Now that we're a subproject, our main goal is to keep the AI Conformance standards current, vendor-neutral, and standard-setting. We want to make sure Kubernetes captures the latest advancements in AI infrastructure while keeping the ecosystem fair for everyone. When we find gaps where no clear community pattern exists, we help foster and form new standards to solve them.

AI Conformance and Kubernetes

FK: AI Infrastructure is evolving very quickly, while Kubernetes APIs are designed to remain stable for years. Is this something you consider a challenge?

Janet and Yuan: It's definitely a tricky balance. AI moves very fast, while Kubernetes is designed to be stable and boring. But we actually structured the program around this exact tension.

First, we use a tiered graduation model. When new AI infrastructure concepts emerge, we introduce them as recommended SHOULD requirements. That gives the ecosystem room to experiment and agree on best practices without locking Kubernetes into rigid APIs too early. Once those APIs stabilize and with ecosystem adoption, we graduate them to mandatory MUST requirements.

Second, we intentionally keep our focus on the infrastructure layer. We test for core capabilities like accelerator support through Dynamic Resource Allocation (DRA), rather than getting bogged down in specific AI frameworks or model servers. That keeps the base platform stable while letting the AI tooling evolve as fast as it needs to.

FK: DRA has evolved, also due to the work of WG Device Management, as an important part of Kubernetes (and especially so for AI workloads), with SIG Architecture having an important role in how it's integrated in Kubernetes: do you find any parallel in this? Specifically, do you think there will be a heavier focus in the integration with the evolving Kubernetes architecture as part of SIG Architecture?

Janet and Yuan: There is a huge parallel there. Whenever we face a massive, complicated challenge that touches multiple parts of the codebase and involves multiple SIGs, a Working Group is the best place to start. It lets experts from different SIGs get together to figure out the problem, and build consensus.

Being part of SIG Architecture means there will be a much heavier focus on how AI capabilities weave into the evolving Kubernetes architecture. Instead of treating AI as an add-on layer, we're looking at how core Kubernetes primitives, like scheduling and resource allocation, need to adapt at a foundational level to support the next decade of AI workloads.

Final remarks

FK: For interested contributors, what's the best way to get involved with the AI Conformance subproject?

Janet and Yuan: We're always looking for new contributors. The easiest way to get started is by checking out our main repo at kubernetes-sigs/ai-conformance and join our meetings. If you're interested in defining new AI Conformance requirements, you can jump into PR reviews or propose your own using our KAR template. If you want to write code, we always need help expanding our automated Go test suites in the test/ directory.

For vendors looking to certify their platforms, all the details are at cncf/k8s-ai-conformance.

FK: Any final comments you would like to share?

Janet and Yuan: We've been blown away by how fast the community has rallied around this. When we first announced the AI Conformance program during the keynote at KubeCon NA 2025, we weren't sure what the response would be. But by the time we gave our update keynote at KubeCon EU 2026, we had grown from 18 certified platforms to 31 in just a few months.

That kind of growth shows just how much the industry wanted a unified, vendor-neutral standard. It gives organizations the confidence that they can run their AI workloads on any certification Kubernetes platform without getting locked into a proprietary stack.

If you're a platform vendor, we'd love to see you get certified. If you're a developer interested in the intersection of AI and cloud-native infrastructure, come join us in SIG Architecture!

FK: Excellent, thank you both for guiding us in this journey on AI and AI Conformance in Kubernetes.

29 Oct 2026 5:00am GMT

27 Oct 2026

feedKubernetes Blog

Announcing the Workload Conformance Working Group

We are excited to announce that the Kubernetes community now has a Workload Conformance Working Group. The working group is writing a shared standard for how workloads behave at runtime on Kubernetes. To get it right, we need input from the people who build those workloads and from the people who run the clusters they're deployed on.

Why workloads need a shared standard

Certified Kubernetes tests the cluster, and Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads. Nothing comparable exists for the workloads themselves, so cluster operators still check each application by hand before routine maintenance or a Kubernetes upgrade.

The problems they find are familiar. A routine node drain is often how you discover that an application can't tolerate disruption. An upgrade can break an application that still depends on a removed API version. Others show up in day-to-day operation: workloads that ask for privileges they don't need, or reserve resources they never use.

Kubernetes already documents much of this, including security and handling disruptions. Even so, every cluster operator ends up repeating the same assessment, and application maintainers get the same questions from each environment they support. A common specification with repeatable tests would give both groups the same baseline to start from.

What the working group will deliver

The charter sets out three deliverables:

The first step is deciding which workloads and behaviors the specification covers. The scope includes security, resilience during disruptions, resource use, networking, storage, API usage, and observability, but the group hasn't yet agreed on specific requirements or on how to test them. However, one rule is already set: every requirement needs an objective test that a test binary can run, so nothing subjective goes into the specification.

The specification covers how a workload runs, and importantly not what it does. Consequently, application logic is out of scope of workload conformance. The binary won't retest anything Certified Kubernetes already covers, and it won't require a particular workload packaging format, or vendor tool like policy engine, security scanner, etc.

How the work is organized

Two Special Interest Groups (SIGs) are sponsors for the working group.

Whenever a requirement touches another Kubernetes SIG's area, such as node behavior or networking, the working group will initiate conversations with those SIGs as well.

The working group is a forum where SIGs can get involved and shape the direction of Workload Conformance while the specification is being written. We're aiming for a stable first specification and working tests within two to three Kubernetes release cycles.

Get involved

The specification will and needs to be built from real examples, so we want to hear your experiences. If you run clusters, tell us how you assess workloads today and what broke during your last upgrade or maintenance window. If you maintain an application, tell us what it needs from the cluster and where the existing guidance left you guessing.

You can find us in #wg-workload-conformance on Kubernetes Slack (visit slack.k8s.io for an invitation) and on the mailing list. The working group meets every other Wednesday at 15:00 UTC. The Zoom link and the agenda are in the meeting notes. If you want to raise a topic, add it to the agenda. Joining the mailing list usually adds the meeting invite to your calendar.

Thanks to everyone who reviewed and supported the working group proposal.

27 Oct 2026 4:30am GMT