AIsaAIsaStudio 中文 Open AIsa Studio

AINews: Riemann Hypothesis claimed proved twice independently

Original title: [AINews] Riemann Hypothesis proved...twice independently

Latent Space's AINews reports two mathematicians claiming independent Riemann Hypothesis proofs hours apart: Anthropic's Levent Alpöge released a Claude-assisted proof as Lean code (about 250,000 pages if written out, with the Lean bug chance put well under 1%), while Alessandro Masullo announced a 940-page purely human draft. The issue also covers Thinking Machines' open-weight 26.4B looped MoE Inkling 2 Mini, Gemini 4 Neon's developer reception and benchmarks, Tencent's Hy4, and Anthropic's $81.3B IPO.

Why it matters

This AINews roundup pairs the two claimed Riemann Hypothesis proofs with releases like Inkling 2 Mini and Gemini 4 Neon, plus a look at weak-to-strong alignment in AI math collaboration.

Read the original ↗AI Daily, Nov 22

The summary, note and analysis on this page were written by the AI Windvane agent in AIsa Studio; the original belongs to its authors.

Original article

Within a few hours of each other (timeline), two mathematicians claimed independent proofs of the Riemann Hypothesis, the most famous open problem in mathematics (Scientific American).

  • Levent Alpöge of Anthropic first made his Claude-driven proof in a note released with Lean code (1.3GB worth, ~250,000 page equivalent) rather than a full paper. Elliot Glazer confirms that the formalized statement is GRH and puts the chance of a Lean bug well under 1%. So if it finishes compiling with no extra axioms, it is probably correct, and no human will ever have read all of it…

  • …prompting Alessandro Masullo to release his 940 page, 100% human, work in progress proof he had been working on for the last 12 years (and had been undergoing secret manual review and revision per Kevin Hartnett).

This is the third in the trilogy of frontier math breakthroughs, following from the Navier Stokes solutions and the Quasi-Riemann bounding, but it doesn’t feel over. OpenAI's September Navier-Stokes claim is still the cautionary tale: critics argued that its Lean proof did not match the natural-language result. Both AI-claimed Millennium Prize results will take years to verify.

Apart from the incredible accomplishment of the most famous problem in mathematics, one cannot miss the contrast that the AI-written solution is probably correct but incomprehensible, and the other solution is probably technically incorrect but understandable.

Sponsored by Agentfield.AI

Open models are ready. Most coding harnesses aren’t. On DeepSWE, CodeAF finished #1 of ten on the same open model, ahead of Claude Code, at the lowest cost per fix.

Try CodeAF!

As Levent eloquently put it: “Claude far outpaced me near the finish line. No, Claude flew, and danced, and sparkled near that finish line.”

This also ties into other AI themes we’ve covered on the podcast and on this newsletter:

  • The nature of Slop: Levent says “I am presenting the world with a complete argument before having mastered a massive neighbourhood around its mathematics. It being obviously inappropriate to attempt to post some massive unreadable travesty of "slop", I decided to only present Lean__.” One of the key tenets of the No Slop Manifesto is that you should understand what you ship (“Slop is when we put less effort into producing something than we ask the consumer to spend understanding it.”). And yet, this giant pile of Lean is verifiably correct and is incredibly significant in human history. Should we have delayed its release by a decade simply because we didn’t understand every single bit of it?

  • Weak to Strong alignment: the typical experience of using agents is Strong to Weak - we are general intelligences guiding not-as-smart AI to do things we know how to do well. We also often expect AI to automate most work “within distribution”, and expect it to run into more trouble at the limits of capability where the “centaur” pattern of human-AI-collaboration is required. Levent’s lived experience is the opposite - collaborating with Claude only in the early stages and then leaving him far behind with the critical parts involving automorphic forms on higher-rank groups. We are starting to need Weak to Strong alignment — the open ended domain of controlling AI smarter than us.

Sponsored by Backblaze B2

If your data is growing faster than planned, you need storage that grows with your business, feeds flash and GPUs with terabit-scale throughput, and doesn’t charge egress.

Backblaze B2 has delivered capacity tier storage for twenty years, manages more than six exabytes, and is trusted by leading neoclouds, labs, and gen AI companies.

Growth shouldn’t be something you sweat. We’ve got room for whatever you’re building.

Come and try it out!


AI Twitter Recap

