🚀 Open-source upgrade unlocked. Tencent Hy-MT2 is now under Apache License 2.0 — maximum freedom for research, commercial use, fine-tuning, and derivatives. No strings attached.😎😎😎 Proud to push model weights back to the community. Our two variants are currently sitting at #1# and #4# on the Hugging Face trending leaderboard. Clone, fork, break things, ship feedback. The iteration loop is live.🔥 Let’s keep building the frontier together. #Tencent# #Hy# #HyMT2# #Apache2# #HuggingFace# #OpenSourceA#

📢 Official Announcement: Qwen Partners with Fireworks AI to Accelerate Access to Qwen Family Models We are pleased to announce a strategic partnership between Qwen and Fireworks AI to deliver optimized, production-ready deployment of Qwen's closed weights models via the Fireworks Platform. @FireworksAI_HQ This collaboration empowers developers and enterprises to: ✅ Deploy Qwen models with lower latency and reduced fine tuning and inference costs ✅ Leverage enterprise-grade reliability, security, and scalability ✅ Integrate seamlessly into modern AI workflows 🔹 Get started with Qwen on Fireworks: #Qwen# #FireworksAI# #OpenSourceAI# #LLM# #AIInfrastructure# #ResponsibleAI# #DeveloperCommunity#

We’re excited to welcome Mooncake to the PyTorch Ecosystem! Mooncake is designed to solve the “memory wall” in LLM serving. By integrating Mooncake’s high performance KVCache transfer and storage capabilities with PyTorch native inference engines like SGLang, vLLM, and TensorRT-LLM, it unlocks new levels of throughput and scalability for large language model deployments. Mooncake enables prefill decode disaggregation, global KVCache reuse, elastic expert parallelism, and serves as a fault tolerant PyTorch distributed backend. 🔗 #PyTorch# #OpenSourceAI# #LLM# #AIInfrastructure#

🧩 Kimi K3’s MoE and Attention Are Built Around Trade-offs, Not Tricks Kimi K3’s open release has drawn attention to its scale. But its architecture tells a more useful story: the hardest part of scaling is keeping quality, efficiency, and stability in balance. Zhihu contributor 苏剑林 @Jianlin_S explains the design logic behind two core components: Stable LatentMoE and K3’s hybrid attention. At a high level: K3 = KDA + MLA + Stable LatentMoE + AttnRes 1️⃣ Stable LatentMoE: more experts at similar cost LatentMoE compresses each token into a smaller latent space before routing it to experts, then projects the result back to the full hidden dimension. This reduces expert computation and communication. The saved budget can support more, narrower experts without greatly increasing training or inference cost. But the longer projection chain also magnifies numerical instability. K3 introduces three fixes. 🔹 SiTU-GLU softly caps extreme activations in both branches of the expert network. Compared with hard clipping, soft capping preserves smoother optimization. 🔹 RMSNorm is placed before the final up-projection. It stabilizes training and helps balance routed experts against shared experts. 🔹 Quantile Balancing replaces the previous load-balancing update, which became unreliable as the expert pool grew. It approximates global routing quantiles with histograms, allowing efficient aggregation across machines. The broader lesson is clear: scaling MoE is not just about adding experts. Routing, activation ranges, normalization, and distributed communication must scale with them. 2️⃣ Why K3 still uses MLA Some newer models have moved away from MLA, partly because speculative decoding changes the inference trade-off. MLA keeps KV Cache small and remains highly competitive under fixed training and memory budgets. But its decoding path is relatively compute-heavy, leaving less room for Multi-Token Prediction to trade extra computation for speed. Other attention designs simply move the bottleneck: 🔹 Smaller designs may reduce computation but lose quality or require a larger KV Cache. 🔹 Larger designs can recover quality, but increase training and prefill costs. An ideal replacement would preserve quality, reduce KV Cache, lower decoding compute, and cost no more during training or prefill. No simple design currently satisfies all four conditions. K3 therefore keeps MLA and combines it with KDA. The linear-attention layers handle most long-context processing efficiently, while MLA preserves full-attention capacity where it matters. 3️⃣ “Abandoning MLA” is not so simple Architectures that appear to replace MLA may still retain its core intuition. For example, a wide MQA design with shared K and V resembles MLA’s decoding form. Sparsity and compression can then reduce its compute and cache costs. This can work, but it introduces more infrastructure complexity. So the current debate is less about whether MLA is obsolete. It is about which combination of full, linear, sparse, and compressed attention offers the best system-level trade-off. 4️⃣ Why K3 can remove RoPE K3 removes RoPE from its MLA layers. That would hurt a pure-MLA model. But K3 is a hybrid of KDA and MLA. KDA’s DeltaNet-style updates already introduce an implicit positional transformation. In this sense, KDA provides something similar to a generalized form of RoPE for the full network. Adding explicit RoPE back produced little difference, so K3 followed the simpler design. K3 is not truly position-free. Its positional structure is partly carried by KDA instead of an explicit embedding. ⚙ The real architecture lesson None of these choices is especially flashy in isolation. Stable LatentMoE controls the numerical and routing problems created by more experts. KDA and MLA divide long-context work according to their strengths. NoPE removes a redundant component only after the hybrid architecture makes it unnecessary. K3’s main design principle is therefore not novelty for its own sake. Every architectural change must justify itself across quality, efficiency, and stability. 🔗 Full reading: 📖Blog post: #KimiK3# #MoE# #Attention# #LLM# #AIInfra# #OpenSourceAI#

#OpenSource# doesn't scale by accident. Share how your organization approaches governance, contribution strategies, security, compliance, community engagement, & more at OSPOlogy + #OSPOSummit# China. 📅 September 7, Shanghai 🎤 Submit to speak by July 12:

More opensource goodness. We have just released a CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities in your code. Scan repositories, review changes, track findings over time, and run security checks in CI.

🚀 Your next big #OpenSource# conversation starts in Shanghai. Join #KubeCon# + #CloudNativeCon# + #OpenInfraSummit# + #PyTorchCon# China, September 7-9, for three days of technical sessions, community collaboration, & the ideas shaping the #AI# era. ⏰ Register by July 28 to save ¥710 RMB: