AI Frontier Daily Briefing: 2026-10-26
84 stories on the 2026-10-25 (UTC) Hacker News front page, 17 with more comments than upvotes. Judgment line: Apricitas tallies 200k US media, film and arts jobs lost in four years and asks how much is AI (527 comments, the day's busiest thread); a long essay argues AI demolished the software 'toll booth' and OpenAI and Anthropic handed dynamite to everyone outside it; r/opensource bans solo projects and anything built with LLMs (posted from a 24-minute-old account, authenticity disputed); Meta defies a Brazilian electoral court's 24-hour deadline as WhatsApp searches for 'brasil' surface Bolsonaro and Meta AI returns both candidates' ballot numbers as 'random'; Fields Medalist Borcherds stops grading homework for correctness (236 comments to 154 points); Nikon strips a microscopy prize after scientists spot AI-altered cell structures. Models line: Cerebras details running a 3-trillion-parameter Kimi K3 across 59 wafers at 1000-2000+ tok/s; a 10-year-old Inception v3 hits 62% on skin-cancer diagnosis vs 42% for GPT-6 Astra and Claude Fable 5.1; GVS5H gets five Qwen3.8-27B models to share a ledger and beat Fable 5 on LiveCodeBench Hard (92.4% vs 90.4%); Destined AI open-sources Hurston-1, a 3B TTS covering Southern American and six African English varieties with a telephony mode. Security line: Wiz's Gheist report - 850+ accounts, 13.5k ci-sync branches printing secrets, GitHub's new workflow approval hold blocking every public run; Bugsink on Brotli fixes shipped 8 months late; Dreamhost forces password resets and warns against email links. Governance line: France's PM asks four ISPs to stand ready to cut TikTok, Instagram, Snapchat and X; FOSDEM 2027 opens a Digital Dissident devroom. Tools line: Wide Events resurfaces; bbtree claims the fastest ordered map (Turso inserts 2.22x); a collection of tiny programs; FindMyWeb builds your own tracker on Apple's Find My network; a blog reworked for AI agents; the Figma numpad mystery traced to a 1981 IBM decision. US shift adds 8: a researcher zero-days his own 2025 Samsung TV for root, finds Bixby mic audio and screenshots feeding ad targeting (841 points, top of the day; OpenAI banned him for 'cyber abuse'); JetBrains open-sources the agentic IDE Thinkrail; Drew Breunig divides context engineering's history, 2026 is harness engineering; Goose, the day's #1, is a new language whose compiler is mostly Claude-written; Overgrown lets neglected tabs grow vines; Farol maps PR risk for the human approver; Google turns three Nest thermostats back into dumb ones; William Gibson's fictional AI Eunice is argued near arrival. 29 items.
84 stories made the 2026-10-25 (UTC) HN front page; 17 had more comments than upvotes. Today’s headlines sit almost entirely on the judgment line: who gets blamed for 200,000 creative-class jobs (527 comments, the day’s busiest thread), whether the software toll-booth model survives AI, and platform neutrality getting audited item by item in a Brazilian election. The models line is specialist vs generalist: a wafer-scale writeup of a 3-trillion-parameter Kimi K3 deployment, and a 10-year-old CNN pinning frontier LLMs at 42%. Security brings Wiz’s full Gheist postmortem; tools bring wide events, a fastest-ordered-map claim, and a blog rebuilt for AI agents. The US shift adds 8: the 841-point Samsung TV root shell and its author’s OpenAI ban, JetBrains’ agentic IDE Thinkrail, a field history of context engineering, Goose (the day’s #1, mostly compiled by Claude), the Overgrown tab extension, Farol’s PR risk maps for human approvers, three Nest thermostats bricked back to manual, and the case that Gibson’s Eunice is nearly here. 29 items.
1. 200k creative-class jobs gone in four years. How much is AI?
Digital arts shrink, live shows grow. Draw your own line.
Economics blog Apricitas runs the BLS numbers: the US media, film and arts industries shed over 200,000 jobs in four years, roughly 50,000 in the past year alone and accelerating lately. Film and sound recording lost more than 100,000 - about a third of the sector, a 30-year low; written publishing is down over 70,000. The author concedes precise attribution is hard - companies hide AI use for copyright reasons - but the pattern is stark: every digital-arts subsector shrinks while in-person entertainment grows; only ~32% of arts workers use generative AI versus 62% across all industries. 492 points, 527 comments, the day’s busiest thread. If you build content or creative tooling, this is direct evidence the demand side is contracting. Source · HN discussion
2. A free Photoshop clone in a weekend? The toll booth loses its gate
$20-a-month dynamite, sold to everyone in line.
The essay’s core claim: software companies like Adobe charged recurring fees because building competitors was slow and expensive, and AI removes that scarcity - hobbyists now clone flagship tools in a weekend, and the money doesn’t migrate to the AI labs, it evaporates. OpenAI and Anthropic’s plan was to sell AI software engineers to companies like Adobe and pocket the saved salaries; instead their ~$20/month subscriptions armed everyone outside the toll booth. Meta open-sourcing Llama on Feb 24, 2023 broke the artificial scarcity, and open-weight models rent cheap. The numbers cited: ~$500B in combined 2026 capex from Amazon, Alphabet and Meta, mostly AI data centers; Adobe stock at its lowest since 2019. 81 points, 93 comments. If your pricing rests on scarcity, this is the re-pricing memo. Source · HN discussion
3. r/opensource bans solo projects - and anything built with LLMs
Would a one-person XZ backdoor even be postable?
The subreddit’s mods announced a new rule: no solo projects, no projects using LLMs at all, even when the output isn’t slop. Complication: the announcement came from a 24-minute-old throwaway account, and HN users report a spam wave of such posts that moderators are banning as they appear, so the rule’s authenticity is disputed. 75 points, 103 comments, split between “AI project announcements drowned the subreddit” and “by this standard, Bernstein’s software - and the Linux kernel, which accepts LLM contributions - wouldn’t pass.” If you run an open-source project, distribution channels are turning AI exclusion into an admission gate. Source · HN discussion
4. Meta ignores a Brazilian court order - R$500k in fines per day
“Technical failures,” said every platform, ever.
Justice Marco Aurélio Bellizze of Brazil’s Superior Electoral Court ordered Meta to apply identical criteria to Lula’s and Flávio Bolsonaro’s campaigns, with a fresh 24-hour deadline on Sunday; Meta didn’t comply, facing R$500,000 (~$99k) per day, doubling to R$1M. Evidence collected by Sleeping Giants Brasil and CTRL+Z: a WhatsApp GIF search for “brasil” surfaced Bolsonaro with his ballot number, Instagram suggested “#lulaladrão” as the first Lula hashtag, and Meta AI asked for a random number 1-25 returned 13 and 22 - both candidates’ ballot numbers. Meta denies favoritism, blaming “technical failures.” Also on the front page the same day: Al Jazeera reports Meta employees said Lula’s accounts were restricted during the election (178 points, 134 comments). Together the two threads drew over 600 points. If you run recommendation systems, this is platform neutrality audited line by line in court. Source · HN discussion
5. Fields Medalist stops grading homework - AI wrote it anyway
Looms replaced weavers. Now it’s the math department.
UC Berkeley professor and Fields Medalist Richard Borcherds said in an interview that watching students routinely use AI for top scores made paying readers to grade homework pointless; he now gives completion credit and concedes it’s “not a very good system” with no alternative in sight. He expects AI to surpass human mathematicians at everything within a few years if progress holds, and is no longer sure whether to advise students into math. The context: OpenAI’s claim last week that agents solved the Navier-Stokes existence and smoothness problem. Campus-wide, the Academic Senate only requires AI-use statements in syllabi; Berkeley tested Turnitin and Rumi and found detection inadequate to standardize. 154 points, 236 comments, a 1.53 comment ratio - one of the day’s most contested posts. If you build education products, homework evaluation just lost its anchor. Source · HN discussion
6. Nikon strips a photo prize after scientists spot AI-altered cells
Cells popping in and out of existence?
At Nikon’s 16th Small World in Motion competition, the winning entry by Tsinghua’s Dr. Ning Xu - time-lapse of cilia beating in a child’s airway - was disqualified after scientists flagged cell structures that changed size and popped in and out of existence, a University of Florida associate professor calling it textbook AI generation; a UT Southwestern PhD student also found a suspected AI watermark in the source image, and two former judges had questioned it. Xu admitted in a since-deleted LinkedIn post to using AI in post-processing to “distinguish and visualize features,” denying generating the footage. The prize passed to Nguyen Nam Nhat of Vietnam, and Nikon said it will revisit the rules. 125 points, 61 comments. If you ship generated content, this “structural anomaly plus source watermark” evidence chain is worth studying. Source · HN discussion
7. 3 trillion parameters across 59 wafers - Cerebras shows its work
Wafer-scale plumbing, documented end to end.
Cerebras published a detailed explainer on deploying trillion-parameter models on wafer-scale hardware, using the open-source Kimi K3 (~3T parameters, 69 linear-attention plus 24 dense layers) as the worked example. The design: 1) each WSE-3T wafer holds 44GB of on-chip memory, weights at 4-bit and KV cache at 8-bit, about 16GB per layer; 2) each wafer runs two linear-attention layers or one dense layer, 59 wafers total; 3) only activations cross between wafers over RDMA-on-Ethernet, roughly 2 microseconds per hop. Target generation speed is 1,000-2,000+ tokens/s, with tokens-per-megawatt at equal speed as the headline metric. Cited model scores: 88.3% on Terminal-Bench 2.1 (GPT-5.6 Sol: 88.8%) and 91.2% on BrowseComp. 339 points, 123 comments. If you track self-hosting economics, this is the most complete public wafer-scale deployment writeup available. Source · HN discussion
8. A 10-year-old CNN beats frontier LLMs at skin cancer, 62% to 42%
Great at everything, worse at one thing that matters.
Dermatology consultant Magnus Lynch (King’s College London) ran a blind test on 200 biopsy-proven lesions: a 2015 Inception v3, fine-tuned on 68,011 ISIC archive images and deliberately not state of the art, got 125/200 (62%) first-choice diagnoses versus 84 (42%) for GPT-6 Astra and 85 for Claude Fable 5.1; with second choices counted it was 173 vs 134 and 138, and melanomas were found 13/30 vs 8 and 11. The CNN ran entirely in a phone browser over WebGPU. His caveats: the test set was small, all-biopsy cases are harder than typical, the MILK10k dataset has been public since 2025 so LLMs may have trained on it, one run per case. 306 points, 158 comments. If you build vertical medical AI, specialist small models are still at the table. Source · HN discussion
9. Five Qwen3.8-27B models share a ledger and beat Fable 5 on LCB Hard
Same score as the frontier model, one-fifth the price?
GVS5H (named for “Gorilla vs 5 Humans”) implements ledger-based zero-shot self-orchestration: fresh instances of one model split the problem and coordinate through a shared filesystem holding the plan, notes and current solution - no training involved. On the 100 latest LiveCodeBench Hard problems (LCB-100, pass@1), the author reports open-weight Qwen3.8-27B jumping from 66.8% to 92.4%, past Fable 5’s 90.4%, with Qwen3.8 Flash Next at 93.0% for 9% of the cost; across 11 models, gains up to 25.6 points. Code is MIT-licensed, roughly 966 stars at snapshot. The author warns gains aren’t universal - some models are unchanged or worse. 180 points, 67 comments. If you build agent orchestration, a shared ledger is the cheapest collaboration baseline to try and to verify. Source · HN discussion
10. Hurston-1: an open 3B TTS that speaks Southern and African English
Synthetic callers, now with regional accents.
Destined AI released Hurston-1, a 3B-parameter English TTS fine-tune of Maya Research’s Maya1, covering American, Southern American and six African English varieties (Nigerian, Yoruba-Igbo, West African, East African, Swahili-East African, Southern African); weights are Apache-2.0. Training used LoRA (rank 64) for 2,000 steps on ~190 hours, ~136 of them from a consented, paid corpus including about 10 hours of real AI-voice calls. The distinctive feature is NB-TTS “phone mode,” emitting 8kHz G.711 audio straight for Twilio-style telephony; limits include no voice consistency across calls and weak names, dates and amounts. 24 points, 10 comments. If you test voice agents or IVRs, this gives you a dialect test-data generator. Source · HN discussion
11. 850 accounts, 13,500 branches - Gheist weaponizes stolen tokens
No C2 server. GitHub itself is the channel.
Wiz details the Gheist campaign (tracked since Sept 15): stolen GitHub tokens plant a ci-sync- branch plus .github/workflows/sync-check.yml in every reachable repo, committed as ci: sync config; the workflow prints environment variables and the secrets context through base32 -w 120 - GitHub masks secrets only verbatim, so encoded secrets print in full - and the operator pulls the log via API and deletes the run within seconds. Scale: 850+ compromised accounts and 13,500+ branches; from Oct 19 a sync-host job also targeted self-hosted runners, hunting 31 token formats, private keys, Terraform state and cloud metadata. GitHub’s July 28 approval hold for suspicious workflows in public repos blocked every observed public run, but private repos and GHES aren’t covered and exploitation succeeded; as of Oct 24 the attack is ongoing and roughly two-thirds of implicated accounts are gone. Hunt for ci-sync- branches, runs deleted within a minute, and the gheist user agent - and rotate every repo, org and environment secret. Source · HN discussion
12. Patched in February, shipped in October: Brotli’s security lag
A compression library with a supply-chain problem.
The Bugsink author catalogs Brotli’s maintenance record: a memory-corruption flaw in the decoder (CVE-2026-111497, the root of Node2Shell/HTTP2Shell) was fixed by Google on Feb 27, 2026, but the release only landed Oct 21 - after Node’s public advisory. An earlier decompression-bomb DoS fix was publicly committed Sep 17, 2024, yet the C release took over a year; the Python API change was poorly documented, Scrapy stumbled, urllib3 added a limit only on Dec 5, 2025 and shipped a second patch ~153 days later under GHSA-mf9v-mfxr-j63j. His conclusion: seriously question whether you need Brotli support at all. 21 points, 7 comments. If you depend on upstream C libraries, response latency belongs in your selection scorecard. Source · HN discussion
13. Dreamhost forces password resets - and tells you to ignore its emails
A real reset wave makes perfect phishing weather.
Dreamhost began investigating File Manager connectivity issues on Oct 23 afternoon, which spread to FTP/SFTP and webmail; that evening it started precautionary password resets for “some email and FTP/SFTP users,” invalidating old passwords, with the reset flow completed Oct 24 and most notification emails out by midday Oct 25. The root cause hasn’t been disclosed; the company repeats that it will never email asking for your password and tells users to go straight to panel.dreamhost.com, with new passwords taking up to 15 minutes to propagate. File Manager remained unavailable at publication time. 83 points, 32 comments. If you have a Dreamhost account, change it in the panel now - don’t wait for, or click, any email. Source · HN discussion
14. France’s PM asks four ISPs to stand ready to cut TikTok and Instagram
They tried this in New Caledonia. The courts pushed back.
French investigative outlet Blast obtained the letter and meeting record: Prime Minister Sébastien Lecornu asked Orange, SFR, Free and Bouygues Telecom to prepare for the Oct 24 demonstration by standing ready to cut access to TikTok, Instagram, Snapchat and X; the carriers expressed doubts in the meeting, and no shutdown is confirmed to have happened. The government used the same measure during the 2024 New Caledonia crisis and was rebuffed by the Conseil d’État. 142 points, 168 comments, a 1.18 ratio, echoing several other censorship threads on the same page. If you operate platforms, CDNs or compliance in Europe, “standby shutdown” belongs on the risk register. Source · HN discussion
15. FOSDEM adds a “Digital Dissident” devroom for developers under threat
The weakest link in the chain decides the outcome.
FOSDEM 2027 (Jan 30-31, Brussels) opens a Digital Dissident devroom, with Bogomil Shopov issuing the call: aimed at developers and researchers living under regimes like Russia, Iran, China, Belarus and Myanmar, whose safety depends on a whole tool chain - reaching the network, anonymous communication, evidence handling, secure publishing from risky devices. Submissions must include an explicit threat model and an honest account of limitations, and must avoid operational details that could endanger specific users; invited communities include Nym, Delta Chat, SimpleX, Nostr, Psiphon and the Tor ecosystem. The CfP opened Oct 24 and closes Nov 30, with speakers notified Dec 2. 284 points, 149 comments. If you build anti-censorship or privacy tooling, this is the closest thing to a field-study venue. Source · HN discussion
16. Wide Events, not “metrics, logs and traces”
Unknown unknowns need full-fidelity fields.
Ivan Burmistrov’s Feb 2024 essay resurfaced: he argues the metrics-logs-traces framing plus a 60-plus-term glossary creates mass confusion, and that traces, structured logs and periodic metric snapshots are all special cases of one thing - the wide event, a record with named fields carrying all plausibly relevant context. His example is Meta’s Scuba, where an ad-impression record carries Timestamp, AdId, UserCountry, Placement, CampaignType, UserOS, OSVersion and AppVersion, with a native samplingRate for transparent upscaling; in one incident he drilled CampaignType, then UserOS, then AppVersion, then OSVersion to isolate an iOS-Android divergence to a new OS version - no predefined metrics, no cardinality limits. He also points to Honeycomb and Axiom as exploration-first UIs, and suggests continuous profiling fits the same model. 55 points, 13 comments. If you run observability, this is the route that saves your cardinality budget. Source · HN discussion
17. bbtree claims the fastest ordered map - 5x over Rust’s std BTreeMap
Drop-in replacement, measurable speedup?
Xiangpeng Hao released bbtree, a zero-dependency, no_std-compatible ordered map with an API that swaps directly for Rust’s BTreeMap. His benchmarks: ~5x faster than the std BTreeMap single-threaded, ~12x faster than crossbeam-skiplist at 96 threads, and ~30% less memory. Real-project swaps on a Ryzen 9 9900X (only the map changed): fjall LSM memtables 2.47x on gets, Tonbo 6.83x on 10M-row writes, and Turso (a Rust SQLite) 2.22x on random-rowid inserts plus 1.90x on indexed point selects. 150 points, 19 comments. If you work on storage engines, this is a performance experiment you can reproduce today. Source · HN discussion
18. A 436-byte Lisp, 25-line DOM diffing - small is beautiful
Nobody reads a 20k-line project. Everybody reads 200 lines.
Dave Gauer’s card collects programs small enough to fit in your head: Luke Jackson’s ijk, a DOM diffing library in 25 lines of JavaScript; Philippe Brochard’s Forth in 46 bytes; Arthur Whitney’s J interpreter in one 122-line page of C, documented in Roger Hui’s Incunabulum; Justine Tunney’s SectorLISP2, a Lisp with garbage collection in 436 bytes; Frank Force’s 3D browser game in 2KB compressed. On languages, he praises Forth, Lisp and Tcl - cores that “fit on an index card” - and Lua, whose 5.1 manual covers the core language in 27 pages, quoting David Ungar: simplicity trumps expressiveness. 183 points, 29 comments. His point: a golfed program’s existence proves the concept can fit in anyone’s head. Source · HN discussion
19. Your own AirTag - FindMyWeb taps Apple’s Find My network
Apple’s moat, crossed by open source.
FindMyWeb on Codeberg is a self-hosted tracker stack with a unified web UI: a Python backend talks to Apple’s Find My network via malmeloo’s FindMy.py (initial protocol research from seemoo-lab’s openhaystack), with Google Find My Device and Samsung SmartThings support planned; the frontend is Vue/TypeScript, and a Zephyr-based firmware called FruityTag flashes onto DIY hardware - the whole chain, firmware to UI, self-hosted. 46 points, 9 comments. If you build self-hosted hardware, this is the most complete open stack from protocol to interface. Source · HN discussion
20. He rebuilt his blog for AI agents - Markdown everywhere
Content signals in robots.txt. That’s where we are.
Jake Marsh documented turning his blog into an agent-native publication: every post gets a .md version - by URL suffix or an Accept: text/markdown header, served directly by nginx; he added llms.txt and an llms-full.txt aggregating every post, plus a Content-Signal declaration in robots.txt; the JSON Feed carries a _markdown_url per item, and IndexNow notifies agents and search engines on updates. The motivation is blunt: make the blog natively readable and citable by AI agents instead of forcing them to scrape HTML. 33 points, 8 comments. If you run a content site, agent-readability is becoming the next SEO. Source · HN discussion
21. Numpad Shift+2 broke “zoom to selection” - blame a 1981 IBM keyboard
Not a Figma bug. A 40-year-old design decision.
Marcin Wichary’s classic thread (written when he took over Figma’s Twitter in 2021): on Windows, Shift+2 on the numeric keypad didn’t zoom to selection because the OS reported a down-arrow instead. The 1981 IBM 5150 crammed arrow keys into the numpad for layout reasons and invented Num Lock to switch modes; to spare users constant toggling, engineers made Shift temporarily invert the keypad mode - so numpad Shift+2 was never a 2. The behavior survived “in code through all the versions of Windows, from 1.0 all the way to 10”; the Mac never had the problem because it shipped without a numpad at first. Only when browsers exposed enough key-event information could Figma tell the two Shift+2s apart and fix it. 66 points, 9 comments. When debugging weird compatibility, the answer may be a hardware decision made before you were born. Source · HN discussion
22. Root shell on his own Samsung TV, then OpenAI banned the digger
Your TV listens. OpenAI banned the guy listening back?
Security researcher @log4j, a bug-bounty hunter, kept getting oddly well-targeted ads from his 2025 Samsung TV. The Tizen firmware is AES-encrypted with no extractable keys without tearing the set apart for UART/JTAG, so he went the zero-day route and got a root shell. Live-tweeting the dig, he reported Bixby microphone audio categorized for ad targeting, screenshots of TV usage, and cross-device identifiers in the packet logs; sets without a mic look for one on a connected soundbar or Bluetooth device. Mid-investigation OpenAI banned his account for “cyber abuse,” prompting his line: “Finally found a company that truly listens to its customers.” Commenters pushed back that dog-bark and baby-cry detection are advertised opt-in SmartThings features, so read the whole thread before crying surveillance. 841 points, 625 comments, the day’s highest score. If you build living-room hardware or privacy tooling, this is a complete data-collection forensics walkthrough. Source · Report · HN discussion
23. JetBrains open-sources Thinkrail, an agentic IDE with living specs
An IDE that maintains its own specs. JetBrains wants in?
Thinkrail is a JetBrains incubator project under Apache-2.0: a thin host that runs the open-source pi coding agent in-process and bridges it to a web UI (React 19, Zustand, Tailwind v4). It spins up isolated git worktrees as parallel workspaces, runs multiple concurrent pi sessions with a model picker, token/cost readouts and subagent delegation, and maintains a graph of SPEC.md files the agent reads and updates through spec_* tools - “specs as ground truth.” It supports MCP servers, Agent Skills, GitHub PR and CI workflows, ships as desktop installers for macOS Apple Silicon, Windows and Linux plus a CLI, pins the runtime to Bun 1.4.4 with Node.js >= 22.19, and offers English and Simplified Chinese UIs. 220 points, 164 comments. If you build agent IDEs, the specs-as-ground-truth design is the part to study. Source · HN discussion
24. Context engineering’s three-year arc ends at harnesses
Prompts weren’t enough. Context wasn’t either. Now what?
Drew Breunig (cofounder of Cmpnd, author of the upcoming O’Reilly “Context Engineering Handbook”) summarizes his AGNTCon talk: the field went 2023 prompt engineering, 2025 context engineering, 2026 harness engineering, as each capability leap moves work from probabilistic model calls into deterministic code. Context windows grew from GPT-4o’s 128K to Llama 4 Scout’s 10M tokens, yet Gemini 2.5 starts repeating actions past 100K tokens and he personally resets around 200K; METR’s long-horizon tasks now run 3.4 hours on GPT-5, 6.4 on Gemini 3.1 and 12.0 on Opus 4.6. On context inertia - agents anchoring on one hypothesis - he cites Anthropic’s Memento clearing context every ~1.5 hours, Microsoft Research’s Fork-and-Flush, and a UC Berkeley result where forgetting agents scored higher (1,144,695 vs 1,007,073). One enterprise loaded 600 skills per engineer and the agent collapsed. 205 points, 49 comments. If you build agent frameworks, this failure-mode list is a direct self-check. Source · HN discussion
25. Goose tops HN at #1, a new systems language mostly written by Claude
Human designs it, Claude writes the compiler. Fair split?
Wouter van Oortmerssen (creator of Lobster) designed Goose, and Claude Fable implemented most of the compiler - he calls it “an experiment in using AI to implement a new language, rather than reproduce an existing one”; Apache-2.0. There is no heap allocator, no GC and no lifetime annotations: dynamic values live inline on data stacks and a deeply nested structure frees in a single store; the compiler infers a root for each reference and rejects ones that could outlive their owner; references into arrays stay valid while the array grows. Relative references (T&
26. Neglect a tab and it overgrows - past 5% coverage, vines wall it off
22 tabs open, 14 fully overgrown. Time to garden?
Charlie Gerard, a senior research engineer, built the Chrome extension Overgrown: each tab runs a “neglect clock” while out of view, and plants spread from the edges toward the center the longer you ignore it. Past 5% coverage the page is walled off - scrollable but nothing is clickable, selectable or draggable. You reclaim a tab by slashing through the vines with the mouse, choosing between a rusty machete, a chainsaw or a flamethrower; she admits to 22 open tabs with 14 completely overgrown. The code is open source, split into a background worker managing the jungle per tab, a popup for settings and stats, and a content/overlay layer holding SVGs for plants and weapons plus the growth logic. 318 points, 111 comments. If you build browser extensions or want a restrained joke for tab hoarders, the three-layer structure is a clean little reference build. Source · HN discussion
27. Farol maps the risk of approving a PR, post-AI-review
Someone still has to hit approve. Show them the blast radius?
Farol (Portuguese for lighthouse) is Winnin’s open-source CLI and GitHub Action under MIT, built for the gap after AI code review and before the human approval: it diffs merge-base against head, builds a declaration graph with the real compilers (TypeScript compiler API, go/types, Python ast), computes what each changed declaration reaches - pages, API operations, RPC methods, jobs, scripts - and produces a 0-100 score in three tiers: fast track, quick review, careful review. The score drops live as you tick off reviewed files. It ingests existing CI artifacts (Istanbul, coverage.py, Go cover, ESLint, ruff, golangci-lint, npm audit, govulncheck, pip-audit) and analyzes offline: it never executes your code or sends it anywhere. Reported numbers: ~3 seconds for a 300-file Python service, 662 past commits across four repos with zero problems in 56 fast-tracked ones, score AUC 0.72-0.83. 60 points, 37 comments. If AI writes your code and you still sign off, this is the missing approval-stage tool. Source · HN discussion
28. Google turns three old Nest thermostats back into dumb ones
Buying a thermostat shouldn’t mean betting on the vendor?
Google confirmed end-of-support for the 2011 first-gen Nest Learning Thermostat, the 2012 second-gen and the 2014 European second-gen - “each over a decade old.” Cloud features stopped working on October 25, 2025: owners lost app status checks, remote control, notifications, Home/Away Assist, multi-device Eco Mode and emergency shutoff, keeping only on-device manual control and local schedules. The third-gen, Thermostat E, 2020 Nest Thermostat and fourth-gen remain supported for now. The open-source No Longer Evil firmware restores remote control, scheduling and auto-away after a flash, self-hostable or via a Home Assistant add-on. 76 points, 70 comments. If you own cloud-dependent hardware, this EOL path will eventually reach your device. Source · HN discussion
29. Gibson’s fictional AI Eunice is almost here, argues a close read
Talking isn’t the bar. Doing things while talking is?
Blogger Armin Catovic lines up the AI Eunice from William Gibson’s 2020 novel Agency against today’s products: 1, OpenAI’s GPT-Live and Dessa from Block already deliver remarkably human-like full-duplex conversation; 2, OpenAI’s Dots and Meta’s Muse pitch 7x24 agents that pursue goals and work in the background; 3, Eunice’s signature scene is quietly booking travel mid-conversation - acting in parallel with the talking is the real bar. The novel shipped roughly three years before ChatGPT and six before the current agent boom. 76 points, 74 comments. If you build voice agents, “acts while it talks” is the next metric to target. Source · HN discussion