Friday, 17 July 2026
Moonshot AI releases Kimi K3, a 2.8-trillion-parameter model it calls the first 'open 3T-class' release; a new legal paper argues AI-agent personhood is beside the point and proposes a six-layer accountability stack instead; and São Paulo's facial-recognition network now watches an estimated 47% of Brazil's population
Today's Lead
EngineeringMoonshot AI
Kimi K3: Open Frontier Intelligence
Moonshot AI released Kimi K3, a 2.8-trillion-parameter Mixture-of-Experts model the company is calling the first 'open 3T-class model,' taking the open-weights crown from DeepSeek's 1.6T V4 Pro. The architecture, called Stable LatentMoE, activates only 16 of 896 experts per token — a design Moonshot says delivers roughly 2.5x the scaling efficiency of the prior Kimi K2 generation — and ships with MXFP4/MXFP8 quantization for practical deployment plus a 1M-token context window. It's available immediately via API at $3/$15 per million input/output tokens (predecessor K2.6 was $0.95/$4), with full open weights promised by July 27, 2026. Independent benchmarking from Artificial Analysis has K3 beating Claude Opus 4.8 Max and GPT-5.5 High on several evaluations while trailing Claude Fable 5 and GPT-5.6 Sol, and it now tops Arena.ai's Frontend Code leaderboard. Simon Willison's traditional 'pelican riding a bicycle' SVG test showed the model is capable but expensive to run — the pelican alone burned over 13,000 reasoning tokens and cost 25 cents, since K3 currently exposes only a single 'max' reasoning-effort level.
Pydantic
The human-in-the-loop is tired
The article argues that human-in-the-loop review of AI-generated code is producing a specific, underdiscussed kind of burnout: it strips developers of the cognitively rewarding parts of the job — designing, building, problem-solving — while expanding the exhausting, low-status parts, namely constant vigilant review of someone (or something) else's output. Because AI agents can generate large volumes of plausible-looking code quickly, the human reviewer's job shifts from creator to gatekeeper, a role that demands sustained attention and taste but offers little of the intrinsic satisfaction that made the work engaging in the first place. The piece contends humans remain genuinely necessary — for architectural judgment, quality control, and taste — but warns that treating review as an infinite, low-effort backstop for AI output is not sustainable, and that teams optimizing purely for AI throughput risk burning out the people meant to be supervising it.
Read →imdanielkendall.com
The Great Software Regress: How Move Fast and Break Things Broke Our Lives
Prompted by a MINI firmware update that broke Android Auto, the author argues the tech industry's 'move fast and break things' culture has quietly degraded the reliability of software people now depend on for basic daily functions — cars, phones, home devices — not just web apps where a broken deploy is a minor inconvenience. The piece traces this to agile sprint culture's bias toward shipping now and fixing later, and to security-compliance regimes (like blanket 14-day patching mandates) that incentivize frequent, rushed releases over stability, contrasting this with counterexamples like the 0patch project, which shows security can be maintained without constant disruptive updates. It closes by pointing to Windows 11's growing complexity as a symptom of an industry that keeps adding surface area rather than protecting the focused, dependable design earlier software generations aimed for.
Read →PrivacyPros
GrapheneOS recommended for domestic abuse victims
PrivacyPros lays out why GrapheneOS — a privacy- and security-hardened Android fork — is increasingly recommended to domestic abuse survivors in Australia as a way to neutralize the surveillance tools abusers commonly exploit on stock Android and iOS devices. The hardened OS strips out Google's default tracking and telemetry, and adds features specifically useful under coercive control: per-app sandboxed Google Play isolation and hidden user profiles so a second, private profile can exist invisibly alongside a decoy one; granular runtime permissions that block silent location or microphone access; verified boot with tamper detection to catch spyware installation; and a duress PIN that wipes or hides sensitive data instantly if a survivor is forced to unlock their phone under threat. The piece frames this as a reminder that the privacy features enthusiasts value as a hobbyist preference are, for some users, a basic safety requirement.
Read →Turso
We're building Postgres in Rust. Using the LLVM of databases
Turso — the company behind the Rust rewrite of SQLite (Limbo) — is applying the same idea to Postgres: rather than reimplementing the database as one monolithic binary, they're building it around a shared bytecode virtual machine (a VDBE, in SQLite terminology) that different SQL frontends compile down to, an architecture they describe as making it 'the LLVM of databases.' That abstraction is meant to let Postgres-compatible and other SQL dialects share the same core execution engine, while enabling an async-first design with built-in concurrent writes and auto-updating materialized views, and the ability to run the same core across servers, phones, and browsers. It's an ambitious bet that the historical case for one-database-per-runtime is outdated, and that compiling to a common intermediate representation — the way LLVM decoupled language frontends from CPU backends — is the right abstraction for databases too.
Read →JSTOR Daily
The Debate Over Pictures in Science
Drawing on historian Anne Secord's research, JSTOR Daily revisits a 19th-century controversy in British botany over whether illustrations helped or hurt the growth of the scientific community. When Joseph Hooker returned from Antarctica with plant specimens and illustrations in 1843, he was dismayed to find his publisher cared only about the pictures — a tension that ran through the field: as the 1815 Apothecaries' Act forced British doctors to study botany and demand for public lectures surged, some botanists like William Hooker found illustrations essential to holding an audience's attention, while others, like Peter Rylands, worried that pictures attracted casual dabblers seeking a different, lesser kind of pleasure than the discipline of written description could provide. Astronomer John Herschel captured the anxiety by warning against catering to 'the passions' at the expense of 'sound knowledge,' while advocates like Edwin Lees compared rejecting illustrations to refusing a candle at dusk. The resolution, Secord argues, wasn't a clean victory for either side but a norm that images were legitimate so long as they stayed grounded in expertise rather than becoming a 'cloak' for entertainment — an early version of a tension between accessibility and rigor that runs through every subsequent debate over how to popularize science.
Read →