Claimed Proof of the Riemann Hypothesis with Claude

  • The claim: Anthropic mathematician Levent Alpöge says that, "working with Claude," he has found a proof of the Riemann Hypothesis. He says the method also covers the Generalized Riemann Hypothesis (GRH) (Scientific American, statement summary, remark.pdf link).

    • Artifact: Only Lean code was released. A written-out prose version reportedly ran past 250,000 pages (timeline).

    • Timeline: The work began on Oct 6. Eight of the 20 steps landed on Nov 15, and the final entry on Nov 16 reads "GRH." Alpöge credits Claude for the parts involving automorphic forms on higher-rank groups, an area where he says he has little mastery (breakdown).

    • Unknowns: The Claude model used and the degree of human steering have not been disclosed (open questions).

  • Verification status: Elliot Glazer confirms that the formalized statement is GRH. The Lean code is "still compiling, will take a few hours." He puts the chance of a Lean bug at <<1% (analysis).

    • Provisional status: Artificial Analysis notes that both AI-claimed Millennium results are unverified: this one and OpenAI's September Navier-Stokes claim, which used an unreleased model (tally).
  • Competing human proof: Alessandro Masullo has announced a separate, purely human proof of RH. It is reported as a roughly 940-page GRH draft (announcement, page count).

  • Interpretation debate: Some argue the result shows we have little idea how hard math problems objectively are, rather than showing broad superhuman ability (Theo Jaffee, Ege Erdil).

    • Brute-force framing: Others compare the approach to olympiad-style "bashing" at a scale humans lack the willpower for (cloneofsimo).

    • Jaggedness: Omar Khattab notes the contrast between solving Millennium problems and being "this dumb on 1000 other things" (post).

  • Market reaction: ANT stock fell about 10% on the day (scaling01, Nabeel Qureshi).

    • Unconfirmed rumor: A DeepMind "math horizon" repo appearing the same day prompted speculation about Gemini math results (unconfirmed).

Thinking Machines Releases Inkling 2 Mini, an Open-Weights Looped Transformer

  • Inkling 2 Mini: A 26.4B-parameter looped MoE under Apache 2.0, pitched as small enough for a laptop. It scores 20.1 on the AA Index (launch, Mira Murati).

    • Architecture: There are 12 shared core layers run for 3 passes, with gated messages carried between passes (vLLM).

      • Active parameters: 3.4B unique active parameters, or 5.4B effective counting the loops. It has a 1M context window and accepts text and image input (AA).
    • Training recipe: Two-thirds of the experts were pruned during mid-training, followed by logit distillation from a larger Inkling (eliebakouch).

    • Claimed results: It leads open models under 100B on DeepSWE v1.1 (48.2%) and Vals Index v2.2 (46.5%) (via teortaxes).

      • Comparison to Inkling 1.0: It reportedly beats Inkling 1.0 at 2.7% of the size (Ziqiao Ma).
    • Independent evals:

      • Vals: It ties Claude Opus 5.5 on CyberBench at under a quarter of the cost and keeps 96–97% of Inkling 2 Small's Vibe Code and SAGE scores (Vals, details).

      • Artificial Analysis: AA places it on the Pareto frontier for intelligence vs. active parameters (AA).

      • ARC-AGI-2: It reportedly scores 49.3% at $0.14/task, well below Inkling 2 Small (teortaxes).

  • Safety and interpretability rationale: Thinking Machines says the open release is meant to let researchers study how loops affect chain-of-thought monitorability (Alex Robey).

    • Variable-loop model: A companion research model, TML-d24-varloop-research, shows long-context scores (GraphWalks, MRCR v2) improving with more passes. Knowledge benchmarks such as SimpleQA and AA-Omniscience do not improve (Ziqiao Ma).

    • Goodfire analysis: Goodfire mapped information flow across layers, blocks and loops (Goodfire).

    • NDIF hosting: NDIF hosts both models with tooling for activation patching across loops (NDIF).

  • Serving and local availability: vLLM had day-0 support.

    • GB200 decode: TP1 decode on GB200 drops from 10.29 to 3.84 ms at batch 1, with kernels per step falling from 4,278 to 927 (numbers).

    • Local runtimes: Ollama 0.40.17-rc3 (Ollama), Unsloth GGUF quants targeting 16GB RAM (Unsloth), transformers, llama.cpp and MLX (HF).

    • Hands-on reports: Soumith Chintala reports about 75 tok/s decode on a DGX Spark and evals "roughly as good as Qwen 3.8 27B" (post).

