Cascadity Audio
← All streams

#open-source

Everything tagged open-source, across every stream.

0

IEEE Spectrum: the PHP2Shell flaw shows AI is exposing decades of old bugs faster than volunteers can fix them

A clear explainer of how a years-old crash bug became a critical exploit with AI help, and why defenders worry about the gap between finding and fixing.

IEEE Spectrum's Dina Genkina looks at PHP2Shell, the PHP flaw disclosed in late October that put sites running WordPress, Drupal and other PHP software at risk of data theft and remote code execution. The underlying memory bug had been reported to the PHP Foundation in 2024 but was treated as a mere crash. A researcher at the security firm Calif, auditing PHP with AI tools under OpenAI sponsorship, turned it into a working code-execution exploit within two weeks; Wiz confirmed and expanded the findings, and four PHP engineers spent two months on a patch. As far as anyone knows, it was fixed before attackers had the exploit.

"Now it is time for the technical debt to be paid off," says Matt Suiche of Tolmo. Columbia's Suman Jana describes an asymmetry: AI makes finding bugs easier, but fixes must close every path without breaking anything, which strains unfunded open-source maintainers. Johns Hopkins' Matthew Green expects little to change until something worse happens; meanwhile, he says, install updates promptly.

Cascadic Analysis 2
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

The bug was reported in 2024 and filed as a crash; a researcher auditing PHP with AI tools turned it into a working code-execution exploit within two weeks. Fixing it took four PHP engineers two months. Columbia's Suman Jana names the asymmetry: AI makes finding bugs easier, while fixes must close every path without breaking anything, and much of that work falls on unfunded maintainers.

0
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

This one went well: as far as anyone knows, PHP2Shell was patched before attackers had an exploit. A good outcome can be read as proof that the current setup works, and Johns Hopkins' Matthew Green expects little to change until something worse happens. Each near miss that ends well makes the next one easier to underfund, even as AI tools surface more old bugs at once.

0
Rabbit Holes 1
0

r/homeassistant: a huge upcoming release raises AI worries, and a core developer explains how they review code

A maintainer's candid account of how a big open-source project handles a flood of AI-assisted contributions.

The post is an image, titled "Who's excited?", about the size of the upcoming Home Assistant 2026.11 release. German Home Assistant blog simon42 reports the 2026.11 beta is out with the final release planned for November 4, and that it reads like three releases at once, with HACS (the community add-on store) becoming a built-in marketplace and support for Matter cameras.

The top reply, from user frenck_nl, who says the screenshotted post is his, explains that the release is big because of a large number of contributions, that bringing HACS in was only a few pull requests, and that AI shows up in many submissions. He writes that the team has added static checks and tuned automated Copilot reviews, that his analysis of 10,000 reviews found about 40% of review comments were repeats worth automating, and that human judgment still decides. Other commenters say they'll wait for a later point release, or doubt that a large count of merged changes is good news in the AI era. About 2,600 upvotes in a 386,000-member community.

Cascadic Analysis 2
UndertowRole underspecification / the Doorman Problem

What hidden risk could pull against this, even if the news is good?

frenck_nl's numbers draw the line well: about 40% of review comments were repeats worth automating with static checks and tuned Copilot reviews. The other 60% is the part of a reviewer's role that isn't written down, judging whether a change fits the project and will be maintainable, and he says human judgment still decides. The risk in a release this large is volume quietly shifting more of that judgment to the automated layer.

0
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

A change that passes static checks and an automated review can still fail in someone's home months later, on a device combination nobody tested. Commenters planning to wait for a later point release are guarding against exactly that. A large count of merged changes measures throughput at merge time, not how the code behaves once it is running.

0
Rabbit Holes 1
  • Home Assistant

    After exploring Who’s excited?, the project itself is introduced in Home Assistant.

    Wikipedia describes Home Assistant as free, open-source software for centralized home automation that works across device brands and runs with local control.

    Wikipedia · Wade · 5 min

    0
0

Ghostty 1.4 terminal ships compressed scrollback, full Kitty graphics support and 10 security fixes

Hand-written release notes that explain the engineering, including a surprising macOS kernel limit on terminal reads.

Ghostty, the free, non-profit terminal emulator, released version 1.4.0 on October 27 after seven months of work: 2,889 commits from 172 contributors. Highlights from the release notes:

  • Memory: scrollback that isn't on screen is now compressed while the terminal is idle, cutting its physical memory use by 70-90% for typical text, so the default scrollback limit rose from 10 MB to 50 MB. Hidden tabs release GPU memory (about 385 MiB down to 18 MiB in one macOS test).
  • Graphics: Ghostty now implements 100% of the Kitty graphics protocol, including animation, which the maintainers say makes it the first terminal other than Kitty to do so.
  • Speed: the team found macOS caps each read from a pseudo-terminal at about 1 KiB and reworked how output is drained and parsed.
  • Security: ten advisories are fixed, including paste protection that missed carriage returns and crafted Kitty graphics or hyperlinks that could, in some cases, read files or run commands. It also supports macOS 27.

On Hacker News, users compared it with Konsole, WezTerm and iTerm2, and a commenter from the project pointed to libghostty, the embeddable terminal core.

