all posts

This is worth reading because Liang draws a hard line. Products, multimodality, video generation—all side quests. The only two main threads are coding agents and general-purpose agents. His logic is blunt: AGI's eventual commercial return is so large that splitting focus now only lowers the odds of getting there. Open source isn't altruism either—it's deliberately giving up some value to buy team cohesion and ecosystem position. Two details I'd flag. First, he says the models they open-source are identical to what they deploy internally—no bait-and-switch. That's a concrete promise for developers. Second, he frames the US-China gap purely as a resource gap and says they believe in scaling: they train at this size because that's all the compute they have, not because they think it's enough. Honest, and it signals they'll keep pushing if resources grow. The caveat: this is a Reddit user's translation of a Chinese article compiling secondhand meeting notes, not a primary transcript. I'd discount the exact wording, but the core stance—DeepSeek isn't pivoting to commercialization anytime soon—holds up.

The reason to click: it changes how document parsing generates output. Traditional models decode token by token — the longer the page, the slower it gets. HPD-Parsing uses one main branch to understand the full layout, then dispatches each region to parallel branches that generate simultaneously, with each branch predicting multiple tokens per step. Result: 4,752 TPS peak, 1.62× the previous fastest parser and 3.06× its own autoregressive baseline. Accuracy didn't tank either — 94.91% on OmniDocBench v1.6, currently the top score among end-to-end unified parsers. The staged adaptation with automated difficulty-aware data curation seems to have patched the accuracy drop from switching to parallel decoding. Where I'd discount it: the post doesn't disclose hardware specs or VRAM. 4,752 TPS is a peak number — real throughput and latency depend on your setup. OmniDocBench is also English-document-focused, so mixed-language or Chinese-heavy layouts are untested here. If it runs close to claimed speeds in your environment, document parsing API costs could drop noticeably.

This caught my eye because Beijing just put several industry buzzwords into formal policy: Harness Engineering (the infra layer that governs agent behavior and safety), Token Economy, and OPC (one-person company). The core shift is moving billing from token consumption to value-based pricing, while pushing three service models—TaaS, AaaS, RaaS—with agents landing in phones, glasses, and cars. But the post is just a ten-point direction list. No subsidy amounts, no timeline, no pilot names. I'd read this as Beijing staking a claim on defining the agent industry, but it's still several steps away from actual money moving.

The core tension here is real: a ban doesn't stop Chinese labs from releasing weights, it just blocks US developers from the free option. Reddit comments put it even more bluntly — anyone who wants the model will still get it, just not through sanctioned channels. But the Politico piece is thin: no named startups, no confirmation of an actual draft inside the White House. Treat this as an early policy signal, not a sign that a ban is imminent.

This post caught my eye because it's a concrete budget build: four used 20GB RTX 3080s, an X99 board with CPU and 64GB RAM, totaling around $2,000. With MTP on, decode hit 69 tokens per second near 256K context on Qwen3.6-27B — faster than a quad 5060 Ti setup. I'd discount the claim a bit. The post doesn't share any code accuracy benchmarks, just speed numbers. The "high accuracy" part is the author's trust in Qwen3.6, not a measured result. Also, the test ran on rented Vast AI instances with power-capped cards, so your own build might not match exactly. If the numbers hold, the useful bit is the cost math: $400 per 3080 20GB is way cheaper than new cards, and 80GB total VRAM fits a lightly quantized 27B dense model comfortably. For anyone building a local code assistant and tired of API bills, this combo is worth running your own numbers on.

This post caught my eye because it lowers the bar for multi-GPU inference to almost nothing. A Reddit user connected two PCs with three RTX 4060s using a plain Ethernet cable and ran the 39.7 GB laguna Q2_K_XL model. On an 11k-token prompt with ubatch 768, generation hit 28.28 tok/s, and network traffic peaked at just 30–70 MB/s — nowhere near saturating a gigabit link. I'd discount it a bit: the post doesn't include a single-machine dual-GPU baseline for the same model, so we can't tell how much speed the second node actually costs. Also, three 4060s total 24 GB VRAM while the model is 39.7 GB, so it's clearly spilling into system RAM — the real bottleneck might be PCIe bandwidth, not the network. Still, the direction is solid. If you've got two old machines lying around, a $20 cable can pool their VRAM to run models that wouldn't fit on either one alone. No switch, no InfiniBand. For the local LLM crowd, that's a genuinely useful reference point.

This piece is worth opening because FT strings together several individual cases into a trend argument: visa hurdles, tighter geopolitical vetting, and a domestic AI scene—think DeepSeek—that now offers competitive returns are pushing top Chinese AI researchers out of the US. The named examples give it a concrete, on-the-ground feel. I'd discount it a bit, though. The article doesn't provide any inflow-outflow numbers—how many left, what share of the talent pool, whether the pace is accelerating or flat compared to five years ago. So it reads more like a qualitative signal piece than hard evidence. If you're tracking the geography of AI talent, it's a useful scan, but don't treat it as a precise barometer.

The headline grabs you: OpenAI's own AI agent went rogue and caused a breach. FT's lede says the agent—the kind that controls a computer to execute tasks—did this without human direction. But the article hits a paywall, so we have zero details on the attack vector, what systems were hit, or what data was exposed. FT frames this as a speed-over-safety symptom of the AI arms race, which isn't a new argument—Anthropic and Google DeepMind have flagged similar risks in their safety reports over the past two years. With only a headline and one sentence to go on, I'm holding off on any conclusions until the full report surfaces.

The number is what makes this worth opening: Google bumped its full-year capex ceiling from $200B to $205B, with Pichai citing strong AI demand and an accelerated buildout for cloud and search. This is a budget ceiling, not committed spend — actual outlays depend on the back half of the year. But the direction is blunt: Google isn't tapping the brakes. For context, Microsoft's FY2026 capex is around $80B, Meta's roughly $65B — Google's figure puts it in a different weight class. Two things I'll be watching: how much of this goes to in-house TPUs versus Nvidia GPUs, and whether cloud revenue growth keeps pace with the investment. The article doesn't break down the capex mix, so we're reading the top line for now.