HackerNews Digest

July 04, 2026

Giant trees have no trouble pumping water to top branches: new research

The study, led by researchers from the University of Exeter and Cardiff University and published in *Science*, investigated water transport in tropical Dipterocarp trees ranging from 7 m to 71 m in Malaysian Borneo. Measurements of hydraulic traits along the trunk revealed that taller trees compensate for height by widening basal water‑conducting vessels and by developing leaves with higher wilting thresholds, maintaining liquid water flow despite extreme negative pressures. Growth‑rate data before, during, and after the 2023‑2024 El Niño drought showed no height‑related decline in growth or drought‑induced mortality compared with shorter conspecifics. The findings contradict the prevailing hypothesis that vessel length and gravity limit hydraulic efficiency, photosynthesis, and growth in tall trees. Consequently, models predicting greater drought vulnerability for the tallest 1 % of forest carbon stock may overestimate risk. The research, funded by the Natural Environment Research Council, involved multiple international institutions and highlights the need to reassess hydraulic resilience in other tall tree species.
Read full article →
The comment expresses strong enthusiasm for plant cultivation and experimental techniques, emphasizing plants’ adaptability and the author’s shift from computer science toward botanical science. It highlights interest in defoliation, low‑stress training, and advanced water‑transport concepts such as structured water, while noting both supporting studies and critical reviews of those theories. The author also references giant trees, their water acquisition methods, and questions the potability of tree‑derived water, combining optimism about plant potential with a measured curiosity about contested scientific explanations.
Read all comments →

Leanstral 1.5: Proof abundance for all

Leanstrad 1.5 is an Apache‑2.0‑licensed proof‑engineering model for Lean 4 with 119 B total parameters and 6 B active ones. It is trained in three stages—mid‑training, supervised fine‑tuning, and RL with CISPO—using two environments: a multiturn theorem‑proving loop that iteratively refines proofs via Lean compiler feedback, and a code‑agent loop that edits files, runs bash commands, and interacts with the Lean language server to complete long‑horizon proof tasks. Benchmarks show full coverage of miniF2F (100 % validation and test), 587/672 solved on PutnamBench, and state‑of‑the‑art results on abstract‑algebra suites (87 solved on FATE‑H, 34 on FATE‑X). Pass@8 scales smoothly with token budget, reaching 587 solved problems at 4 M tokens. Case studies demonstrate practical code verification: Leanstrad proved AVL‑tree insertion/deletion time bounds over 2.7 M tokens, and an automated Rust‑to‑Lean pipeline flagged 47 property violations across 57 repositories, uncovering 11 real bugs (5 previously unreported). The model, weights, and a free API endpoint are hosted on HuggingFace and usable via Mistral Vibe.
Read full article →
The discussion acknowledges the release positively but questions the choice of the zig‑zag decoding overflow as a flagship bug, arguing it reflects typical testing oversights rather than a uniquely hard case and noting the library’s low usage and limited test coverage. Critics point out that the model comparisons are outdated, that Europe’s AI ecosystem appears lagging, and that prompt sensitivity hampers reproducibility, while others appreciate the progress in Lean‑based automated proof tools and suggest clearer guidance on inputs and prompt construction.
Read all comments →

GLM5.2 on AMD MI355X at 2626 tok/s/node at over 2x lower cost than Blackwell

The article compares AMD Instinct MI355X GPUs to NVIDIA Blackwell (B300) GPUs for large‑language‑model inference. AMD hardware costs ≈2.75× less while offering comparable silicon specs, but NVIDIA’s software stack provides superior day‑0 support, making AMD inference slower and harder to set up. Wafer achieved a performance‑per‑dollar improvement on the MI355X by: * Quantizing GLM‑5.2 from bf16 to AMD’s MXFP4 format using AMD Quark, achieving lossless accuracy versus FP8. * Selecting the sglang inference engine (vLLM lacked MXFP4 support; ATOM degraded at long context) and fixing its ROCm image to enable speculative decode, including correcting module‑prefix mismatches for the MTP head and adding a ROCm guard to the fused metadata kernel. * Applying configuration flags (`--kv-cache-dtype fp8_e4m3`, `--enable-aiter-allreduce-fusion`) and tuning MoE kernel selection for fp4 shapes (model_dim 6144, moe_inter 2048, E 256, topk 8). * Optimizing tensor parallelism (TP4×DP2) for prefill‑bound workloads, raising throughput from ~1461 to 2626 tokens / s / node at 2.4 RPS, which is 80 % of Blackwell performance at >2× lower cost. The results demonstrate that with proper quantization, framework fixes, and kernel tuning, AMD GPUs can approach NVIDIA performance while delivering significantly better cost efficiency, indicating the CUDA advantage is diminishing.
Read full article →
Comments emphasize a need for clearer performance‑per‑watt data to assess AMD’s competitiveness against Nvidia, especially for data‑center deployments where electricity costs are high. Many express skepticism toward benchmark claims that rely on aggressive quantization, noting apparent accuracy drops and questioning real‑world relevance. There is interest in software support and pricing details, with concerns about sourcing AMD hardware and its economic viability. Overall, the discussion reflects cautious optimism about AMD’s potential but doubts about current metric transparency, benchmark integrity, and practical deployment economics.
Read all comments →

