# standard Published articles for standard. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The skills CLI now supports Notion hosted skills DevFeed: [The skills CLI now supports Notion hosted skills]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-09-17T18:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Notion](), [Command-line interface](), [API](), [personal access token](), [standard]() Tags: [agent](), [agent-skills](), [api](), [cli](), [commands](), [install](), [integration](), [notion](), [permissions](), [personal-access-token](), [skills](), [standard]() ### AI overview The skills CLI now supports Notion-hosted skills as an installation source. Teams can author, review, and update reusable agent skills in Notion, then install selected skill packs or individual skills through the CLI. Authentication uses a Notion personal access token and respects Notion page permissions. ### Source excerpt skills@1.7.0 adds Notion skills databases as an install source for agent skills . Notion skills are reusable agent skills written as Notion pages. Teams author, review, and update them in the workspace they already use, then install them into any agent the skills CLI supports. No Git repository required. To browse your Notion workspace's skills, run: The CLI lists the skill packs shared with you and installs every skill in the packs you select. To install a single skill, pass its Notion page URL: Both commands use the Notion CLI (ntn) to authenticate. To set it up: ntn login requires a Notion personal access token, so your workspace must allow them. Access follows Notion's page permissions. You only see skills shared with you, so controlling who can install a skill is the same as controlling who can view the page. This integration is built on Notion's new Agent Skills API, which exposes skills stored in Notion as standard Agent Skills folders. Because the format is standard, the same skills work in any agent that reads them. Get started by creating a Notion skill. Read more ## Measuring and Improving Consistency in Repeated Agent Runs DevFeed: [Measuring and Improving Consistency in Repeated Agent Runs]() Original publisher: [Read original article]() Author: Evelyn Duesterwald; Lilian Ngweta; Vatche Isahagian; Jayaram Radhakrishnan; Vinod Muthusamy; Gaodan Fang; Ashwath Vaithinathan Aravindan; Punleuk Oum; G Thomas; Merve Unuvar; Ayhan Sebin; Michał Ulewi Published: 2026-09-15T16:00:44Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [Benchmark](), [Ground truth / benchmark quality](), [model-deployment]() Tags: [agent](), [benchmarks](), [consistency](), [evaluation](), [gpt](), [inference](), [leaderboard](), [model](), [reports](), [standard](), [technical]() ### AI overview This article presents the Consistency Analyzer, a diagnostic for finding decision points where an agent's behavior may change across repeated runs. It introduces consistency guidelines in ALTK-Evolve and reports that they reduced the consistency gap from 24.4 percentage points to 12.0 points without reducing average accuracy. ### Source excerpt That is embarrassing onstage. In production, it is a reliability problem: a workflow that succeeded once may fail the next time a user makes the same request. For mission-critical work, such as reconciling a financial transaction or checking a contract for an obligation, that can be a showstopper. Most benchmarks hide this variability behind an average. On AppWorld, a ReAct agent using GPT-4.1 succeeded on 77.4% of runs across five repetitions. ## Standardizing Exception Message Style in Ruby DevFeed: [Standardizing Exception Message Style in Ruby]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-09-05T00:00:00Z Content type: article Language: en Sources: [Daniel Doubrovkine]() Topics: [Ruby](), [Exception](), [ci]() Tags: [ci](), [exception](), [exceptions](), [grape](), [lint](), [open-source](), [plugin](), [ruby](), [standard]() ### AI overview The article explains a convention for Ruby exception messages: they should generally begin with lowercase and omit trailing punctuation because they follow the exception class name and a colon. It describes fixing seven inconsistent sites in Grape, documenting the convention, and releasing the rubocop-exception_messages RuboCop plugin to enforce casing and punctuation, with additional checks for redundant class names and interpolation markers. ### Source excerpt While reviewing dozens of PRs from ericproulx optimizing Grape's internals recently, I noticed that the bare raise ArgumentError, "..." calls scattered across the codebase were inconsistent: some messages were capitalized, some ended in a period, most were not. Longtime readers know where this is going. Ruby's own core and standard library exceptions don't do this - TypeError: no implicit conversion from nil to integer, ArgumentError: wrong number of arguments, and so on all read lowercase and unpunctuated, because the message is meant to be read after the exception class name and a colon, not as a standalone sentence. Grape's own Grape::Exceptions::* classes already follow this convention. The bare raise ArgumentError, "..." calls in dsl/entity.rb, dsl/inside_route.rb, dsl/validations.rb, and validations/types/dry_type_coercer.rb didn't, so I fixed those seven sites and documented the convention in CONTRIBUTING.md, in #2909. To avoid regressions, I wrote rubocop-exception_messages, a RuboCop plugin gem with two cops: ExceptionMessages/Casing flags (and autocorrects) messages that don't start with a lowercase letter. ExceptionMessages/Punctuation flags (and autocorrects) messages with a trailing period, with an exception for a literal ellipsis ("still processing.."), which is stylistic rather than a sentence ending. Both cops recognize raise Class, "message" and raise Class.new("message") forms, and handle interpolated (dstr) messages by only checking the literal string segments (the first segment for casing, the last for punctuation), since interpolated values in the middle are out of the cop's control. # bad raise ArgumentError, 'Missing required option.' # good raise ArgumentError, 'missing required option' The gem ships as a modern RuboCop plugin (via lint_roller), so it's a one-line addition to a consuming project's .rubocop.yml: plugins: - rubocop-exception_messages rubocop-exception_messages 0.2.0 is out now, and I've added it back to Grape's own Gemfile and ## Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java DevFeed: [Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java]() Original publisher: [Read original article]() Author: Poonam Parhar Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [Inside Java]() Topics: [Cryptography](), [fips 140-3](), [openssl](), [Java](), [Encryption](), [Security, Privacy and Abuse Prevention]() Tags: [cryptographic](), [cryptography](), [fips](), [fips-140-3](), [java](), [openssl](), [oracle](), [security](), [standard]() ### AI overview Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module and exposes cryptographic services through Java Cryptography Architecture (JCA). ### Source excerpt Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module, making cryptographic services available through the standard Java Cryptography Architecture (JCA) framework. ## C++29 -- начало. Встреча ISO C++ в Брно DevFeed: [C++29 -- начало. Встреча ISO C++ в Брно]() Original publisher: [Read original article]() Author: antoshkka (Яндекс) Published: 2026-08-17T07:01:31Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [C++](), [floating-point](), [implementation]() Tags: [c-plus-plus](), [c-plus-plus-29](), [floating-point](), [fmt](), [format](), [implementation](), [iso](), [standard](), [standard-library](), [tagged-pointers](), [thread](), [threads](), [undefined-behavior](), [undefined-behaviour]() ### AI overview A report on the ISO C++ committee meeting in Brno, where work on C++29 began. It describes plans to organize and clarify documented undefined behavior and ill-formed-no-diagnostic-required cases, along with changes involving constexpr floating-point evaluation and other language rules. ### Source excerpt Привет! На связи Антон Полухин из Техплатформы Городских сервисов Яндекса. Недавно в Брно состоялась встреча международного комитета по стандартизации языка программирования C++, в которой я принимал активное участие. В этот раз началась работа над C++29 и как раз о новинках и хочется рассказать. Читать далее ## The New Default Nix Flake Template Explained DevFeed: [The New Default Nix Flake Template Explained]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2026-08-17T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Template](), [Development](), [Tooling]() Tags: [architecture](), [how-to](), [learn](), [packages](), [patterns](), [shell](), [standard](), [template]() ### AI overview An explanation of the new default Nix flake template, which supports multiple platforms without flake-utils. The article describes the underlying pattern, how to extend it for real projects, and its limitations and advanced cases. ### Source excerpt The default Nix flake template is now multi-platform without flake-utils. Learn how the new pattern works and how to extend it for real projects. ## Using ArgoCD to Manage AI Model Deployments with GitOps DevFeed: [Using ArgoCD to Manage AI Model Deployments with GitOps]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-07-28T18:24:57Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [GitOps](), [argocd](), [model-deployment](), [Artificial Intelligence](), [model-serving](), [Architecture & Design]() Tags: [ai](), [ai-models](), [argo-rollouts-model-promotion](), [argocd](), [argocd-ai-model-deployment](), [argocd-applicationset](), [argocd-sync-waves](), [automation](), [ci-cd](), [declarative-model-serving](), [deployment](), [devops](), [gitops](), [gitops-for-ai-model-deployments](), [gitops-mlops](), [kserve](), [kserve-canary-deployment](), [kubernetes](), [kubernetes-model-deployment-rollback](), [ml-model-deployment](), [ml-model-versioning](), [mlops](), [model-deployment](), [model-registry-to-git-automation](), [model-serving](), [pull-requests](), [standard](), [tutorial]() ### AI overview This tutorial explains how to use ArgoCD and GitOps to deploy AI models while accounting for model weights stored outside container images. It covers pinned model references, rollback and recovery, synchronization ordering, readiness probes, evaluation-based promotion gates, and KServe status handling. ### Source excerpt Your microservices deploy through pull requests with full audit trails. Your models deploy because someone ran a script. Here is how to close that gap with ArgoCD, and what changes when the artifact weighs four gigabytes. ## Your Codename One App Can Be an MCP Server DevFeed: [Your Codename One App Can Be an MCP Server]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-21T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [MCP Server](), [Model Context Protocol (MCP)](), [ui](), [Accessibility](), [App]() Tags: [accessibility](), [agents](), [coding-agents](), [json](), [mcp](), [mcp-server](), [process](), [rpc](), [standard](), [ui]() ### AI overview The article explains how a running Codename One simulator or JavaSE desktop tool can expose its semantic UI and application tools through a local Model Context Protocol server. MCP hosts can inspect forms, interact with labeled fields and buttons, and invoke domain tools while actions run on the event dispatch thread and return fresh state snapshots. ### Source excerpt A running Codename One simulator or JavaSE tool can expose its semantic UI and application tools to coding agents over MCP. ## Announcing the CIS Benchmark for CockroachDB v25.x DevFeed: [Announcing the CIS Benchmark for CockroachDB v25.x]() Original publisher: [Read original article]() Author: Adam Brennick,Ayog Mohanty Published: 2026-07-14T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [Benchmark](), [CockroachDB](), [Security](), [Cockroach Labs](), [configuration](), [Cybersecurity](), [Database](), [Self-hosted]() Tags: [announce](), [benchmark](), [cockroach-labs](), [cockroachdb](), [compliance](), [configuration](), [fedramp](), [government](), [hipaa](), [pci-dss](), [published](), [security](), [security-best-practices](), [security-research](), [self-hosted](), [standard]() ### AI overview The Center for Internet Security has published the CIS CockroachDB v25.x Benchmark, providing a consensus-driven security configuration guide for self-hosted CockroachDB deployments. The article explains how the benchmark can support standardized security practices, audits, compliance reviews, and production configuration validation. ### Source excerpt We're proud to announce that the Center for Internet Security (CIS) has published the CIS CockroachDB v25.x Benchmark. ## RFC 10005: BGP Community for link capacity DevFeed: [RFC 10005: BGP Community for link capacity]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T13:31:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [standard](), [Load Balancing](), [Network]() Tags: [bgp](), [capacity](), [internet](), [load-balancing](), [network](), [network-operations](), [rfc](), [rfc-10005](), [route](), [routers](), [routing](), [standard](), [traffic]() ### AI overview RFC 10005 defines a BGP extended community for carrying link bandwidth information in routes. When multiple BGP paths are eligible, routers can use the value to weight traffic according to link capacity, while normal best-path policy still determines route eligibility. The RFC is currently a draft. ### Source excerpt RFC 10005 defines a BGP extended community that lets a router attach link bandwidth information to a route. Another router can use that value when it spreads traffic across multiple BGP paths. RFC 10005 matters because links are not always of the same capacity. This RFC provides routers with a standard way to carry bandwidth ... Read more The post RFC 10005: BGP Community for link capacity appeared first on Justin Wilson (j2sw). ## Pulumi ships a 238-policy ISO/IEC 27001:2022 pack for AWS DevFeed: [Pulumi ships a 238-policy ISO/IEC 27001:2022 pack for AWS]() Original publisher: [Read original article]() Author: Dan Biwer Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Amazon Web Services](), [Security](), [Cloud](), [configuration]() Tags: [audit](), [aws](), [compliance](), [crossguard](), [features](), [governance](), [infrastructure](), [iso](), [iso-27001](), [policy](), [policy-as-code](), [product](), [pulumi](), [pulumi-cloud](), [security](), [standard]() ### AI overview Pulumi announces a pre-built ISO/IEC 27001:2022 policy pack for AWS, available in Pulumi Cloud as iso-27001-aws. The pack contains 238 policies mapped to relevant ISO 27001 controls and supports auditing existing AWS resources and preventing non-compliant resources during pulumi up. ### Source excerpt ISO/IEC 27001 is the international standard for information security management. Proving you meet it usually means months of mapping abstract security controls to concrete cloud configuration, then authoring custom checks one resource at a time. We're changing that. Today we're shipping a pre-built ISO/IEC 27001:2022 policy pack for AWS, live now in Pulumi Cloud as iso-27001-aws. It encodes the standard's security expectations as 238 ready-to-run policies, so you can align your AWS estate to ISO 27001 in minutes, not months. Why ISO 27001 matters For many companies, ISO 27001 is what stands between them and a customer or a market. The sooner you can reach a certifiable state and prove you stay there, the less compliance slows the business down. The pack collapses months of policy work into something you run continuously, so security keeps pace with growth instead of blocking it. How the pack maps to ISO 27001 The hard part of ISO 27001 has always been translation: its controls are written in the language of governance and risk management, not in the language of AWS resources. Every team has had to interpret each control and decide what it means for an S3 bucket or an RDS instance. The pack does that interpretation for you. Its 238 policies are aligned to the relevant ISO 27001 controls, so each result connects back to the standard instead of leaving you to map it yourself. You can browse the full pack in the pack reference. Audit and prevent The same pack works two ways, so you can both reach compliance and stay there: Audit. Scan your existing AWS estate against the pack, including resources that Pulumi doesn't manage. You get an honest baseline of where you stand against ISO 27001 today, with every finding tied back to the control it affects. Prevent. Run the same pack as a preventative policy during pulumi up to block non-compliant resources before they're ever created. New infrastructure is born aligned to the standard. Audit gets you clean. Preventative policie ## Obfuscated Rhythm Games DevFeed: [Obfuscated Rhythm Games]() Original publisher: [Read original article]() Author: Dan Lew Published: 2026-06-23T14:17:46Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [obfuscation](), [standard]() Tags: [game](), [games](), [music](), [obfuscation](), [standard]() ### AI overview The article examines three rhythm games released in 2025 that intentionally obscure which buttons players should press and when. It discusses how Rift of the Necrodancer, Rhythm Doctor, and Unbeatable derive much of their challenge from less legible note charts and altered visual or auditory cues. ### Source excerpt I've been a rhythm game fiend since my introduction to Dance Dance Revolution in the early 2000s. I spent years obsessed with DDR, took a detour into Beatmania, then played Guitar Hero / Rock Band nonstop for years. I haven't gone deep on any rhythm games recently, ## Open rails for agentic commerce at Open Source Summit North America 2026 DevFeed: [Open rails for agentic commerce at Open Source Summit North America 2026]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-16T23:16:03Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [Artificial Intelligence](), [Open Source](), [systems](), [Protocol (disambiguation)]() Tags: [2026](), [agentic](), [agentic-commerce](), [ai](), [ai-agents](), [business](), [capabilities](), [checkout](), [consumer](), [e-commerce](), [features](), [fragmentation](), [integration](), [interoperability](), [open-source](), [open-standards](), [payment](), [platforms](), [shopping](), [standard](), [ucp](), [universal-commerce-protocol](), [workflows]() ### AI overview An article from Open Source Summit North America 2026 explains why agentic commerce may require shared, open rules and integrations. It presents Universal Commerce Protocol (UCP) as an open standard intended to let agents, businesses, consumer surfaces, and payment providers work together across shopping, checkout, fulfillment, and post-purchase flows. ### Source excerpt by Anurag Sinha, Universal Commerce Protocol (UCP) At Open Source Summit North America 2026, I shared why agentic commerce needs open rails. As AI agents become more capable, the shopping journey is shifting from "show me" to "help me." Instead of browsing, comparing, clicking, and checking out step by step, people can increasingly ask an agent to help them decide what to buy and, in some cases, complete the purchase. Industry forecasts suggest agentic shopping could account for roughly 10% to 25% of U.S. e-commerce by 2030 (Bain), which points to a meaningful shift in how digital commerce will work. Watch the full keynote here. Why shared rules matter That shift also exposes a challenge. Commerce is still highly fragmented. Different businesses, payment providers, and platforms operate with their own rules, workflows, and business logic. Every new surface adds more integration work. Every bespoke connection creates more complexity. And that fragmentation makes it harder for AI systems to understand and perform commerce actions consistently across businesses. A shared language lowers that barrier for everyone. A common language for agentic commerce That is the problem Universal Commerce Protocol (UCP) is designed to solve. We launched the Universal Commerce Protocol, or UCP, with industry leaders to establish an open standard for agentic commerce, built to work across the shopping journey. UCP creates a common language for agents and systems to operate together across consumer surfaces, businesses, and payment providers, so the ecosystem does not need a different bespoke integration for every new agent or platform. Just as importantly, UCP is designed for the real world. Every business has its own way of selling. Checkout, fulfillment, loyalty, policy logic, shipping, and post-purchase flows can vary widely between a local shop, a marketplace, and a large retailer. UCP is built to support that reality. A layered architecture for a shared commerce language UCP uses a ## Khronos Launches Initiative to Extend glTF for Volumetric Media DevFeed: [Khronos Launches Initiative to Extend glTF for Volumetric Media]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-06-15T13:00:00Z Content type: news Language: en Sources: [Blogs Khronos Blog]() Topics: [3D](), [interoperability]() Tags: [3d](), [api](), [blog-gltf-volumetri](), [capture](), [extend](), [gltf](), [media](), [playback](), [standard](), [standards](), [streaming]() ### AI overview Khronos has established a Volumetric Media Subgroup within its 3D Formats working group to extend glTF for interoperability across volumetric capture, data formats, and content playback. The initiative invites organizations to help define the new capabilities. ### Source excerpt Any interested organizations are invited to join Khronos to help define new glTF capabilities to enable interoperable volumetric capture, streaming and playback ## Why JSON and other languages should allow more flexible separators DevFeed: [Why JSON and other languages should allow more flexible separators]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-06-10T12:22:04Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [JSON](), [Haskell](), [Parsing]() Tags: [json](), [language](), [standard](), [transformation]() ### AI overview The article argues that requiring separators in particular positions makes common code transformations harder. Using JSON as the main example, it compares trailing, leading, and both-sided separator styles across languages including Haskell, TLA+, Prolog, Python, Go, and Alloy. ### Source excerpt This is valid JSON: { "a": 1, "b": 2, "c": 3 } This is invalid JSON: { "a": 1, "b": 2, "c": 3, } The difference is the last comma. The JSON grammar specifies that a comma can separate two members of an object but not postcede ("trail") a member. I think this was a design mistake. Say we want to add two new keys to the struct, one before the "a" member and one after the "c" member. Here's what it would look like if trailing commas were permitted: { + "x": 0, "a": 1, "b": 2, "c": 3, + "y": 4, } It's the exact same text transformation regardless of where we add the key. In the current model, we instead have this: { + "x": 0, "a": 1, "b": 2, - "c": 3 + "c": 3, + "y": 4 } Those are different transformations! Similarly if you want to remove an element, you can't just delete the corresponding line1, you have to delete the line and then check that the last line doesn't have a trailing comma. Don't even get me started on all the special cases involved in swapping two lines. JSON isn't the only language with this problem. Haskell writes record types like this: -- from https://play.haskell.org/ data Drone = Drone { xPos :: Int , yPos :: Int , zPos :: Int } This "partial bullet point" style of putting separators at the beginning of rows makes it easier to change the last row but harder to change the first one. TLA+ has this problem too: \* both valid VARIABLES a, b, c vars == <> \* both invalid VARIABLES a, b, c, vars == <> This one's annoying because 1) you're constantly adding new top-level variables while working on a spec and 2) the PlusCal DSL does not have this problem: \* Totally fine! (*--algorithm foo { variables a; b; c; The worst offenders, IMO, are logic languages like Prolog. Not only don't you have trailing separators, you have a special terminating symbol: foo(A, B, C) :- A = 1, % comma B = 2, % comma C = 3. % period! I guess you can sort of think of it as funny-lookin' braces: foo(A, B, C) :- A = 1, B = 2, C = 3 . But this is not standard synt ## What Is ACH Payment? A Complete Guide for SaaS Founders DevFeed: [What Is ACH Payment? A Complete Guide for SaaS Founders]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Transactions]() Tags: [ach](), [bank](), [batch](), [business](), [compliance](), [cost](), [guide](), [payment](), [payments](), [saas](), [scheduled](), [standard](), [us]() ### AI overview This guide explains ACH payments for SaaS companies, including how the US bank-transfer network works, why ACH fees can be lower than card fees, settlement timelines, and options for accepting ACH without operating a merchant account. ### Source excerpt ACH payments explained for SaaS - how they work, why they cost 10x less than cards, settlement timelines, and how to accept them without your own merchant account. ## Clear Signing: Making Transaction Approvals Safer on Ethereum DevFeed: [Clear Signing: Making Transaction Approvals Safer on Ethereum]() Original publisher: [Read original article]() Author: Hester Bruikman Published: 2026-05-12T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Security](), [Blockchain](), [App]() Tags: [blockchain](), [developers](), [ethereum](), [format](), [security](), [signing](), [standard]() ### AI overview An Ethereum Working Group has launched Clear Signing, an open standard intended to help wallets present human-readable, structured descriptions of transaction effects. The approach includes ERC-7730, a descriptor registry, verification through independent reviews and attestations, and tools for wallet and developer adoption. ### Source excerpt An Ethereum Working Group consisting of wallet developers, security firms and the Ethereum Foundation's Trillion Dollar Security Initiative today launched an open standard designed to end blind signing -- a structural flaw that has contributed to billions in user losses, including the Bybit hack. Ethereum Foundation's Trillion Dollar Security Initiative... ## QCOW2 is now GA in XCP-ng DevFeed: [QCOW2 is now GA in XCP-ng]() Original publisher: [Read original article]() Author: Damien Thenot Published: 2026-05-05T17:29:49Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [Disk image](), [cloud-infrastructure]() Tags: [new-feature](), [news](), [production](), [qemu](), [release](), [standard](), [storage](), [test](), [update]() ### AI overview XCP-ng 8.3 makes QCOW2 production-ready for virtual disks up to 16 TiB, addressing the 2 TiB limit of VHD. VHD remains the default for smaller disks, while Xen Orchestra automatically selects QCOW2 for new disks larger than 2040 GiB. The release emphasizes stability, testing, and compatibility with existing storage repositories. ### Source excerpt QCOW2 is now GA in XCP-ng 8.3, supporting VM disks up to 16 TiB and replacing the 2 TiB VHD limit. Production-ready, stability-focused, with performance optimizations coming soon. ## A year of open collaboration: Celebrating the anniversary of A2A DevFeed: [A year of open collaboration: Celebrating the anniversary of A2A]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-04-16T20:55:00Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [A2A protocol](), [Artificial Intelligence](), [Google](), [interoperability](), [Open Source](), [linux foundation](), [Security](), [Load Balancing]() Tags: [a2a](), [a2a-protocol](), [a2april](), [agent2agent](), [agents](), [ai](), [ai-agents](), [amazon](), [amazon-web-services](), [cisco](), [cryptographic](), [interoperability](), [linux-foundation](), [load-balancing](), [microsoft](), [open-source](), [sap](), [security](), [specifications](), [standard]() ### AI overview Google reflects on the first year of the Agent2Agent (A2A) protocol, including its donation to the Linux Foundation, the growth of its supporting ecosystem, and the release of A2A Protocol v1.0. The article highlights security, enterprise architecture, and interoperability improvements for multi-agent workflows. ### Source excerpt by Patricia Cruz, Google Open Source One year ago, on April 9th, 2025 Google announced the Agent2Agent(A2A) protocol. We saw the need for a "common language" that allows AI agents built on different frameworks to collaborate well across diverse systems. Then, on June 23, 2025 at the Open Source Summit North America in Denver, Mike Smith stood on stage to share a pivotal moment for the future of AI interoperability when Google officially donated the A2A protocol to the Linux Foundation, establishing it as a vendor-neutral, community-governed standard. This move was driven by a core belief: for AI agents to truly transform how we work and live, they must be able to communicate across framework boundaries and organizational silos without being locked into a single provider's ecosystem. By placing A2A under the neutral stewardship of the Linux Foundation, we opened the doors for the entire industry to build, contribute, and innovate together. A Foundation of Partners The formation of the A2A Project was made possible through the support of our founding members, including Amazon Web Services, Cisco, Microsoft, Salesforce, SAP, and ServiceNow. Over the past twelve months, this coalition has grown, with over 100 technology companies now supporting the project. From Prototype to Production The momentum since the donation has been remarkable. What began as a Google-led initiative has evolved into critical infrastructure for horizontal, peer-to-peer collaboration. Just one month ago, in March, the project reached a major milestone with the release of A2A Protocol v1.0, the first stable, fully production-ready version of the standard. Key achievements from the community this year include: Enhanced Security: The implementation of Signed Agent Cards for cryptographic identity verification, ensuring trust in multi-agent workflows. Web-Aligned Architecture: Refined specifications that support familiar load-balancing and security patterns for enterprise-scale deployments. Ecosystem ## Wastrel Compiles Hoot Scheme-to-WebAssembly Output DevFeed: [Wastrel Compiles Hoot Scheme-to-WebAssembly Output]() Original publisher: [Read original article]() Author: Andy Wingo Published: 2026-03-31T20:34:23Z Content type: article Language: en Sources: [wingolog]() Topics: [WebAssembly](), [Compiler](), [scheme]() Tags: [accidentally-quadratic](), [aot](), [bigint](), [bignums](), [compiler](), [compilers](), [exception-handling](), [exceptions](), [gc](), [gcc](), [gmp](), [hoot](), [igalia](), [library](), [maps](), [precision](), [scheme](), [standard](), [tail-calls](), [wasm](), [wastrel](), [webassembly](), [whippet]() ### AI overview The article describes recent work on Wastrel, an ahead-of-time WebAssembly compiler, including compiling output from the Hoot Scheme-to-Wasm compiler. It covers implementing bignum operations with mini-gmp and updating Hoot to use standardized WebAssembly exception handling. ### Source excerpt Good day! Today (tonight), some notes on the last couple months of Wastrel, my ahead-of-time WebAssembly compiler. Back in the beginning of February, I showed Wastrel running programs that use garbage collection, using an embedded copy of the Whippet collector, specialized to the types present in the Wasm program. But, the two synthetic GC-using programs I tested on were just ported microbenchmarks, and didn't reflect the output of any real toolchain. In this cycle I worked on compiling the output from the Hoot Scheme-to-Wasm compiler. There were some interesting challenges! bignums When I originally wrote the Hoot compiler, it targetted the browser, which already has a bignum implementation in the form of BigInt, which I worked on back in the day. Hoot-generated Wasm files use host bigints via externref (though wrapped in structs to allow for hashing and identity). In Wastrel, then, I implemented the imports that implement bignum operations: addition, multiplication, and so on. I did so using mini-gmp, a stripped-down implementation of the workhorse GNU multi-precision library. At some point if bignums become important, this gives me the option to link to the full GMP instead. Bignums were the first managed data type in Wastrel that wasn't defined as part of the Wasm module itself, instead hiding behind externref, so I had to add a facility to allocate type codes to these "host" data types. More types will come in time: weak maps, ephemerons, and so on. I think bignums would be a great proposal for the Wasm standard, similar to stringref ideally (sniff!), possibly in an attenuated form. exception handling Hoot used to emit a pre-standardization form of exception handling, and hadn't gotten around to updating to the newer version that was standardized last July. I updated Hoot to emit the newer kind of exceptions, as it was easier to implement them in Wastrel that way. Some of the problems Chris Fallin contended with in Wasmtime don't apply in the Wastrel case: sinc ## JSON and C++26 compile-time reflection: a talk DevFeed: [JSON and C++26 compile-time reflection: a talk]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-03-26T00:29:38Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [C++](), [JSON](), [Library]() Tags: [2025](), [c-plus-plus](), [cppcon](), [json](), [speed](), [standard](), [talk](), [video](), [youtube]() ### AI overview The article announces a CppCon 2025 talk about using C++26 compile-time reflection for high-speed JSON serialization and deserialization. It says the authors extended the simdjson library to test the approach and that the talk video is available on YouTube. ### Source excerpt The next C++ standard (C++26) is getting exciting new features. One of these features is compile-time reflection. It is ideally suited to serialize and deserialize data at high speed. To test it out, we extended our fast JSON library (simdjson) and we gave a talk at CppCon 2025. The video is out on YouTube. Our ... Continue reading JSON and C++26 compile-time reflection: a talk ## The 3 curves that make a scalable business DevFeed: [The 3 curves that make a scalable business]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-02-10T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Software](), [Code quality](), [Processes](), [Users]() Tags: [automate](), [bugs](), [code-quality](), [documentation](), [engineering](), [revenue](), [scale](), [software](), [standard](), [support](), [test](), [users]() ### AI overview An opinion article explains three growth curves behind a scalable business: users and revenue should grow exponentially, bugs linearly, and support work logarithmically. It argues that retention, automation, code quality, testing, documentation, and streamlined processes help engineering organizations scale. ### Source excerpt You want users and revenue to grow exponentially. Bugs per day to grow linearly. Support work to grow logarithmically. Your goal is to make this happen. ## JWT Authorization Grant and Identity Chaining in Keycloak 26.5 DevFeed: [JWT Authorization Grant and Identity Chaining in Keycloak 26.5]() Original publisher: [Read original article]() Author: Giuseppe Graziano Published: 2026-01-23T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [JSON Web Tokens](), [Keycloak](), [OAuth 2.0](), [OAuth](), [Authorization](), [Internet Engineering Task Force (IETF)]() Tags: [authorization](), [deprecated](), [external](), [identity](), [idm](), [jwt](), [kerberos](), [keycloak](), [ldap](), [oauth](), [oauth-2-0](), [openid-connect](), [preview](), [saml](), [sso](), [standard](), [trust]() ### AI overview Keycloak 26.5 introduces preview support for JWT Authorization Grant under RFC 7523. The feature lets clients exchange a signed JWT from an external issuer for a Keycloak access token. The article also explains how combining this grant with OAuth 2.0 Token Exchange can preserve identity and authorization context across multiple trust domains. ### Source excerpt Modern applications and AI agents increasingly operate across distributed trust domains, where each domain is protected by its own OAuth 2.0 Authorization Server. A single request may also traverse multiple resource servers to complete a task. This raises an important challenge: every protected resource must understand who initiated the request, which authorization was granted, and optionally which other resources were accessed before making an authorization decision. Preserving this information across domains is critical. Keycloak 26.5 introduces preview support for the new feature JWT Authorization Grant, implementing RFC 7523. This feature allows a client to present a signed JWT from an external issuer and obtain a Keycloak access token, providing a standard and secure way to authorize requests based on external assertions. However, exchanging a token alone does not fully solve the problem of propagating identity and authorization context across multiple trust domains. The IETF draft OAuth Identity and Authorization Chaining Across Domains defines a standardized flow that combines JWT Authorization Grant (RFC 7523) with OAuth 2.0 Token Exchange (RFC 8693), which Keycloak already supports, to preserve the original user's identity, claims, and authorization throughout the chain. JWT Authorization Grant The JWT Authorization Grant feature allows a client to present a signed JWT assertion to the token endpoint and obtain an access token without an interactive authorization step. To initiate this flow, the client sends a request to the token endpoint with the grant_type set to urn:ietf:params:oauth:grant-type:jwt-bearer and the external token passed in the assertion parameter. It provides a standard and secure alternative to the preview feature External-to-Internal Token Exchange V1 which will be deprecated. Trust relationships in Keycloak are defined through Identity Providers. The JWT Authorization Grant can be enabled and configured in a dedicated section of the ex ## Unsigned char std::basic\_string\<\> in C++ DevFeed: [Unsigned char std::basic\_string\<\> in C++]() Original publisher: [Read original article]() Published: 2026-01-03T22:00:02Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [C++](), [standard](), [LLVM](), [clang](), [gcc]() Tags: [bits](), [c-plus-plus](), [clang](), [concatenation](), [cryptographic](), [freebsd](), [gcc](), [llvm](), [openbsd](), [standard](), [string]() ### AI overview A C++ post explains why code using std::basic_string can fail on FreeBSD and OpenBSD. The issue involves std::char_traits: LLVM 19 removed its unconstrained base template because the C++ Standard does not require it for unsigned-character types. Code may need string concatenation and related operations replaced or a correct custom specialization provided. ### Source excerpt Brief post on a somewhat vexing and irritating C++ problem I ran into some time ago. I hope that this page will help other people deal with this problem more quickly than I did. I've long used std::basic_string, an unsigned char string, for fiddling with bits. You could use a regular char string, but especially when doing cryptographic or sub-byte operations, it is more convenient to not have to deal with sign bits. [Next page]()