hot events · 2026-06-13

The only reason to click is that $965 billion number. If it holds, this would be the most expensive public debut in history, topping even the OpenAI valuation rumors from earlier this year. But I read the full article body — there's nothing beyond the headline. No revenue, no losses, no underwriter names, no roadshow timeline. A confidential filing is just the first step; final pricing is still several rounds of negotiation away. This number is more a marker of how feverish AI funding has gotten than a real price tag. I'd discount this until the S-1 drops. For now, treat it as a sentiment indicator, not a valuation anchor.

This came from Google Research's official blog and hit the HN front page, with the two sources emphasizing different angles. Google's post focuses on carbon footprint: a 64-phone cluster built from retired Pixel 4 through 6 devices, running Llama 3.2 3B and Gemma 2B at 2-3x the energy efficiency of a single TPU v5e, using the phones' existing batteries as a buffer so no extra UPS is needed. The HN thread is more pragmatic—people are doing napkin math on whether the global supply of retired phones could actually support inference at scale, and questioning whether phone SoC latency makes this unusable for real-time workloads. I'd discount this in two ways. First, the efficiency comparison is against a single TPU v5e, not a TPU cluster or a dedicated inference card at equivalent power draw—some of that efficiency gain comes from a well-chosen baseline. Second, the deployment, maintenance, and software orchestration costs for 64 individual phones are completely unmentioned, and those tend to eat efficiency wins in real-world ops. What's solid: Google is seriously exploring retired edge devices for inference. What's missing: any signal on whether this gets anywhere near production workloads.

The timeline here is what makes this worth reading: Google pledged in 2018 not to use AI for weapons, quietly removed that restriction in February 2025, and signed a classified military AI deal with the Pentagon in April. Mayrhofer says none of this went through internal discussion — leadership decided unilaterally. He also points out the company dropped its carbon-neutral goals, citing AI energy consumption. His line is blunt: Google AI products could "be used directly against me and my family." He's upfront about having an EU tenured professorship as a safety net, so quitting wasn't a financial gamble for him the way it would be for others. DeepMind researcher Andreas Kirsch also publicly said he was "deeply ashamed" back in April. Google's spokesperson response is that they're "proud" to serve national security and that AI shouldn't be used for domestic mass surveillance or unsupervised autonomous weapons. But Mayrhofer's concern is exactly about where the "any lawful purpose" clause ends. No further internal records have surfaced yet — I'll keep an eye on this one.

The reason to click: Zyphra split the classic TTS quality-vs-speed tradeoff with a sparse MoE—8B total params, only 900M active at inference, real-time 44.1kHz output. Zero-shot voice cloning is the headline: feed it a reference clip and it mimics the speaker's timbre and style, no fine-tuning needed. Text handling skips the phonemizer entirely. It reads raw UTF-8 bytes, which helps with Chinese, Korean, Japanese, and mid-sentence code-switching. Training data scaled from 200K to over 6M hours, with staged filtering to cut down hallucinations and repetitions. TTSDS prosody score of 88.7 edges out Qwen 3 TTS and ElevenLabs V3, but don't lean on one benchmark—Zyphra also released ZTTS1-Eval, a new eval suite covering 17 languages with updated evaluation models. Weights are Apache 2.0, inference and eval code are public, and it runs on Zyphra Cloud's AMD hardware. What's missing: real-world latency numbers from local setups and cloning consistency across accents. The Reddit thread doesn't have community benchmarks yet. I'd treat this as the strongest open-source TTS candidate for expressiveness right now, and wait for community latency reports before calling it production-ready.

The useful bit here is Zuckerberg saying the quiet part out loud. After cutting 10% of staff in May and shoving roughly 7,000 people into AI roles, the new Applied AI Engineering org ran a 50:1 IC-to-manager ratio — and now they're walking it back. He says the company will 'almost certainly make more mistakes' but ruled out another company-wide layoff this year. I'd read this as internal pressure relief: admit the pace was off, then throw a July hackathon and more team-building budget at morale. The memo doesn't mention Llama 4 or any model progress, so this is an organizational brake, not an AI capability problem.

The price gap here is wild: $200 a month gets you $8K–$14K worth of tokens at API rates, a 40–70x spread. SemiAnalysis bought every plan from both companies and ran heavy coding tasks until hitting weekly caps to get these numbers. I'd discount this on two fronts. First, the post doesn't say which model versions or token prices were used for the conversion—Claude Opus 4.8 and Sonnet 4.5 have very different API rates, so the 70x figure might not be precise. Second, this is a maxed-out stress test; most users won't hit weekly limits, so the actual subsidy per user is smaller. The core point still lands: when power users consistently max out their limits, the gap between subscription revenue and inference cost gets hard to ignore. Both Anthropic and OpenAI are effectively subsidizing heavy users with investor money right now, and that pricing structure won't hold long-term.

This one's worth opening because it gives a concrete upper bound for one-shot coding: not a function, but a full game idea the author held for years, turned into a playable index.html in a single run. 45 minutes of reasoning, over €20 in tokens, 2,319 lines with zero dependencies—those numbers put a price tag on "think hard, then write." I'd discount two things. The post doesn't name the exact Claude Fable version, and it never explains what "dangerous" means in Anthropic's safety framing—the title is mostly playing off the launch narrative. Also, this is one sample; we don't know how complex the game logic really is or how maintainable the output would be. The useful bit is the comparison: the author's GitHub repo logs earlier model failures on the same task, so this genuinely stumped previous systems. If you're trying to gauge whether long-reasoning models can replace the "stare at the problem for an afternoon, then code" workflow, this case is more telling than a benchmark score.

The sudden part is the blanket cutoff: all users, all sessions, Fable 5 just errors out. Elvis Saravia's take is don't panic — he already thought Fable 5 wasn't worth it for most tasks, with high cost and nerfed performance. His go-to combo is still Opus 4.8 for planning and GPT-5.5 for execution. The post doesn't spell out what the directive actually says or how long this lasts, so treat it as a temporary pull for now. If it's a security review, pricing or capability limits might shift when it comes back.