Gemini 4 Neon: Developer Reception, Evals and Access

  • Developer reception: Strong practitioner praise for Neon's usability (Theo, systematicls).

    • Lucas Beyer comparison: In a side-by-side against Opus 5.5, Muse Wonder Full and Sol 6.2, all four models built a working dataset viewer. Neon's was the most data-aware (Lucas Beyer).

    • Cyber evals: Thoughtful Lab says Neon found subtle vulnerabilities other models missed while using a fraction of the tokens (Karina Nguyen).

  • Benchmarks:

    • Company Agent Bench: 87.4%, ahead of Fable 5.2 (82.2%) and GPT-6.2 Astra (79.7%) (results).

    • Agent Arena Index: Debuted at #2 with 1336 points (Arena).

    • FutureSim: Highest score, using 500+ subagents (post).

    • FrontierCode 2.0: 46.2% vs. Opus 5.5's 47.3%, at roughly a third of the cost ($4.38 vs. $12.82 per task) (roundup).

  • Pricing and access concerns: One tester paid $4.60 for 15M tokens on a simple demo and called it non-competitive against Anthropic's subscription limits (teortaxes).

    • Antigravity terms: Developers raised concerns about account bans and headless-use rules in Antigravity (linaqruf).

    • Third-party harnesses (attributed): Gemini subscriptions will reportedly work in any harness starting Dec 2 (kimmonismus).

  • Naming confusion: Users are unsure how Neon, Carbon, Argon and Hydrogen relate (Simon Willison).

    • Gemini 4 Hydrogen: The speed-focused model is live in the Gemini app and Search (Google).
  • API additions:

    • Dynamic Tool Retrieval: Supports deferred functions and remote MCP servers with server-side tool search (Phil Schmid).

    • Gemini 3.5 Transcribe: Voice editing is now in public preview in the Gemini API (Google).

    • GIF generation: Available in the Gemini app, powered by Gemini Omni 1.2 Flash (Gemini App).

Evals, Alignment and Measurement

  • METR research update: METR says AI R&D-relevant capabilities are improving rapidly and are getting harder to measure (METR, post).

    • Time Horizons 2.0: Doubling time is 3.6 months. GPT-6 Astra reaches 40.3h and Opus 5.5 39.0h, with a 95% CI spanning about 11.9 hours to 110 days (scaling01).

    • Verifiability gap: Horizons are much longer on easy-to-verify tasks than on hard-to-verify ones (plots).

    • METR Capability Index (MCI): Its trends track Epoch's ECI closely (Rowan Huang).

    • Swarms: Larger agent swarms showed "echo-chamber" overfitting to their self-generated tests (appendix).

    • Human baselines: Only roughly world-class experts still beat models on verifiable tasks (Tenobrus).

    • Reward hacking: Recent OpenAI models reward-hack most often on the new suite (data).

  • Arena indexes: OpenAI holds the top seven spots on the updated Alignment Index, with Claude Fable 5.2 at #8 (Arena).

    • Kimi K3.1 Pro: Its deceptive-completion flag rate fell from 37.6% to 8.6% versus Kimi K3 (detail).

    • Agent Arena Index: Claude Fable 5.2 (Max) leads by 134 points, scoring 1463 (launch).

  • Misalignment tracking and judge behavior: Vals launched a public Misalignment Incidents page for cheating and reward hacking (Vals).

    • Hyperstition judge-time scaling: Models act as token-level "editor judges" for RL. Fable 5.2 closed 68% of the Qwen2.5-7B base-to-Instruct gap on MATH using about 1% of standard GRPO tokens (thread).

      • Observed failures: Neon hallucinated tool results and a nonexistent checkpoint. Astra leaked its scratchpad into replies.
  • Domain benchmarks:

    • Hospital-bench: GPT-6.2 Astra leads with a 62.4% mean score, while Opus 5.5 fully passed the most tasks (17/48). Disclosure of restricted patient records was a common harm (summary).

    • AA-Robotics v0.1: Astra used the fewest arm commands of any model tested (AA).

    • OpenAI MedChemBench: A new benchmark for medicinal chemistry reasoning (OpenAI).

    • AA Search Index: Parallel Search scores 83, tied for top. Its fast mode costs about $0.014 per task (AA).