MSI Center – How to gain SYSTEM privileges in seconds

The author examined MSI Center, preinstalled on MSI laptops and desktops, by extracting its offline installer (identified as Inno Setup) and decompiling the 170 bundled executables (mostly C#) with ilspycmd; a subset of C++ binaries were inspected in IDA. Searching for insecure patterns revealed that the “Notebook Foundation” service creates a named pipe (\\.\pipe\MSI_SERVICE_2) on boot with permissions allowing any authenticated user to connect. The pipe accepts commands that can read, write, or delete registry keys, manipulate WMI settings, execute or terminate processes, all under the LocalSystem account. Communication is encrypted with 3DES using a client‑provided string as the key; the service brute‑forces decryption against registered client names, enabling privilege escalation when a payload is successfully decrypted. A proof‑of‑concept launches cmd.exe as LocalSystem, and the exploit can be triggered remotely via SMB if valid credentials exist. MSI patched the issue within two days of report (09‑05‑2026 discovery, 01‑06‑2026 patch release) but did not issue a CVE; a CVE request is pending review.
Read full article →
The comments express overall satisfaction with MSI’s quick patch response, noting the company’s prompt communication about the update timeline. However, they also criticize the underlying software design, calling it poorly written and questioning the continued use of deprecated 3DES encryption, which is viewed as a security red flag. The author seeks more technical detail on the fix and speculates that the patch might have introduced another vulnerability, reflecting lingering uncertainty despite the favorable resolution.
Read all comments →

Steam Controller Auto-Charge – pilot to magnetic charging puck using CV

Steam Controller Auto‑Charge is an open‑source web app that autonomously pilots a Steam Controller into its magnetic charging puck using computer‑vision and WebHID. It tracks user‑selected points on the controller and puck via OpenCV.js optical flow (Lucas‑Kanade) from an overhead webcam. The app communicates with the controller through WebHID, sending 70 Hz asymmetric haptic pulses to the dual LRAs for navigation and reducing pulse frequency by 50 % within 150 px of the puck (Proximity Creep Mode). Battery status is read by intercepting HID Report 0x79 (ID 121) for charging confirmation and Report 0x43 (ID 67) for live percentage and cell voltage. The front‑end is built with Vue 3; tracking logic includes a PID loop, object‑avoidance via an in‑browser Rust/WASM CNN, and off‑loaded detection in a Web Worker. The only dependency is Nix; the app runs on Windows, macOS, and Linux in Chromium‑based browsers with WebHID support. MIT‑licensed.
Read full article →
The discussion highlights a controller that moves across a tabletop using its haptic motors, with a video demonstration provided for clarification. It is compared to a similar iPhone cycloramic app, noting the similarity in concept. Comments also point out the expense of acquiring such a controller and express concern that the audible vibrations could disturb nearby residents, especially when operating late at night. Overall, the tone combines informational description with criticism of cost and potential noise impact.
Read all comments →

SearXNG: A free internet metasearch engine

SearXNG is a free, open‑source metasearch engine that aggregates results from multiple search services and databases while ensuring users are not tracked or profiled. The repository provides an installation guide, a configuration guide for fine‑tuning, and links to additional documentation. Community involvement is encouraged through contribution guidelines, and users can connect via the project’s CONTRIBUTING resources. The software is released under the GNU Affero General Public License (AGPL‑3.0). The GitHub page also displays visual elements indicating organization, documentation, licensing, commit history, and translation status.
Read full article →
Comments express strong overall approval of SearXNG and related tools, highlighting benefits such as privacy, self‑hosting flexibility, ability to prioritize personal sources, and usefulness in building RAG or agent pipelines. Users note practical drawbacks including slower performance, occasional captchas or blocked engines, and instability of some external APIs, prompting reliance on API keys or alternative backends. Preferences vary between speed and result quality, with several users sharing setups involving Hister, TinySearch, and local language models, while also seeking guidance on engine configuration and hosting options.
Read all comments →

Odin, Wikipedia and engagement farming

The article recounts the deletion of the Wikipedia page for the Odin programming language through an Articles for Deletion (AfD) process, noting a 5‑to‑7 vote for deletion versus a 1‑to‑4 vote for keeping. Creator “GingerBill” and others argue that the decision reflects Wikipedia’s reliance on traditional, independent sources, which are scarce in modern software development. Tweets from GingerBill cite perceived bias among moderators, the language’s commercial use (e.g., JangaFX), community adoption, and the inadequacy of primary sources such as the language’s own website or creator statements. Casey Muratori adds that programming‑related notability guidelines are mismatched to the field, where reliable coverage often appears in blogs, YouTube, or internal documentation rather than peer‑reviewed journals. Both emphasize that strict application of existing notability rules would eliminate most contemporary programming topics. The piece suggests adding subject‑specific guidelines—e.g., metrics based on repository counts or notable code‑hosting platforms—to better accommodate software‑industry sources while maintaining Wikipedia’s standards against self‑promotion.
Read full article →
The discussion characterizes Wikipedia’s notability and source policies as outdated and overly biased toward traditional, secondary publications, creating a stark effort imbalance between article creation and rapid deletion. Contributors express frustration that obscure programming languages like Odin are removed despite community interest, while similar niche topics persist, and they criticize the opaque, administrator‑driven process that favors long‑standing editors. Some argue for broader inclusion and community reform, whereas others contend that many specialized languages lack sufficient independent coverage to merit an article. Overall, sentiment is largely critical of the current system and its perceived rigidity.
Read all comments →

The circuit that lets your brain think and see

None
Read full article →
The discussion critiques the use of artificial neural networks to model biological processes, emphasizing that real neurons rely on precise spike timing and local computation that differ from simplified network abstractions. It highlights disinhibitory signaling as a mechanism linking top‑down and sensory processing, drawing parallels to motor control, and suggests that contextual feedback likely shapes perception rather than a strictly feed‑forward flow. While acknowledging the promise of reverse‑engineering brain algorithms for advancing AI, the overall tone remains skeptical about the current modeling approach’s biological fidelity.
Read all comments →

Synthesis is harder than analysis

The article contrasts differential and integral calculus to illustrate why synthesis (global reasoning) is harder than analysis (local reasoning). Differential calculus computes a function’s slope at a point using only nearby behavior, making it algorithmic and easily automated (e.g., automatic differentiation in machine learning). Integral calculus seeks area under a curve, requiring knowledge of the function over an entire interval; no general algorithm exists for arbitrary functions, and many integrals lack closed‑form solutions, needing series expansions or numerical methods. The Fundamental Theorem of Calculus links the two as inverse operations. The author extends this mathematical analogy to software engineering, arguing that analysis breaks problems into localized components (facilitated by encapsulation and separation of concerns), while synthesis must integrate multiple components, a global task that is intrinsically more difficult. In fields like incident response and site reliability engineering, synthesis expertise is undervalued despite being essential for understanding system interactions and resolving complex issues. Improving methods for learning system-wide behavior is therefore advocated.
Read full article →
The comments collectively critique the assumption that all functions are easily differentiable, noting that certain functions lack derivatives at specific points or everywhere, and emphasizing the need for verification rather than accepting results uncritically. They also reference educational frameworks, specifically Bloom’s Taxonomy, to underline the importance of higher‑order skills like analysis and creation in mathematical reasoning. Overall, the tone is analytical and cautionary, highlighting gaps in the original claim and advocating for thorough understanding and validation.
Read all comments →

The firefighting system of the Van der Heyden brothers in 17th century Amsterdam

In the late‑1600s Amsterdam, rapid economic growth created dense fire hazards in homes, workshops, and shipyards. The city first bought dozens of Hans Hautsch water‑pumping engines (horse‑drawn, bucket‑fed) and equipped each district with ladders, hooks, tarpaulins and 28 000 leather buckets, assigning firefighting duties to four guilds. Early incidents—such as the 1669 sugar‑refinery blaze and the 1672 Blaeu printing‑office fire—revealed that the engines could not deliver water to roofs or interior spaces, especially in cold weather. Jan van der Heyden, a painter‑inventor, introduced a new fire‑engine system (with his brother Nicolaas) featuring a suction hose, a flexible “snake” hose, and an air‑chamber for continuous high‑pressure flow. After a decisive 1672 harbor fire, the city retrofitted half its engines and later ordered lightweight models for each of the sixty districts, adding regulated alarms (trumpeters, night watchmen) and monetary incentives for rapid response. From 1682‑1687 fire losses fell to 18 353 guilders (≈ 1 % of the prior decade’s losses), demonstrating the effectiveness of the integrated technical and organizational reforms.
Read full article →
The discussion reflects disapproval of superficial, reactionary replies to provocative headlines, emphasizing that the piece is a well‑crafted historical article deserving thoughtful engagement. Contributors express that the title’s wording incited unnecessary controversy and note that it has been revised to a less inflammatory form, aiming to reduce heated responses and encourage more substantive commentary. Overall, the tone is critical of low‑effort backlash while supporting the article’s quality.
Read all comments →