World Wire

Tencent’s WeChat Vision team has released WeVisOne-VL , an open vision language model in 2B and 4B sizes. The WeVisOne-VL vision language model handles detection, referring, counting, pointing, OCR, segmentation and alpha matting in one model. Pixel outputs come from a 9.6M-parameter decoder, so no separate SAM is needed. It also answers “None” when a queried object is absent. For developers, that can replace a detector, an OCR engine and a segmenter with one model. TL;DR Size: 2B ( 2.44B params ) and 4B ( 4.83B params ) on Hugging Face, and a 9.6M-parameter pixel decoder. Trained with up to 8,192 tokens of context; deployment context length is not disclosed. Runs on: A single GPU through Transformers or vLLM in BF16. The package also lists NPU and CPU devices. VRAM needs are not disclosed. A community GGUF ran object-level tasks on a 6 GB RTX 2060. Performance: Beats the same-scale VLM baselines in Tencent’s tables on most of 30+ benchmarks...

Anthropic’s Frontier Red Team has released FlashProve , an open-source research prototype for provable inference . FlashProve is a zkSNARK system from Anthropic that proves a reply came from a committed model. The proof reveals nothing about the model weights. On Llama 4 Maverick , a 400B mixture-of-experts model, it proves about 110 tokens/second on 1 H100. For developers, this targets a real gap: today you cannot check which model actually answered your API call. TL;DR Size: Proves a 400B MoE model (~17B active per token); context capped at 1,024 tokens per request. Runs on: Prover needs 1 H100 80 GB, 24 CPU cores and ~290 GB host RAM. Verifier runs on a CPU, no GPU. Performance: Orders of magnitude faster than prior open-source zkML systems on the same 400B model. Best: 110 tokens/second proving on 1 H100, with 18.78 MB proofs checked in 17 seconds. Worst: Proving costs ~70 to 95x the GPU time of plain vLLM inference. What problem does provab...

Soniox has released Soniox STT v6 , the latest generation of its speech-to-text API. Soniox STT v6 is a speech-to-text model that reads what a voice agent says while hearing the caller. It uses that text to recognize short replies and to drop the agent’s own voice. The release ships as stt-rt-v6 for streaming and stt-async-v6 for files , across 60+ languages. TL;DR Size: Soniox STT v6 is a proprietary hosted model, no parameter count published. Runs on: Soniox cloud API only (WebSocket streaming and async REST). No self-hosted or on-device option disclosed. Performance: Soniox calls it “significantly” more accurate than v5, but publishes no v6 numbers yet. Best: Price. $0.12/hour streaming and $0.10/hour async, with diarization and language ID bundled. Worst: Zero independent v6 results. Its v5 predecessor scored 1.34% semantic WER on Pipecat, behind v4’s 1.25%. What problem does Soniox STT v6 solve? In a cascaded voice a...

OpenAI has introduced Pando , a new Git backend that now serves all development in its monorepo. The OpenAI Pando Git backend keeps the standard Git client and protocol. Engineers and Codex agents still run git push and git fetch as before. Only the server changed. OpenAI team reports median push latency fell nearly 80%. Pando now delivers nearly a petabyte of Git data per day. TL;DR Scale: Nearly 1 PB of Git data per day; peak above 57 TB in 1 hour. Runs on: Commodity hardware; standard cloud VMs saturate 10 Gbps links on clone and fetch. Performance: Thousands of concurrent pushers without degradation, per OpenAI’s own testing. Best: Median push latency down nearly 80% (about 5x). Worst: Not open source; repeat branch pushes resend non-trunk history (p99 pack under 3 MiB). What is OpenAI Pando? Pando is a Git-compatible server backend from OpenAI that scales concurrent pushes and fetches for a monorepo. It was written in Rust and reache...