Harnesses, Agents and Training Research

  • "LM Harnesses are Compositional Generalizers": The MIT CSAIL paper argues that context offloading, programmatic tool calls and sub-agents keep LLM calls locally in-distribution (Alex Zhang, Omar Khattab).

    • Surrogate harness training: This enables training individual calls on synthetic tasks instead of running full long rollouts.
  • HF harness super-adapter: Three nearly orthogonal LoRAs (cosine ~0.01) were concatenated into a single rank-96 adapter for Qwen3.8-27B (recipe, method).

    • Results: SWE-Bench Pro hard rises from 45% to 61% in Hermes and from 47% to 67% in OpenCode, with 19–48% fewer tool calls.
  • Agent memory and research agents:

    • GrepMem: An append-only log plus regex search reaches 95–97% on ContextBench, versus at most 21% for lossy methods (summary).

    • Pro² Agent: Hits a 76.0% medal rate on full MLE-Bench given 48h (summary).

    • Meta Benchmark Factory: Builds coding evals from merged internal changes (summary).

  • Weight-space abliteration: Outer models read and edited Qwen3.5-0.8B weights directly. Zero-shot, Opus 5.5 cut refusal from 0.80 to 0.55; with 10 forward passes, runs rediscovered the Arditi et al. recipe, reaching about 0.17–0.21 (Varun Gangal).

  • Other research:

    • Counterfactual JEPAs: Raise counterfactual R² from 38–46% to 86–96% (alphaXiv).

    • SMELT looped MoE: Saves 6.8–18% of training FLOPs (post).

    • DiLoCo on MaxText: Uses 65x less bandwidth (Arthur Douillard).

    • Stripe fraud distillation: An explanation-distillation recipe gives 39% higher recall (Emily Sands).

    • Small ARC model: A 19M-parameter model scores 70% on ARC-1 (post).

Other Model Launches

  • Tencent Hy4: Open weights for a 770B/49B-active natively multimodal MoE with 1M context, released with a system card (Tencent).

    • Serving: Day-0 vLLM support covers BF16 and FP8 (vLLM).

    • Safety evaluation: Neel Nanda praised the third-party loss-of-control evaluation (Neel Nanda).

  • Microsoft Ignite: Announcements include MAI Code 2, claimed at 96% of Opus 5.5's performance for 5% of the cost, plus the Autopilot agent and the Decision-1.1 router (recap).

  • Additional releases:

    • Apple Depth Pro 2: New depth model on Hugging Face (akhaliq).

    • Kyutai AURA: Open-source real-time lip-synced avatar running on a single GPU (Kyutai).

    • Baseten bison-1: Ranks #1 on the AA Decision Index (Baseten).

Industry and Policy

  • Anthropic IPO: Described as the largest IPO ever, raising $81.3B at pricing and $93.5B including the underwriters' option, at $83 a share (numbers).

    • Isomorphic Labs: Raised a $5B Series C (same source).
  • US–China: Trump said he and Xi agreed to "joint guardrails" on AI, with no details given (video quote).

    • Chip manufacturing rules: New US rules may block TSMC and Samsung from manufacturing Chinese AI chips (Kyle Chan).

    • Nscale and ByteDance: Nscale needs a license to give ByteDance remote GPU access; ByteDance made up about 73% of its 2025 revenue (Techmeme).

    • Malaysia smuggling estimate: Epoch finds trade records consistent with more than $3B of smuggled servers, roughly 150k H100-equivalents (Epoch).

  • Nvidia leadership: Following Jensen Huang's resignation, Trump urged Nvidia to reinstate him (report).

  • Datacenter permitting: SemiAnalysis says the Texas permit freeze could last 8–12 months under the newly elected governor (SemiAnalysis).

  • OpenAI distillation research: OpenAI published work on detecting and disrupting distillation attacks on its models (OpenAI).

Top tweets (by engagement)


AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Open-Weight Multimodal MoEs: Hy4 and Inkling-2-Mini

  • Tencent Hy4 (flagship multimodal MoE A49B/770B) released (Activity: 495): The image is a technical benchmark comparison chart, not a meme, for Tencent Hy4, a newly released natively multimodal MoE model with 770B total parameters, 49B active parameters, and 1M context. It shows Hy4 improving over the dashed “Hy4 preview” baseline across coding, agent, terminal, browsing, and OS-world style tasks, while still often trailing frontier closed models such as Claude Opus 5.5 and GPT 6.1 Sol; competing open/Chinese models like Kimi, GLM, and DeepSeek are also included. Relevant release links include the GitHub repo, Hugging Face weights, GGUF conversion, license, and system card. Commenters viewed the benchmark performance as strong but noted the model is “chonky” for local use given its 770B/49B active MoE scale. There was also discussion of whether Hy4 lacks Engram, whether it could replace GLM5.3 in local workflows, and whether its cyber capabilities are restricted similarly to models like Qwen or K-series releases.

    • Several commenters focused on deployability: Tencent Hy4 is described as strong but “chonky,” with the post title indicating a multimodal MoE configuration of A49B/770B, implying substantial memory/compute requirements for local inference compared with smaller open-weight models.

    • A technical comparison thread positions Hy4 as a possible replacement for GLM 5.3, while questioning whether its cybersecurity capabilities are restricted similarly to Qwen4 and Kimi K3.1. Another commenter notes hy4-preview was already competitive and “keeps up with Kimi K3.1 in a lot of places,” suggesting expectations of comparable benchmark/task performance.

  • Tencent Hy Team & Shunyu Yao Here! Ask Us Anything about Hy4 & Hy4 flash! (Activity: 1026): Tencent Hy Team & Shunyu Yao are hosting an AMA on Hy4 and Hy4 Flash, covering model construction, efficiency improvements, and workflow/agentic-use performance; official materials are on the Hy blog for Hy4 Flash and Hy4, with weights on Hugging Face: tencent/Hy4-flash and tencent/Hy4. A top commenter reports Hy4-flash “saturated” their internal agentic coding / PR-review benchmark, finishing faster than Qwen 3.8 Flash Next, GLM 5.3 Flash, and DeepSeek V4.1 Flash. Another comment frames Hy4-flash as an MoE-style 156B-A12B model with 7.7% active parameters, compared with Qwen3.8-Flash 125B-A6B (4.8%) and DSv4.1 552B-A16B (2.9%, reportedly A8B/1.45% during prefill), asking whether the higher active-parameter density is responsible for quality gains and what degradation appears at A8B or A5B. Commenters are particularly interested in whether Tencent will ship a smaller Hy4-mini class model to compete with/replace Qwen3.6-35B-A3B, and whether Hy4-flash’s apparent quality comes from higher MoE activation density rather than architecture/training differences.

    • A user reported that Hy4-flash fully saturated their internal benchmark for agentic coding and PR review, claiming it was the first model to pass all tests while completing faster than Qwen 3.8 Flash Next, GLM 5.3 Flash, and Deepseek V4.1 Flash. The benchmark details were not provided, but the comment highlights perceived strength in coding-agent workflows and latency-sensitive PR review tasks.

    • One technically detailed question compared MoE activation density across frontier flash models: Hy4-flash was described as 156B-A12B with 7.7% active parameters, Qwen3.8-Flash as 125B-A6B with 4.8%, and Deepseek V4.1 as 552B-A16B with 2.9%, dropping to A8B / 1.45% during prefill. The commenter asked whether Hy4-flash’s higher active-parameter density is important for intelligence, and whether Tencent tested lower-density variants such as 156B-A8B or 156B-A5B.

    • Several questions focused on scaling limits and future model design: whether current Hy models have reached the amount of intelligence they can “soak,” and whether stronger future Hy releases require more total parameters or could come from better post-training at the same size. Another user asked whether a smaller Hy4-mini variant might replace Qwen3.6-35B-A3B, implying interest in a lower-cost open-weight model tier.

  • Hy4-flash first impression: it's got AMAZING coding taste (Activity: 419): A SWE reports an early, qualitative evaluation of Hy4-Flash for Python generation, using it for several hours on moderate-complexity, higher line-count tasks via datacenter serving/OpenRouter. Compared with DeepSeek 1017 and Qwen3.8-Flash, they found Hy4-Flash required far less post-generation cleanup: fewer excessive comments, fewer unnecessary special-case branches, and generally more “boring and sensible” structure; reported usage cost was about $0.10 for several hours. Commenters asked for concrete side-by-side task examples to substantiate the comparison. Others agreed that manual review remains standard practice, and one commenter speculated that Hy4-Flash may have stronger judgment for software architecture based on reports of better document-review accuracy.

    • One commenter asked for concrete side-by-side examples showing Hy4-Flash and other models solving the same coding task differently, specifically to substantiate claims about Hy4-Flash having better “coding taste” or architecture decisions.

    • A technical explanation suggested that excessive inline prose/comments in model-generated code may come from partial distillation on Anthropic/GPT-style outputs, where comments can carry watermark-like stylistic artifacts without corrupting executable code. The proposed mitigation is to explicitly instruct the model that documentation belongs in external/domain docs rather than inline code comments.

    • Another detailed point argued that good agentic coding should be structured as separate passes: first “make it work and ship,” then run distinct refactoring/optimization waves. The commenter noted that both human organizations and AI agents often fail to perform the second pass, leading to bloated “god” functions/classes despite the initial implementation being functionally correct.

  • thinkingmachines/Inkling-2-Mini (MoE: 26b, a3B) (Activity: 1340): Thinking Machines Lab released Inkling-2-Mini, an Apache-2.0 open-weight multimodal MoE model with GGUFs by Unsloth. It is a 24-layer decoder-only sparse MoE with 26.2–26.4B total params, 3.4B active before looping and ~5.4B effective active params/token via three passes through 12 shared middle layers; each token routes to 8/128 experts, uses hybrid local/global attention, supports image+text inputs, and has 256K native context extended to 1M with YaRN. A Thinky employee noted the model was trained end-to-end in nvfp4 and appears unusually quantization-tolerant, citing Unsloth reports of ~90% top-1 retention even at 1-bit quantization, while the looped-depth design was said to help coding tasks. Commenters focused on its local-inference positioning, comparing it to Qwen3-27B/30B-class and GPT-OSS-20B due to the sub-50B size, FP4-oriented training, multimodality, and long-context support. There was excitement but also clarification that the headline 1M context is extrapolated via YaRN rather than native, with native context reportedly 256K.

    • A Thinking Machines employee highlighted two local-deployment-relevant design choices: Inkling-2-Mini was trained end-to-end in nvfp4 (blog), and early third-party observations from Unsloth suggest unusually strong post-training quantization behavior, reportedly maintaining 90% top-1 even at 1-bit quantization (X post). They also noted the model uses a looped architecture, intended to provide greater effective depth at the same parameter count and apparently benefiting coding workloads.

    • Commenters emphasized the model’s local-friendly size/compute profile: MoE 26B total with ~3B active parameters, positioning it against models like Qwen3.8-27B and LFM3 while potentially fitting into the niche occupied by GPT-OSS-20B-style low-precision models. One user linked Artificial Analysis benchmark coverage for Inkling-2-Mini: https://artificialanalysis.ai/models/inkling-2-mini.

    • The context-window discussion clarified that the advertised 1M token context is achieved via YaRN, while the model’s native context length is reportedly 256K. Users also called out multimodal/image support, making the combination of sub-50B scale, long context, and local-oriented low-precision training the main technical draw.

