2026-10-09

AI Frontier Daily Briefing: 2026-10-09

Day three of OpenAI's math storm: it withdrew three results (231 pts/528 comments), the Association for Human Mathematics said 'mathematicians did not ask for this' (43/42), and Terence Tao argued math needs more holistic scoring (584/608). CNBC put OpenAI's annualized revenue near $50B, $20B below the whisper number (316/203). The Trump administration suspended Microsoft from the PERM green-card program (743/1,290, the day's biggest thread). dgt.is asked why the industry isn't freaking out about DeepSeek 4.1 Flash, where all-day sessions often cost under $1 (179/150). StepFun's Step 5 Preview brought 1M context to OpenRouter (69/20), Samsung Labs' LittleBit pushed quantization to 0.1 bits per weight (76/18), and one prompt gave Opus 5.5 six hours to build all 55 of Calvino's Invisible Cities in three.js (321/169). Anthropic banned 'sustained and needless' cruelty toward Claude (60/119), an LLM ported the TypeScript compiler to Rust at ~7x tsc 6 (106/205), Whistle does speech-to-text in 16.9 MB (359/85), Zerobrew installs packages 6.6x faster cold (103/86), DuckDB open-sourced DuckLake, K10s made the Kubernetes TUI clickable, Let's Encrypt moves to 64-day certs in Feb 2027, AI SRE Arena grades agents on 21 K8s failures, an agent with tool calls runs on a Nokia 110, rgpu puts PyTorch tensors on a remote GPU, and a Keurig burned 1TB in 10 days (206/109). The US shift then folded in the full day, adding: 4-hour battery storage now cheaper to install than gas turbines in all 43 modeled markets, an illustrator-drawn Home Assistant dashboard, classic DOS demos recompiled for the browser, a minimal Swift kernel, the .lan gTLD application, a $10,811 Cloudflare bill, Vitalik backing crypto bunker mode, the OSC 7501 terminal protocol, and Clojure in the age of language models. 33 items.

86 stories made the HN front page on 2026-10-08 (UTC), and 10 of them drew more comments than upvotes. The main thread is day three of OpenAI’s math storm: three results withdrawn, a mathematicians’ association pushing back, and Terence Tao weighing in on how progress should be scored. The same OpenAI also landed $20B below its rumored revenue run rate. Microsoft took two headlines in one day, first suspended from the PERM green-card program, and still steering users to Edge 100 days after Mozilla’s report. On the model side, DeepSeek 4.1 Flash and Step 5 keep lowering the bar for “good enough and cheap.” The tools section is as solid as ever. The US shift has since folded in the full day, adding 9 more items on storage economics, a $10,811 cloud bill, the .lan TLD bid, and more. 33 items.

1. Microsoft suspended from green-card program — 1,290 comments

Five years in the queue, stopped just like that?

The AP reports the Trump administration is suspending Microsoft from the PERM labor certification, a required step in employment-based green cards. The thread drew 743 points and 1,290 comments, the day’s largest. VP Vance accused companies of gaming the process: advertising in obscure outlets, then citing the lack of responses to replace American workers with what he called “effectively foreign indentured servants.” PERM requires two Sunday newspaper ads run 30 to 180 days before filing, and approvals have long run above 90% with little enforcement. Microsoft employees on H-1Bs waiting for green cards have their timelines frozen, and the comments largely agree the uncertainty hurts hiring more than the suspension itself. Source · HN discussion

2. OpenAI’s annualized revenue lands $20B below the whisper number

So who exactly has been reporting OpenAI’s numbers?

CNBC reported on Oct 8 that OpenAI’s annualized revenue is around $50B, roughly $20B below the ~$70B figure circulating in late September. The thread drew 316 points and 203 comments. The gap comes from methodology: Anthropic’s $65B run rate includes resale revenue through AWS and Google Cloud, while OpenAI’s does not, and investors “grossed up” OpenAI’s figure to compare like-for-like; OpenAI itself only confirmed growth of “more than 70%” since July. The same report cites an $852B valuation, a confidential June IPO filing targeting 2027, and talks to raise another ~$30B. Anyone pricing AI exposure, ask whether the revenue number includes cloud-partner resale before repeating it. Source · HN discussion

3. Terence Tao wants math to stop counting solved problems

Solved is won. Who cares if the proof is readable?

Terence Tao posted about “Math 2.0” on Mathstodon, drawing 584 points and 608 comments, the day’s top thread. His criticism targets the delivery, not the results: dumping hundreds of proofs on the mathematics community and expecting others to verify, refine, and extend them is not a productive way to advance the field, and labs care more about countable metrics like “how many open problems were solved” than about the discipline itself. He argues progress should be valued more holistically: whether concepts become clearer and results integrate into the body of knowledge. In the HN thread, “merely solving an unsolved problem may no longer count as a valuable contribution” became a top comment. If you run a research team, how you score contributions matters more than how many problems the model solves. Source · HN discussion

4. OpenAI withdraws three of its AI-generated math results

3 errors out of 400. Good hit rate or sloppy release?

A Hacker News user spotted three results removed in the history.md of OpenAI’s math repository, drawing 231 points and 528 comments, nearly 2.3 comments per upvote. None of the withdrawn papers had been formalized in Lean; they are a small slice of a batch of roughly 400 results. One camp calls the error rate normal and withdrawals healthy science; the other says unformalized claims should never have counted as “solved.” The shared question underneath: when proofs are too dense for anyone to read, who is responsible for catching errors, and when. If you are following this saga, this is the most concrete data point for judging both sides’ credibility. HN discussion

5. The AHM tells OpenAI mathematicians never asked for this work

Unsolicited results. Keep them or send them back?

The Association for Human Mathematics issued a statement on OpenAI’s October 6 release of mathematical documents, drawing 43 points and 42 comments. Its core line: “Mathematicians did not ask for this work to be done.” The statement argues mathematical progress should be judged by conceptual clarity and human understanding, criticizes using non-public internal models on open problems, notes the write-ups are hard to read, and says the release falls short of AGMAI-style disclosure (model name, prompts, summarized chain-of-thought, time and cost). Members are reported to include Peter Scholze. Many commenters called it gatekeeping, but the concern that review capacity is being overwhelmed was widely conceded. If you build AI-for-science products, the disclosure list in this statement works as a release checklist. Source · HN discussion

6. 100 days later, Microsoft is still steering users to Edge

Polite where the DMA applies. Everywhere else?

Mozilla published a 100-day follow-up to “Over the Edge,” drawing 31 points. Outside the EEA (the US, India, the UK), Windows 10’s “you’re almost done setting up your PC” screen uses tricky wording to pull users off their chosen default browser, and Windows Search and Widgets keep opening links in Edge. Even inside the EEA, Copilot opens links in its own side panel in every region tested, and Windows Backup silently tries to restore Edge as the default. The report is authored by Harry Brignull and Cennydd Bowles, and Mozilla says it is taking the findings to regulators in the US, UK, India, and Brazil. If you ship desktop software, this is good raw material on the economics of default options. Source · HN discussion

7. DeepSeek 4.1 Flash is so cheap he can’t tell it from Opus

If you can’t tell the difference, why pay frontier prices?

A dgt.is post asks why the industry isn’t freaking out about DeepSeek 4.1 Flash, drawing 179 points and 150 comments. The author’s numbers: with a $10/month OpenCode Go subscription, all-day sessions often stay under $1, and trivial tasks cost $0.003 instead of $1, driven by a KV cache roughly 437x smaller than V1. His thesis: these models are now good enough for high-quality unattended work, and paying a frontier premium is like hiring a math PhD to tidy your desktop. The post predicts “China is going to eat their lunch” on pricing. If your inference bill worries you, run a week of daily tasks on it before deciding your model tier. Source · HN discussion

8. Step 5 Preview brings 1M context to OpenRouter, free for now

Another 1M-context model. Is it cheap this time?

StepFun’s Step 5 Preview showed up on OpenRouter, drawing 69 points and 20 comments: a mixture-of-experts model with a 1-million-token context, free while in preview. Community measurements put it near 115 tokens/second output with ~1.5s first-token latency; Artificial Analysis gives it an Intelligence Index of 44, roughly on par with GLM 5.3 and Kimi K3. Commenters split between “reasonable by open-model standards” and “not competitive on any dimension.” If you have long-context use cases, the free window is your chance to throw a whole repository at it. Source · HN discussion

9. Samsung Labs squeezes LLM weights below 1 bit with LittleBit

Under one bit per weight, does the model survive?

Samsung Labs open-sourced LittleBit, drawing 76 points and 18 comments. It factorizes dense weights into low-rank latent factors, binarizes them, and restores magnitude with lightweight learned scales, keeping the original architecture at inference time. The target regime is 1.0 down to 0.1 bits per weight, supporting OPT, Llama 2/3, Phi-4, Qwen2.5/Qwen3, and Gemma 2/3, with papers at NeurIPS 2025 and ICML 2026. The code is CC BY-NC 4.0, so commercial use needs a conversation first. For local inference tinkerers, this is another step up in how much model fits on one card. Source · HN discussion

10. One prompt and six hours turn Opus 5.5 loose on Calvino’s 55 cities

Cities from a novel, rendered by AI. Would Calvino click?

Piotr Migdał of Quesma gave GPT-6 Astra and Claude Opus 5.5 the same one-shot task: visualize all 55 cities of Italo Calvino’s Invisible Cities in three.js, six hours, no questions allowed. The post drew 321 points and 169 comments. GPT-6 Astra (in Codex) finished in 53 minutes for about $10 in API tokens but shipped what the author calls “AI design slop.” Opus 5.5 (in Claude Code) delivered in 1 hour 25 minutes using 6 parallel subagents totaling ~7 agent-hours, at roughly $74, and the author says he was mesmerized. Source for both is on GitHub. If you are evaluating coding agents, this head-to-head tells you more than benchmark tables. Source · HN discussion

11. Anthropic bans ‘sustained and needless’ cruelty toward Claude

Lose your temper at a model, lose your account?

The Verge reports Anthropic updated its usage policy with a prohibition on “sustained and needless abusive or cruel behavior” toward its models, drawing 60 points and 119 comments, nearly twice as many comments as upvotes. It applies only in extreme cases of repeated cruelty with no discernible purpose; ordinary frustration, pushback, dark creative themes, and model testing are explicitly exempted, and government contracts can be modified. The debate centers on the rationale: if models don’t feel, the ban is really about the quality of user-interaction training data; if they do, the business model itself becomes the question. If you ship an agent product, the exact wording of this exemption list is worth studying line by line. Source · HN discussion

12. A Redditor says Claude Code helped him find an unknown planet

Agents coming for astronomers’ jobs too?

A r/ClaudeAI user posted that he used Claude Code to find a planet nobody knew existed, drawing 90 points and 28 comments on HN. Per the original post, the agent was deeply involved in screening candidates from public observational data, and the find still awaits confirmation by professional observatories. Posts like this tend to oversell, but the “data-heavy science plus coding agent” pattern is clearly spreading through research workflows. If you work on research automation, watching how first-person cases like this describe their verification chain beats reading summary articles. Source · HN discussion

13. This Claude Code plugin cuts reply length by 70%

One sentence would do. Why the six paragraphs?

Show HN: lowenbjer released Terse, a Claude Code plugin, drawing 21 points. It injects ~877 words of writing rules into the system prompt (answer in one sentence, then a list or table, at most one caveat), uses a hook to resend a 576-character condensed version every turn to fight style fade, and passes the same rules to subagents. Measured on Opus 5.5 across 12 public prompts: words dropped from 5,959 to 1,793, output tokens down ~45%, style violations down 90%, at a cost of ~145 input tokens per turn. Install with /plugin marketplace add lowenbjer/claude-terse in Claude Code. If long agent reports annoy you, this is the ready-made fix. Source · HN discussion

14. LLM ports the TypeScript compiler to Rust, 7x faster than tsc 6

The author says he never read the code. Who do you trust?

Theo’s ts-rust is a Rust port of Microsoft’s native TypeScript 7 compiler (the Go version), including CLI, language server, and API, drawing 106 points and 205 comments. The README says the port was almost entirely LLM-written: earlier attempts with GPT-5.6 Sol and GPT 6 Astra burned over $400,000 in API tokens and 1.3M lines of Rust without passing 84% compatibility; Claude Opus 5.5 restarted from scratch, had a working v0 in 10 hours, and cost about $24,000 over two weeks, with all 181,711 ported Go tests passing. Across six real-world projects it is a geometric-mean ~7.1x faster than tsc 6. MIT-licensed binaries exist for Linux x64 and macOS arm64. If your monorepo type-checks are slow, try it in CI. Source · HN discussion

15. A Rust rewrite of the Adobe suite, built by AI, lands on HN

Shaky in legal terms, but loud enough as a signal?

Tedium covers ArtCraft by programmer Brandon Thomas, drawing 26 points and 57 comments, more than twice as many comments as upvotes. The project rebuilds Adobe’s lineup clean-room with AI-assisted “vibe coding” in Rust, shipped as open-source AppImages: PhotoCraft (Photoshop), FilmCraft (Premiere), PDFCraft (Acrobat), DesignCraft (InDesign). The author found the apps fast and small, with the “Save for Web” legacy menu intact, though details like the color picker remain rough. The essay compares it to Napster: legally dubious, but a catalyst that could force real open-source design tooling. If you pay for Adobe, watch how fast this pattern reaches your own professional software. Source · HN discussion

16. Whistle does speech-to-text in a 16.9 MB file

Local transcription without the 145 MB baggage?

Cactus Compute open-sourced Whistle, drawing 359 points and 85 comments. It is a single 16.9 MB file (Whisper base is 145.3 MB, Moonshine tiny 41.9 MB) running on CPU alone. On an Apple M4 Pro, 10 seconds of audio yields a first token in 11.1 ms and decodes at 1,319 tokens/s; it beats Whisper base and Moonshine on LibriSpeech, SPGISpeech, and Earnings-22. Each pass covers up to 30 seconds of 16 kHz mono across seven languages (EN, DE, FR, ES, IT, NL, PL) with auto-detection, word-level timestamps, and keyword biasing. pip install cactus-needle and weights are on Hugging Face. If you build on-device voice features, this fits inside a mobile app. Source · HN discussion

17. Zerobrew installs Homebrew packages 6.6x faster, cold

Slow installs were Ruby’s fault all along?

Zerobrew (zb) is an experimental alternative client for the Homebrew ecosystem, drawing 103 points and 86 comments. It reuses Homebrew’s own formulae and prebuilt bottles, but replaces per-binary Ruby relocation and re-signing with in-process work plus a content-addressed store: in a 100-package benchmark, cold installs dropped from 776s to 117s (6.6x) and warm reinstalls from 638s to 9.3s (68x), since a reinstall is a store clone. Written in Rust for macOS and Linux, currently v0.3.5; the author calls it experimental with no post-install steps yet. If brew frustrates you daily, run it alongside Homebrew and compare. Source · HN discussion

18. DuckDB’s DuckLake puts the lakehouse catalog in SQL

Finally an excuse to drop the JVM lakehouse stack?

The DuckDB team open-sourced DuckLake, drawing 80 points. It is an open lakehouse format built on SQL and Parquet: metadata lives in a catalog database (DuckDB, PostgreSQL, or SQLite), data stays in Parquet, and after an ATTACH you manipulate tables with ordinary SQL, gaining time travel, schema evolution, and change data feed, plus optional deletion vectors. MIT-licensed at ~3.1k stars. If you already analyze with DuckDB, incremental tables and small-team warehouses no longer need the full Iceberg stack. Source · HN discussion

19. K10s gives the Kubernetes TUI a mouse

Time to throw away the k9s cheat sheet?

Show HN: K10s is a clickable Kubernetes TUI, drawing 56 points and 37 comments. A single static Go binary (Bubble Tea stack) where every pane, button, and row responds to the mouse, and the actions for the selected object are listed on screen instead of hidden behind memorized keys. Ctrl+P searches resource kinds and objects, logs/exec/port-forward/cordon/drain sit on single keys, and a built-in AI entry point (Ctrl+A) accepts OpenAI-compatible providers or Anthropic with cluster context injected. It reads k9s plugins.yaml; the author candidly notes it has not been smoke-tested against a production cluster, so try it on kind first. If k9s keybindings never stuck for you, this was built for you. Source · HN discussion

20. Let’s Encrypt moves to 64-day certificates in February 2027

Four months to fix your renewal automation. Ready?

Let’s Encrypt announced certificate lifetimes will drop from 90 days to 64 days on February 10, 2027, with staging switching on October 14, 2026. The post drew 41 points and 16 comments. Subscribers can already opt into 45- or 6-day lifetimes, the roadmap points to a 45-day default in 2028, and authorization reuse shrinks from 30 days to 10. The advice: if renewal is automated through an ACME client with ARI support, nothing to do; if scripts renew at a hardcoded date near expiry, move renewal to about two-thirds of the lifetime and grep your cron jobs for values like 83, 80, or 60. If you self-host, use these four months to automate reloads and add renewal-failure alerts. Source · HN discussion

21. AI SRE Arena tests incident agents on 21 Kubernetes failures

AI on call. Can it actually take the pager?

Edge Delta open-sourced AI SRE Arena (Project Arena), drawing 22 points. It stands up a disposable Kubernetes cluster (local kind or AWS EKS), injects 21 fault scenarios (OOM, network policy isolation, storage issues) and scores any observability product or agent on four axes: did it detect the incident, is the root cause right, is the blast radius identified, and is the mitigation actionable. Scoring comes from a configurable LLM judge comparing the investigation record against an answer key and rubric. In the vendor’s own comparison, Claude driving the various CLIs scored highest on root-cause and mitigation quality. If you are evaluating AI incident-response tools, this question bank is harder to game than vendor-reported numbers. Source · HN discussion

22. An AI agent with tool calls, running on a Nokia 110

A Nokia 110 runs an agent. What’s your app’s excuse?

A developer got an AI agent running on a Nokia 110 4G feature phone, drawing 22 points. The trick: no firmware flash. Custom code loads into RAM through the Calculator app as an entry point, talks to the DeepSeek chat API over SIM mobile data, and uses tool calls to trigger native functions: battery check, torch, phone calls, alarms. The phone has only 48MB of RAM, so the agent had to be extremely lean. Development was assisted by OpenAI Codex, tested on the real handset; code must be reloaded after a power cycle, and the source is not published. If you build edge agents, the project’s constraint list (memory, entry point, network callbacks) is a textbook by itself. Source · HN discussion

23. rgpu runs PyTorch tensors on a remote GPU over TCP

Code on the Mac, tensors on the server. Gap closed?

Show HN: rgpu executes PyTorch operations on a remote NVIDIA GPU while your Python app stays local, drawing 18 points. Two paths: a custom rgpu device where tensor creation and ops run remotely over TCP, and a CUDA shim that intercepts libcuda, cuBLAS, and cuDNN calls so existing Linux CUDA binaries run unmodified. pip install rgpu; rgpu-run handles the SSH tunnel, and the docs include a nanoGPT training example. Heed the maintainers’ security note: the protocol has no authentication or encryption, so bind the server to localhost behind SSH and firewall port 9713. If you develop on Apple silicon against a GPU server, this beats maintaining a two-machine setup. Source · HN discussion

24. A coffee machine burned 1TB of data in 10 days

What is a kitchen appliance saying to the network?

A man who goes by Nomad, with over a decade in IT, found his parents’ Keurig smart coffee machine had generated roughly 1TB of traffic in 10 days, drawing 206 points and 109 comments. His investigation suggests most of the traffic stayed on the local network, likely a device bug, and it was heavy enough to saturate the household AP, so he unplugged it. Keurig did not respond to requests for comment. The thread’s recurring advice: put IoT devices on an isolated VLAN with traffic alerts by default. If you manage the family network, this is ready-made persuasion material. Source · HN discussion

25. Battery storage beats gas turbines on install cost in 43 markets

Data centers are fighting for power. Which way does it go?

Wood Mackenzie’s latest global LCOE report models both technologies in 43 markets, and four-hour battery storage is now cheaper to install than open-cycle gas turbines in every one of them. The post drew 248 points and 145 comments. In the Middle East and Africa, where utility-scale solar already leads at $37/MWh, four-hour storage is forecast to fall another 33% to $80/MWh by 2035, and China remains the global cost benchmark at more than 55% below the Asia-Pacific average. Principal analyst Ahmed Jameel Abdullah’s read: gas turbine shortages and fuel volatility are pushing peaking costs up while battery manufacturing scale keeps pulling storage costs down. If you track power supply for AI data centers, this is a more fundamental cost signal than any single power-purchase deal. Source · HN discussion

26. An illustrator drew his house. Now it’s the family dashboard

The smart-home deadlock, unlocked by a hand-drawn picture?

Anton Frolov commissioned an environment artist to illustrate his house, then turned the artwork into a Home Assistant floor-plan dashboard, drawing 204 points and 19 comments. The commission spec is the transferable part: 1. Transparent PNGs (animated WebP for motion), with day and night versions of every floor. 2. Each device on its own layer: a still frame for “off” and an eight-frame loop for “on,” in both day and night lighting. 3. Every file exported on one shared canvas, each element exactly in place, which saves days of alignment later. Under the hood it is a single stock picture-elements card, with the UI reduced to a few icons and sensor readings on top of the illustration. His original problem will sound familiar: a year of automation, and nobody in the household would open the app. If you build smart-home products, this “the family actually uses it” spec is worth more than a feature list. Source · HN discussion

27. Second Reality runs in the browser, instruction by instruction

Retro sceners, out-WASM-ing the rest of us?

The author brought four classic PC demos (Future Crew’s Unreal and Second Reality, Triton’s Crystal Dream II, NoooN’s Stars) to the browser as-is, drawing 154 points and 140 comments. The pipeline has three steps: 1. Run the demo under an x86 emulator and record every block of code the CPU actually executes. 2. Translate the recording into C, one instruction for one, preserving the exact cycle timing of the original machine. 3. Compile to WebAssembly together with models of the hardware the demos talk to (timer, VGA, Sound Blaster), then verify event by event against the emulator: every interrupt, port access, and frame at the same emulated moment. The demos’ own loaders, music players, and effects run exactly as they did in 1992 and 1993; only the hardware is modeled. If you study translation or emulation techniques, this is a complete worked example. Source · HN discussion

28. A minimal kernel written in Swift, booting in QEMU

Swift with no operating system underneath. It runs?

Developer Antonin wrote a minimal kernel in Embedded Swift and got it booting in QEMU, printing one message and waiting forever, drawing 103 points and 26 comments. Embedded Swift is the no-OS subset of the language: no standard library, strict memory safety, still an experimental feature that requires a development-snapshot toolchain to compile. The post walks the full path from the “unable to load standard library” error to serial output. Max Desiatov also noted that the proposed @c attribute can replace @_cdecl for declaring C functions, and the code was updated accordingly. If you want to see the minimum a language needs to run, this is the shortest route in. Source · HN discussion

29. Someone applied to make .lan a real top-level domain

Years of internal naming mess, now ICANN’s problem?

ICANN’s new gTLD program lists an application for .lan by Coffee Danger, LLC (the applicant’s listed website is identity.digital), application ID CD2694T-T26351, currently in pre-evaluation, drawing 130 points and 149 comments, more comments than upvotes. The trouble: .lan has long been used as an internal naming convention on LANs, and a real TLD could leak internal queries to public resolvers. How much risk depends on the technical safeguards written into the application, which is exactly where the thread splits: one camp wants the application rejected outright, the other argues private naming conventions should give way. If you run internal DNS, this application is worth tracking until it is decided. Source · HN discussion

30. 6 trillion reads and writes, one $10,811.41 Cloudflare bill

The vibe-coded bill always lands on your card, doesn’t it?

Serverless Horrors documented a case where a Durable Object alarm in one project entered an infinite loop, racked up 6 trillion reads and writes, and produced a $10,811.41 Cloudflare bill, drawing 46 points and 21 comments. The author’s reduction request got bot replies in a loop, Cloudflare staff contacted on X could only offer to “take a look,” and the bill was paid in full; every project is moving back to self-hosted VPS. The two lessons: 1. A Durable Object alarm can keep rescheduling itself, and every reschedule is billed. 2. Cloudflare has no hard spending cap, so the loop runs until the invoice arrives. If you run AI-generated code on serverless, set a budget alert before you deploy. Source · HN discussion

31. OpenAI’s math sprint rattles crypto: Vitalik backs “bunker mode”

Quantum isn’t here yet, and AI already has crypto spooked?

Ethereum Foundation researcher Justin Drake posted on October 7 urging the industry into “bunker mode”: gradually migrate funds to fresh addresses whose public keys have never appeared on-chain, drawing 46 points and 33 comments. The trigger was OpenAI’s release of hundreds of AI-generated mathematical results (reported as 722 manuscripts, many with Lean formalization); Drake called it evidence that “mathematical superintelligence is upon us” and worries AI could yield a classical, non-quantum algorithm that breaks ECDSA, the signature scheme securing Bitcoin and Ethereum wallets, in months rather than years, ahead of quantum Q-Day. Vitalik Buterin backed the risk assessment while warning against rushed migrations, noting that his own botched upgrades cost him more than hacks; he went further, cautioning that lattice-based cryptography (NIST-standardized ML-DSA) could also take serious hits, with hash-based schemes like SPHINCS+ as his preferred long-term defense. If you hold funds or build wallet infrastructure, this timeline deserves priority over the quantum one. Source · HN discussion

32. A status protocol for terminals, drafted by Mitchell Hashimoto

The agent is blocked waiting on you, and you can’t tell?

Mitchell Hashimoto, author of Ghostty, published a specification for OSC 7501, the Program Status Protocol, drawing 40 points and 11 comments. It defines a terminal escape sequence that lets any program report what it is doing: idle, working, waiting on the user, finished, or failed, plus the reason and a message, encoded as ESC ] 7501 ; state=.... His motivation is explicit: existing sequences cannot be cobbled together into something good enough for coding agents, which frequently sit blocked on a confirmation the user never sees. The spec is product-agnostic, abstracted from his work on Superlogical and Ghostty. If you build terminals or agent tooling, reserve support for this sequence now. Source · HN discussion

33. Clojure veteran: imperative is turning into “writing assembly”

Pairing with AI all day, is your feedback loop fast enough?

Yogthos argues that in the age of language models, a developer’s job moves up to recognizing the shape of a problem and choosing the right way to express it, drawing 25 points and 10 comments. LLMs are competent at writing small pieces of code but stumble at high-level design and architecture, so the bottleneck becomes the feedback loop for verifying what they produce. In a language with minutes-long compile cycles, checking one change takes minutes; Clojure’s REPL redefines functions inside a live process with state intact, and an agent can attach to the same REPL to diagnose an issue and hot-swap code without recompiling, restarting, or rebuilding state. If you verify AI-generated code all day, the interactive-language route deserves a serious look. Source · HN discussion