Rabbit Holes 1
  • Terminal emulator

    After exploring 1.4.0 - Release Notes, for the basics of what Ghostty is, start with Terminal emulator.

    Explains what a terminal emulator is: a program that imitates a video terminal inside a graphical desktop, often called a terminal window.

    Wikipedia · Wade · 5 min

    0
0

r/LocalLLaMA weighs Google Research's open-source Harness2, which lets AI agents rework their own setup

A plain explanation of what an agent 'harness' is, and hands-on skeptics asking whether self-tuning helps local models.

The post shares Harness2 (styled Harness²), released on GitHub by Google Research under the Apache 2.0 license. Its README describes a framework that keeps a model's weights fixed but lets the agent propose and test edits to everything around it (system prompt, guardrails, memory, tools, subagents, skills), then keep the better version and carry lessons to later tasks, without ground-truth answers. The authors report gains of up to 11.5 points on WorkBuddy-Bench, 4.5 on JobBench and 11.8 percentage points on the LAB legal benchmark with GLM-5 and Gemini 3.5 Flash. The README also says it is "not an officially supported Google product."

Top replies worry that all the self-refinement will eat context, a bigger problem for people running models locally, and that a harness tuned to a task can overfit benchmarks. Others answer that it changes context rather than growing it, and ask experts whether it is significant. About 1,600 upvotes in a 329,000-member community.

Cascadic Analysis 3
UndertowLoss of meaningful human control as capability and autonomy increase

What hidden risk could pull against this, even if the news is good?

Guardrails are one of the components Harness² lets the agent propose edits to, along with its system prompt, memory, tools and subagents. A system that can adjust its own rules and keeps the version that scores better needs a fixed line somewhere that it isn't allowed to rewrite, or the person running it is supervising a moving target.

0
UndertowPersistent memory creates a new poisoning surface

What hidden risk could pull against this, even if the news is good?

The "harnessing-level" loop keeps adopted harnesses and lessons from each task in a persistent improvement harness that guides later tasks. A wrong lesson, or one learned from a task containing planted instructions, would carry forward into tasks that have nothing to do with where it came from.

0
UndertowSpecification gaming / goal misgeneralization

What hidden risk could pull against this, even if the news is good?

The README says refinement happens without ground-truth feedback: the agent compares its own runs and keeps the edits that look better. Reddit commenters worried that a harness tuned to a task can overfit benchmarks, and the reported gains (up to 11.5 points on WorkBuddy-Bench) are measured on the same kinds of benchmarks the method is tuned on.

0
Rabbit Holes 1
0

r/LocalLLaMA cheers Linus Torvalds' reply rejecting 'don't use AI' rules for Linux kernel work

Torvalds' mailing-list reply in full, and a useful debate on where AI help ends and low-effort patches begin.

The post is a screenshot of a Linux kernel mailing-list reply in which Linus Torvalds calls the idea of "don't use AI for X" rules "idiotic" and, mockingly, proposes banning compilers and text editors for kernel submissions. He writes that he expects people "to understand what they are doing," and that this has "very little to do with what tools they use." The Next Web reports the reply came on October 13 after kernel maintainers moved to drop the "Assisted-by" tag that had asked contributors to disclose AI coding tools.

The top replies agree that quality work should be accepted regardless of where it came from, while others stress the other half of his message: contributors must understand their code. Several worry that AI makes it easy to flood open-source projects with low-quality pull requests that take maintainers time to sift. About 3,100 upvotes in a 329,000-member community.

Cascadic Analysis 1
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

Torvalds' standard is that contributors must understand their code, whatever the tool. Dropping the "Assisted-by" tag also drops the record of which patches came from AI tools. If a kind of mistake those tools tend to make shows up years later in code that passed review, maintainers won't have an easy way to find the other patches that might share it.

0
Rabbit Holes 1
0

DeepSeek open-sources DeepInfer, the inference engine behind its own production service

A rare look at how a frontier lab actually serves its model at scale, released under Apache-2.0.

DeepSeek published DeepInfer on GitHub, describing it as the high-performance inference framework that powers its large-scale production services. This open-source release covers offline inference for DeepSeek-V4.1-Flash on NVIDIA SM100 GPUs and Huawei Ascend 950 NPUs, with optimized kernels (FlashMLA, DeepGEMM, DeepEP and others), expert parallelism, draft-token decoding with confidence-scheduled verification, batch-invariant inference and deterministic sampling. The README says pieces needed for a complete service are not included: a KV cache system, prefill/decode disaggregation and load balancing across replicas. It is licensed Apache-2.0.

It was the most-upvoted story on Hacker News this week. The discussion centered on the economics: a commenter quoted a post on the Chinese site Zhihu claiming strong per-GPU revenue, which set off a debate over whether serving AI models is profitable and what open releases like this mean for the valuations of US frontier labs. Others asked why DeepSeek, and China more broadly, would give this away, with replies arguing it is ordinary open-source strategy rather than state direction.

Cascadic Analysis 1
UndertowWe don't completely understand why frontier models behave as they do