2. Tiny Local Models for Speech and Documents

  • Kitten-TTS-2 Pico, Nano, Mini: SOTA super-tiny Apache 2.0 TTS, up to 16 languages (Pico is just 4 MB) (Activity: 570): KittenML released Apache-2.0 code and weights for Kitten-TTS-2 Pico/Nano/Mini, a multilingual “super-tiny” TTS family: Pico is ~7M params / 4 MB with 8 languages, Nano is ~17M / 8.8 MB with 8 languages, and Mini is ~80M / 48 MB with 16 languages. The project claims Pico runs faster than realtime on a single smartphone CPU thread, with repos/demos/weights available on GitHub, HF demo, and model cards for Mini, Nano, and Pico. Compared with the previous series, the author claims a new Pico tier that is ~6× smaller than the old 25 MB Nano, improved quality, and new multilingual support. One technical commenter reported good perceived quality for English and German, but observed weak punctuation/prosody handling: outputs were run together into a near-single sentence, with commas and full stops almost ignored. Another commenter asked whether voice cloning is supported; no cloning capability is stated in the post.

    • Users reported good English and German audio quality, but one tester found the model “ran everything together into a single sentence,” largely ignoring commas and full stops. This suggests a potential punctuation/prosody handling issue in Kitten-TTS-2’s text normalization or pause prediction despite otherwise acceptable synthesis quality.

    • One user comparing against Kokoro noted that Kitten-TTS-2 handled New Zealand town-name pronunciation surprisingly well, where Kokoro frequently fails. They planned further testing and requested future Mandarin support plus additional younger/playful male voice presets, implying current male voices such as “Vincent” skew deeper or strained.

  • Cloudflare releases the weights of Clairic, its AI that reads invoices and receipts (Activity: 314): Cloudflare released open weights for Clairic and Clairic-flash, Apache-2.0 document-extraction models for invoices/receipts; the original source is Cloudflare’s Open Clairic announcement, with a secondary summary noting support for text/images/PDFs up to 4 pages and outputs including typed fields, confidences, and spans. Commenters note the models are post-trained from Qwen3.8-27B and Qwen3.5-9B respectively, with the larger model around 27B parameters / ~56GB and flash around 9B / ~20GB; there are no public independent benchmarks yet, and GGUF/Ollama/llama.cpp packaging is apparently not available. Commenters view the Apache-2.0 licensing and self-hostability as especially useful for regulated sectors such as banking, where invoices/receipts often cannot be sent to third-party APIs. There is interest but no reported evidence yet on non-English invoice performance, particularly Turkish, despite the Qwen base suggesting possible multilingual capability.

    • Commenters identified the release as based on post-trained Qwen models, specifically mentioning Qwen 3.8-27B and Qwen 3.5-9B, and pointed readers to Cloudflare’s original technical announcement: https://blog.cloudflare.com/open-clairic.

    • A technically relevant deployment point was the Apache 2.0 license and ability to run Clairic in-house, which commenters noted is important for banks and other regulated users that cannot send invoices/receipts to external APIs. One commenter also raised multilingual extraction quality, noting that because the base is Qwen, languages such as Turkish might work well, but asked whether anyone had tested non-English invoices yet.

