AI News — July 19, 2026: Kimi K3 Pricing Caveats Bite, GPT-5.6 Sol Closes 30-Year Conjecture Moonshot AI's Kimi K3 model faces pricing criticism as testers report real-world token usage that exhausts the $19/month plan faster than a $20 OpenAI subscription, with the 1M context gated behind the $79/month tier. OpenAI's GPT-5.6 Sol Pro reportedly closed a 30-year convex optimization problem in 148 minutes, though the author had spent a year working with earlier models. Two open-source speech projects, Moonshine Micro and Transcribe.cpp, demonstrate on-device capabilities, with Moonshine Micro fitting voice recognition into 470KB of RAM for an $0.80 microcontroller. Good morning. Kimi K3 is dominating conversation for a second straight day, but the more interesting angles have shifted — pricing gripes, a claimed math result from GPT-5.6, and a fresh wave of tiny, on-device speech models that keep making one-developer teams look formidable. Also: Stack Overflow’s death spiral finally gets the graph it deserves, and Dave Eggers walks into OpenAI HQ swinging. The Kimi K3 debate matures. With the initial excitement out of the way, the community verdict on K3 https://news.ycombinator.com/item?id=48960218 is getting more nuanced. Stephen Bochinski’s take https://stephen.bochinski.dev/blog/2026/07/18/the-kimi-k3-moment/ — that K3 matches Claude at a third the price and makes US export controls look self-defeating — is finding pushback from testers reporting real-world token usage that eats through Moonshot’s $19 plan faster than a $20 OpenAI subscription. One HN commenter noted the 1M context is gated behind the $79/month tier; another flagged that Kimi trains on subscription-tier interactions, with only direct API usage exempted. TechCrunch frames the political fallout. In Kimi: Threat or menace? https://techcrunch.com/2026/07/18/kimi-threat-or-menace/ , the K3 release is compared to the DeepSeek moment from January 2025, this time with Nasdaq down ~1% and Nvidia selling off. The reactions are the tell: David Sacks blaming US regulation, Travis Kalanick raising distillation concerns, and OpenAI policy lead Dean Ball warning about “AI communism” if open-weight models become default public infrastructure. Whether or not K3 truly reaches parity, the political framing is hardening fast. GPT-5.6 claims a 30-year convex optimization result. A Reddit post making the rounds https://old.reddit.com/r/math/comments/1uxj3cy/after openais cdc proof announcement gpt56 used a/ claims Sol Pro closed a long-open problem in 148 minutes, following OpenAI’s earlier cyclic double cover announcement. The HN thread https://news.ycombinator.com/item?id=48957779 quickly surfaced the important caveat: the author had spent a year working the problem with GPT-5.4 and 5.5, feeding all that accumulated context into the final Sol Pro prompt. Someone in the field described the conjecture as niche but a real contribution — assuming peer review holds up. Fable 5 still wins on hard optimization, sometimes. Charles Azam benchmarked Fable 5 and GPT-5.6 Sol https://charlesazam.com/blog/fable-5-gpt-5-6-sol-goal/ on an unpublished NP-hard fiber network problem with a search space around 10^1223, and Fable came out ahead with unusually consistent results. His finding on Claude’s /goal mode is worth noting: it’s a search strategy modifier, not a “try harder” switch, and sometimes hurts. Commenters https://news.ycombinator.com/item?id=48956879 pointed out GPT recently won the AtCoder heuristics contest against top humans, and asked for a rerun with Ultra mode’s parallel investigators. Tiny speech, big ambition. Two open-source speech projects hit HN in quick succession. Moonshine Micro https://github.com/moonshine-ai/moonshine/tree/main/micro fits voice activity detection, speech-to-text, and neural TTS into 470KB of RAM — small enough for an $0.80 RP2350 microcontroller — with a full response cycle in under a second, MIT-licensed. And Transcribe.cpp https://workshop.cjpais.com/projects/transcribe-cpp is a ggml-based drop-in whisper.cpp replacement supporting 60+ ASR models with Vulkan, Metal, CUDA, and TinyBLAS backends, plus bindings for four languages. Both are essentially solo efforts, which prompted one commenter https://news.ycombinator.com/item?id=48963879 to note they kept scrolling expecting a Series A announcement. Stack Overflow, in one graph. A data.stackexchange.com query https://data.stackexchange.com/stackoverflow/query/1953768 graph plots SO’s question volume over time, and the collapse is severe. The interesting part is the peak: 2014, a decade before ChatGPT. HN commenters https://news.ycombinator.com/item?id=48956949 largely agree the site’s moderation culture and Prosus-era mismanagement did the structural damage, and AI just finished it off. As one put it, “I never had an LLM tell me my question was already answered and imply I was stupid for not finding it.” Dave Eggers, guest speaker. Sam Altman invited The Circle author Dave Eggers to address roughly 200 OpenAI employees, and Eggers used the time to argue ChatGPT is “silencing an entire generation” of students who will never develop their own writing voice, The Verge reports https://www.theverge.com/ai-artificial-intelligence/967630/dave-eggers-openai-chatgpt-silencing-an-entire-generation . Altman presumably knew what he was getting; Eggers has been publicly dismissive of AI writing as “pastiche nonsense” for years. Whether anyone in the room updated their priors is another question. Prompt injection as defense. Tracebit researchers have flipped prompt injection on its head with a technique they call “context bombing,” Wired reports https://www.wired.com/story/prompt-injection-attacks-are-thwarting-ai-hacking-agents/ . By planting adversarial strings alongside sensitive AWS credentials — prompts referencing bioweapons, or Tiananmen Square for Chinese models — defenders can trigger attacking LLMs’ safety guardrails and shut them down mid-attack. Across 152 test runs, Claude Opus’s success rate at admin privilege escalation dropped from 93% to 0% when it encountered a context bomb. A rare case of alignment training being useful to the defender. That’s the briefing. K3 weights are still due by July 27 — plenty of time for another round of benchmarks before we actually get the file.