What hidden risk could pull against this, even if the news is good?

DeepInfer advertises batch-invariant inference and deterministic sampling, so the same input gives the same output. That makes a bad answer reproducible, which is a real help to anyone debugging a model, but reproducing a behavior is not the same as explaining it. The README is also clear that this is a partial release: the KV cache system, prefill/decode disaggregation and load balancing needed for a complete service are not included.

0
Rabbit Holes 1
0

PostgreSQL 19 slips to November after AI-assisted code review turns up more defects than developers can fix in time

The Register reports the delay; core developer Peter Eisentraut's blog explains, candidly, how AI review raised the bar on old code.

The PostgreSQL Global Development Group has delayed PostgreSQL 19, once due in late September or early October, to around November 19, and has pulled 8 to 10 significant features back to next year's release, The Register reports. Leading committer Peter Eisentraut wrote that some reverted features had architectural defects too big to fix quickly during beta, but that LLM-assisted code review also surfaced a long tail of small edge-case bugs that in the past might have trickled in over five years. "You're staring at a list of like forty defect reports," he wrote; even three-line fixes carry a fixed overhead each, "and then you run out of time."

Eisentraut says the affected features were written before AI review became this useful, so the effective quality bar rose after they were committed, and he expects the situation to settle in future cycles. He stresses the reverts were not caused by "vibe coding."

Cascadic Analysis 1
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

Eisentraut says AI-assisted review found a long tail of edge-case bugs that once would have trickled in over five years. The same tools can be pointed at PostgreSQL versions already running in production, by anyone; projects whose fixes take longer than the finding will feel that gap first.

0
Rabbit Holes 2
0

OpenCode 2.0 runs as a background service with a rebuilt API

The open-source coding agent explains what it changed after watching millions of daily users.

OpenCode 2.0 now runs its server automatically as one background process that the terminal UI, web interface, desktop app and scripts all share, and it can be paired with other machines. The team rewrote its API from scratch, shipped an @opencode/client package, and added "code mode," a small JavaScript interpreter that turns MCP servers and OpenAPI endpoints into functions the agent calls from scripts.

Cascadic Analysis 2
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

OpenCode 2.0 runs as one background service that every interface and script talks to, and it can be paired with other machines. One long-running process that holds a developer's credentials and can be reached from several places is a valuable target.

0
UndertowPrompt injection may be fundamentally impossible to eliminate

What hidden risk could pull against this, even if the news is good?

Code mode turns MCP servers and OpenAPI endpoints into functions the agent calls from scripts it writes itself. If text the agent reads, from a web page or a repository, can steer what it writes, those scripts can call real APIs on the user's behalf.

0
Rabbit Holes 1
  • Model Context Protocol

    After exploring OpenCode 2.0, the standard its code mode builds on is Model Context Protocol.

    The open standard Anthropic introduced in 2024 for connecting AI systems to outside tools and data, since adopted by OpenAI and Google DeepMind.

    Wikipedia · Wade · 5 min

    0
0

Developer says he built non-autoregressive decision models with RL a year ago

A small open project challenged the idea that fast structured 'System 1' AI models are a new breakthrough—and HN turned it into a debate about invention versus branding.

The author presented Laya, an open system for fast structured decisions that does not generate text token-by-token. The post argued that similar ideas had been built before newer proprietary “System 1” products attracted attention.

Why HN cared

The technical question—how different these systems really are—quickly became a startup question: how much does good branding and distribution matter compared with being first?

Commenters also revisited the idea that many classification, routing and scoring tasks may not need a giant generative model at all.

HN snapshot: roughly 1.3k points and ~300 comments.

Cascadic Analysis 2
UndertowWe don't completely understand why frontier models behave as they do

What hidden risk could pull against this, even if the news is good?

Whether the architecture is genuinely novel matters less to the naysayer than the assurance problem: faster decision models increase the number of decisions we can delegate without making their internal reasoning any easier to audit.

0
UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

A fast 'System 1' model may look excellent on immediate decision benchmarks while its systematic edge cases only emerge after millions of cheap decisions have already been made.

0
Rabbit Holes 2
  • Try Laya in your browser

    After exploring Laya, you can try it yourself: Try Laya in your browser.

    The project's live demo: try the decision engine yourself before weighing in on who invented what.

    Hugging Face Spaces · Wade · 5 min

    0
  • Non-Autoregressive Neural Machine Translation (2017)

    A 2017 paper that generated whole outputs in parallel instead of token by token: useful background on how old the core idea is.

    arXiv · Swim · 30 min

    0
0

Android 17 adds new APIs without releasing them to AOSP

HN saw the change as another sign that Google is tightening control over Android’s supposedly open platform.

GrapheneOS highlighted that Android 17 introduced new public APIs without simultaneously releasing the corresponding platform source to AOSP, an unusual break with Android’s historical model.

Why HN cared

The thread centered on whether Android remains meaningfully open source when Google controls source-release timing, compatibility requirements, attestation and increasingly important proprietary pieces.

Many commenters connected the issue to a broader concern: a project can technically remain open source while one company retains overwhelming practical control.

HN snapshot: about 1.16k points and ~700 comments.