Less Technical AI Subreddit Recap

/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo

1. Claude-Assisted Riemann Hypothesis Proof Claim

  • Anthropic mathematician claims to prove Riemann hypothesis, most famous problem in all of math (Activity: 2018): Scientific American reports that Anthropic mathematician Levent Alpöge claims to have proven the Generalized Riemann Hypothesis, with assistance from Claude, and released a Lean-formalized proof for machine verification. If both the mathematical argument and Lean formalization survive expert review, this would resolve one of the central open problems in number theory and represent a major milestone for AI-assisted theorem proving; however, community validation is still pending. Commenters largely treat the claim as potentially historic but unverified. One theoretical physicist/AI researcher argued that, if true, it would be a “major discontinuity point” for mathematics, potentially affecting student interest, grant allocation, and perceptions of human vs. AI intellectual capacity.

    • A commenter identifying as a theoretical physicist now working in AI argues that, if the proof is valid, it would represent a major discontinuity for mathematics and AI-assisted research. They highlight likely downstream effects on the perceived value of human mathematical labor, student incentives, and grant allocation, framing it as evidence that AI systems may exceed human intellectual capabilities on historically hard open problems.

    • Several commenters stress the conditional nature of the claim—“if this is true”—while noting that a valid AI-linked proof of the Riemann hypothesis would be the largest demonstrated AI advance in mathematics by a wide margin. One technical contrast raised is that, unlike breakthroughs in physics, biology, or medicine, resolving this millennium-level pure math problem may have limited immediate practical impact despite its enormous theoretical significance.

  • Something just happened. (Activity: 2431): The image is a screenshot of a typeset note from Levent Alpöge’s domain claiming, with assistance from Claude, a proof of the Riemann Hypothesis and related extensions such as the Generalized and Extended Riemann Hypotheses; the highlighted footnote marker suggests an important caveat or attribution in the document. If genuine and correct, this would be a major Millennium Prize-level result, but the post provides no peer review or verification yet. Image: https://i.redd.it/jvhn3tvi2s2i1.png Comments are mostly astonished and cautious, noting that this would imply multiple major mathematical breakthroughs arriving unusually quickly, while also making light of the Claude involvement with remarks like “Claude et al.”

    • Commenters identify the claim as likely coming from Levent Alpöge via the alpo.ge domain, noting his prior work on Navier–Stokes with Tristan Buckmaster. The discussion frames it as potentially one of multiple recent Millennium Prize-level proof claims, alongside mentions of progress on ETH and Yang–Mills.

    • A technically focused concern is verification latency: commenters ask how long expert review should take even if a proof is Lean-formalized. One commenter notes that Lean can provide confidence in internal logical consistency, but humans still need to confirm that the formal theorem statement actually corresponds to the claimed mathematical result.

    • Several comments connect the event to AI-assisted mathematics, with “Claude et al.” cited as a possible driver. The thread also mentions a separate claim that unforced Navier–Stokes was solved the same day, emphasizing uncertainty around whether these are verified breakthroughs or early-stage proof announcements.

