Front-page articles summarized hourly.
In Palo Alto, a downtown office building’s underground megawatt transformer was surrounded by about 2000 gallons of molten used deep-frying grease, heated by the transformer and not solidifying. The grease came from nightly dumping by nearby restaurants, mistaken for storm sewer discharge. The resulting risk of a massive grease fire prompted power shutdown, pumping out the grease, vault cleaning, and a transformer replacement. No one was harmed.
Could not summarize article.
Devlog: Zig main 2026 updates include a type-resolution redesign that lazily analyzes unused fields and improves incremental builds, plus clearer dependency-loop errors. Experimental std.Io implementations (io_uring and GCD) via std.Io.Evented, with caveats. Package workflow tweaks: local zig-pkg storage alongside build.zig and a new --fork to override dependencies. Windows API shifts: prefer native APIs over kernel32, with improvements in entropy and IO. zig libc progress: phasing out vendored C in favor of Zig wrappers via the ZCU. Personal note on local protests.
The post shows how to convert recursive code into stack-safe iterative code by simulating the language call stack with explicit mutable frames. It scales from simple lists to complex mutually recursive trees/forests, culminating in a full iterative fold built with defined frame types (FoldTreeFrame, FoldForestFrame, ExternalCaller). It uses a loop to simulate recursion, including manual memory-management considerations. The approach is validated via property-based testing to prove equivalence with the recursive reference, and benchmarked to show iterative is slower but provides stack safety. Limitations include polymorphic recursion; open questions and references are discussed.
bippy is a small JS toolkit that lets you inspect and manipulate React fibers from outside components by monkey-patching window.__REACT_DEVTOOLS_GLOBAL_HOOK__. It supports React 17–19, requires importing before React, and provides utilities to traverse the fiber tree and props/state/contexts, identify host/composite fibers, and override values at runtime. It includes functions like instrument, secure, traverseFiber, traverseRenderedFibers, setFiberId/getFiberId, getDisplayName/getType, getNearestHostFiber, getTimings, getFiberSource, and more. Caveats: development-only, fiber access varies by React version; best used for experimentation or advanced tooling (e.g., React Scan).
Cursor Cloud Agents risk credential exposure from baked-in snapshots, hardcoded env.json, no rotation/audit, and long-lived tokens. Infisical proposes using a machine-identity credential in the Cursor Secrets UI and fetching all other secrets at runtime. Steps: 1) create a scoped Infisical machine identity and store its client ID/secret in Cursor. 2) Use infisical run to inject secrets as environment variables at startup (no disk writes). 3) or use infisical export to write secrets to files (dotenv/json/yaml). Isolate access per environment; enable rotation and audit trails.
The piece explains how Firetiger’s Network Transports, starting with a Tailscale integration, let its agents access databases on private networks without exposing them to the public internet. Firetiger becomes an ephemeral Tailnet device, controlled by Tailnet ACLs and device tags; you grant access by configuring ACLs and giving Firetiger Tailscale credentials to establish a network transport. This enables Firetiger DBAs and agents to monitor and operate private infrastructure securely. A full end-to-end guide is available.
The piece argues for a scientific framework to judge when generative models are useful, based on three costs: encoding a task in a prompt, verifying the output against requirements, and whether the task is artifact- vs process-driven. Usefulness increases when encoding cost is low, verification cost is low, or the process is less important than the artifact. The author cautions that outputs are probabilistic and often plausibly but not reliably correct, so domain expertise and careful evaluation are required. In practice, many software tasks favor direct production over prompting; hype and vibes are unreliable.
Columba is an Android messaging app for the Reticulum mesh network. It sends LXMF messages and supports LXST voice calls without internet or central servers. It connects over Bluetooth LE, Wi‑Fi, LoRa via RNode, or TCP to Reticulum servers, enabling private, end-to-end encrypted messaging with no accounts or tracking. Features include location sharing with offline map downloads (MBTiles), multi-identity management with export/import and QR sharing, mesh-relay to expand the network, and customizable themes. It uses a native Android UI with Reticulum’s LXMF/ble-reticulum stack.
Tools for the Joha drawing app are being prepared.
Stanford Medicine researchers developed an intranasal vaccine (GLA-3M-052-LS+OVA) that integrates innate and adaptive immunity to provide broad protection against respiratory viruses, bacteria, and allergens in mice. Administered nasally, it protected against SARS-CoV-2 and other coronaviruses, Staphylococcus aureus, Acinetobacter baumannii, and house dust mite allergen for about three months, reducing lung virus load ~700-fold. It uses T-cell signals to sustain innate immunity. Human Phase I trials planned; two-dose nasal spray could offer multi-pathogen protection in 5–7 years.
Cloudflare introduced an experimental /crawl endpoint in Browser Rendering that lets you crawl an entire website with an API call. Submit a starting URL; the service automatically discovers pages, renders them in a headless browser, and returns content in HTML, Markdown, or JSON. Crawls run asynchronously via a job ID. Features include multiple output formats, crawl scope controls (depth, limits, include/exclude patterns), automatic discovery from sitemaps/links, incremental crawling using modifiedSince/maxAge, and a static mode that fetches HTML without a browser. It respects robots.txt and is available on Free and Paid plans. Use cases: training models, RAG pipelines, monitoring content.
An Azimuth blog post traces the Unicode U+237C ⍼ as an azimuth (direction angle) symbol. It appears in Berthold AG’s 1950 Zeichenprobe (listed as Azimut, Richtungswinkel) and in 1949 Schriftprobe (p. 104), but is absent from earlier catalogues (1946 Registerprobe and 1900/1909). The author provides scans of where it appears or would appear and notes a friend’s view that the glyph resembles a light ray through a sextant used to measure azimuth, aligning with a Wikipedia sextant diagram and Unicode typography.
A hub page from The Payphone Project centered on payphones, linking an AP 1984 story "Iowa Payphone Defends Itself" and a large archive of payphone content. The site catalogues news, photos and sounds, related media, and historical notes, with sections such as Daily Payphone, In Movies and on TV, LinkNYC, Payphone Confidential, and Payphone Radio. It features year/month archives, contributor comments, and cross-links to related Payphone Project features.
An online test that measures your ΔE OK JND (color difference). You see two colors, click the line between them, and rounds get tougher as colors get closer until you barely notice a difference. It takes about 40 rounds; most people land around ΔE ≈ 0.02. You can share results and read the post; prompts include "Round 1 ΔE OK — Your ΔE OK JND" and a referral link.
Invoker Commands API lets you assign button-triggered behaviors to other elements declaratively, enabling interaction without JavaScript downloads. Use a button's commandfor attribute to reference the element to control, and command to specify the action. The API defines CommandEvent, and extends HTMLButtonElement with commandForElement and command properties. A command event fires on the controlled element. Examples show toggling popovers, showing dialogs, or applying custom commands (e.g., rotating an image). This API improves built-in controls and accessibility; browser compatibility documented.
Could not summarize article.
Could not summarize article.
Bloomberg shows a bot-detection prompt: to proceed, users must verify they’re not a robot via a checkbox and ensure JavaScript and cookies are enabled. It references Terms of Service and Cookie Policy, directs contacting support with reference ID 546acf6d-1cc0-11f1-979d-4159b8f5303c, and promotes Bloomberg subscription for market news.
Amazon is tightening governance after outages tied to AI-assisted changes. Junior and mid-level engineers must have senior engineers sign off on AI-generated changes, as the company probes recent outages in a “deep dive.” Incidents include a nearly six-hour site outage from an erroneous code deployment and AWS issues linked to the Kiro AI tool—one 13-hour cost-calculator outage in China, and a second incident not affecting customer-facing services. Amazon says it’s pursuing safeguards and improvements; some reports tie outages to layoffs, which the company denies.
Made by Johno Whitaker using FastHTML