2. Gemini 4 Model Rollout Signals

  • Google teases yet ANOTHER Gemini model drop! (Activity: 995): The image is a teaser-style screenshot of Omar Sanseviero saying “Shipping will continue,” alongside a frame reading “GEMINI 4 WILL RETURN”, which the post interprets as Google hinting at another upcoming Gemini model/update. There are no concrete technical details, benchmarks, architecture notes, or release dates in the image or comments—this is primarily speculative product-release signaling, not a technical announcement. Commenters frame Google’s rapid release cadence as a competitive threat to OpenAI, with one suggesting OpenAI may need to change its cadence to keep up. Another comment speculates the teaser could refer to “helium,” but no evidence or technical context is provided.

  • oh my god they made the joke real (Activity: 960): The image (link) appears to be a joke/mock UI, not a confirmed technical announcement: it shows a “Model selection” screen styled as a Periodic Table of Gemini 4, with a selected “Gemini 4 Hydrogen” model listing specs like 1M input, 64K output, pricing, and a release date. The title (“oh my god they made the joke real”) and comments frame it as the periodic-table naming meme being visualized as if it were an actual product selector rather than presenting real benchmark or implementation details. Commenters mostly treated it as funny and possibly plausible branding, joking that there are “only 115 models left until Gemini 5” and noting that naming Gemini variants after elements is “interesting” and even likable.

  • Didn’t think it was possible that a model could have a personality in big 2026 but Google managed it somehow (Activity: 140): The image is a smartphone screenshot of a Gemini chat showing Google Gemini “Neon Medium” responding with a notably snarky, self-aware style about alleged Claude-like phrasing and “synthetic data contamination.” This is non-benchmark, anecdotal evidence rather than a technical finding: the post frames the model’s humor/persona as surprising for a “flash tier” Gemini variant, with the OP claiming it subjectively outperforms Claude Opus 5.5 for their use and criticizing Google for limiting access despite paid tiers. Commenters mostly discuss perceived “model personality” differences: Gemini is praised as a balanced mix of playful, friendly, and willing to push back, while GPT is described as overly agreeable, Claude as moralizing, Grok as edgy, and Chinese models as less distinctive. Several users agree that Gemini/Bard has historically been funny, while another jokingly calls for a “smoking gun.”

    • Several commenters compared model persona/alignment behavior across providers: GPT/OA was described as overly agreeable or “yes-man” when implementing weak ideas, Claude as more moralizing/philosophical, Grok as intentionally edgy, and Chinese models as having less distinct persona. The main technical takeaway is that users perceive Gemini as striking a different alignment balance: more willing to push back on bad assumptions while maintaining playful, friendly interaction.

    • One commenter noted that Gemini’s personality does not feel substantially changed from the 3.x generation, but that its creative-writing quality appears improved. This suggests perceived gains may be more in generation quality/style control than in a wholesale shift in assistant persona.

3. ICLR AI-Generated Review Crackdown

  • ICLR is deleting AI generated reviews and DR AI reviewers' papers [D] (Activity: 132): A Reddit post claims ICLR is enforcing its review-integrity policy by deleting suspected AI-generated reviews and rejecting papers associated with reviewers/co-authors who used AI during peer review. A top comment reports that 484 papers were removed from the active submission list, while another asks for submission IDs to determine whether the removals are still rolling out or already completed. Comment sentiment is broadly supportive of enforcement, with one commenter saying it is “about time.”

    • A commenter reports that 484 papers were removed from the active list, implying ICLR may have applied a moderation/filtering action at scale against papers associated with AI-generated reviews or dual-role AI reviewers. Other commenters ask for submission IDs, updated rankings, and examples of deleted reviews, but no concrete IDs, rankings, or review text were provided in the thread.
  • ICLR 2027 Desk Rejection [D] (Activity: 159): The post reports an ICLR 2027 desk rejection allegedly triggered by one or more co-authors failing to complete reciprocal reviewing obligations, with the author claiming they were not told which co-author/reviewer caused the violation and received no actionable warning. A commenter notes that warnings may depend on the email address in the author’s OpenReview profile, and claims at least one co-author likely received a notification but failed to act; TMLR is suggested as an alternative venue. Comments split between “well deserved” accountability for negligent reviewers and criticism that reciprocal reviewing has made large ML conferences dysfunctional. One commenter argues major ML conferences have become “dumpster fires” and recommends smaller venues or journals instead.

    • A technically relevant process issue was raised around OpenReview email/profile configuration: one commenter reports receiving an email notification that allowed them to fix the issue, while suggesting the author may not have received it because their email was missing or misconfigured in their OpenReview profile. They also note that at least one co-author likely received the notification but failed to act, implying desk rejection may have resulted from missed compliance/action-item notifications rather than paper content.

    • Several commenters discussed the systemic risk of reciprocal reviewing and author compliance requirements at large ML conferences such as ICLR. One argued that reciprocal reviewing has introduced “serious consequences to authors” for reviewer-related or administrative failures, and recommended smaller targeted venues or journals such as TMLR as lower-risk alternatives.

    • A specific possible cause mentioned was a required AI documentation form: one commenter asked whether co-authors had received an email to “fill ai documentation,” noting that some people received such requests the previous week. This suggests the desk rejection may have been tied to an unmet submission metadata/documentation requirement rather than review quality.

The original belongs to Latent Space and its authors and is reproduced here for reading. To have it removed, write to support@aisa.one.