🍒 Cherry Studio 更新 - v2.0.0 🆕 核心更新: - 全新界面与交互设计,支持多窗口和分屏布局,提升多任务处理效率。 - Agent 核心运行时内置,减少依赖安装;支持 OpenAI 和 Anthropic 端点,可复用 Claude 和 Codex 订阅。 - 工具升级:知识库读写、Code Mate 代码工具(一键配置 Claude Code/Codex)、图像生成参数动态展示。 - 性能优化:数据基础升级,长对话滚动更流畅,大文件夹导入不阻塞界面。 🔑 关键词: #cherrystudio, 大版本更新,AI工作区, 多窗口, Agent, 知识库, 性能优化 🔗 查看详情

Channel
开源早报
@zaobaoky
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
708subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002558886633 |
|---|---|
| Type | Channel |
| Username | @zaobaoky |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/zaobaoky |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:15 | 708 | -2 |
| 6 Aug 2026, 16:36 | 710 | no change |
| 6 Aug 2026, 15:05 | 710 | first reading |
Engagement
20 posts held, back to 12 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 46.8%
- avg views ÷ 708 subscribers
- Avg views / post
- 331
- 7 posts measured
- Reaction rate
- 0.257%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (12 June 2026 – 6 August 2026) |
| Views total | 2,318 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 16:36 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
14 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 7 | 50.0% | |
| ❤ | 5 | 35.7% | |
| 👏 | 2 | 14.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 June 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
📢 FFmpeg 更新 — 9.0 版本代号为 "Lei",纪念已故中国开发者@雷霄骅 🆕 核心更新: • 新增 Animated WebP 解码器与解封装器,支持动态 WebP 直接解码 • GPU 滤镜扩展:v360_vulkan(全景投影)、transpose_cuda(旋转)、AMF 帧率转换器与 HDR 色彩转换增强 • 硬件加速新增 ProRes RAW VideoToolbox 与 APV Vulkan hwaccel • ONNX Runtime DNN 后端支持 GPU 执行提供程序;新增 Dolby Vision 多层 HEVC 拆分 bitstream filter • HE-AAC 960 采样解码(DAB+ 数字广播);SMPTE 2094-50 HDR 元数据透传 • 移除独立 CELT 解码与 ogg/celt 解析支持(Opus 内嵌 CELT 不受影响) • 移除已废弃的 NVENC 选项…
📢 Next.js 更新 - 16.3 🆕 核心更新: • Turbopack 开发服务器内存占用降低最高 90%(21.5 GB → 2 GB),磁盘缓存扩展至 next build,重复构建最高提速 5.5× • SSR 渲染层改用原生 Node.js streams,负载下请求吞吐量提升 22%;支持 TypeScript 7 原生类型检查 • 新增 Instant Navigations 套件(opt-in):Partial Prefetching、Navigation Inspector、Instant Insights DevTool、Playwright instant() 测试助手,为 Server Components 应用带来 SPA 级导航响应 • ISR 增强:未预渲染页面首次访问即返回 loading shell,后台自动生成完整页面并缓存;新增 catchError 自定义错误边界支持 Serve…
📢 Qwen 开源了 Qwen 3.8-Max — "A New Bar for Coding and Cowork" 这是 Qwen 系列中首个被开源的 Max 级模型 🆕 核心更新: • 2.4T 总参数 / 95B 激活参数(MoE),基于 Qwen 3.5 架构,为 Qwen 系列迄今最强模型;开源权重将于下周发布 • Coding Agent 能力全面提升:10+ 天自主编程构建自演化 harness(265 commits / 127 PRs),复现并超越论文方法(AIME24 +2.7),在 526 支人类队伍竞赛中击败 87% • 长周期自主任务:自主完成芯片 RTL 设计全流程(500 轮迭代,面积缩减 81%);365 天电商模拟中以 ¥416,252 总余额领先第二名 38% • 多模态 Agent 引入视觉反馈闭环,支持 200+ 页文档 / 100+ 小时视频理解与生产,发布 Qwen-MM-Pl…
👍2
🦈 DeepSeek-V4-Flash API 更新 - 0731 正式版 🆕 核心更新: • V4-Flash 正式版 API 上线公测,模型名 deepseek-v4-flash,调用方式不变 • Agent 能力大幅增强,Code Agent 基准测试全面超越 V4-Pro-Preview • 原生支持 Responses API 格式,针对性适配 Codex • 模型结构与 V4-Flash-Preview 一致,仅重新后训练 • 本次仅升级 V4-Flash API,V4-Pro API 及 APP/WEB 端模型未变更 🔑 关键词: #deepseek Code Agent,Responses API,Codex 🔗 查看详情
⛓ Model Context Protocol 更新 - Specification 07-28 🆕 核心更新: • 架构从双向有状态转为无状态请求/响应模型,支持 Serverless 和边缘部署 • 新增标准化扩展框架:MCP Apps(交互式 UI)和 MCP Tasks(长时任务),均可独立于核心协议演进 • 企业认证增强:原生对齐 OAuth 2.0 / OIDC,直接集成 Entra、Okta 等企业身份系统 🔑 关键词: #MCP Stateless,Extensions,OAuth2 🔗 查看详情
🔀📊 llm-trending 排行榜月报 本次分析的数据周期为月度(Month),对比区间:06.07 → 07.07 🆕 核心更新: • DeepSeek V4 Flash 稳居榜首,用量 12.1T → 20.8T(+72%) • MiMo-V2.5 从 #9 跃升至 #2(3.53T → 17.4T),增幅近 5 倍 • 新入榜: MiniMax M3 #3(17.1T),Claude Opus 4.8 #8(7.43T),GLM 5.2 #10(6.51T) • 跌出榜:DeepSeek V3.2、Gemini 3 Flash Preview、Kimi K2.6 🔑 关键词: #llmtrending@zaobaoky 🔗 查看详情
👏1
🚀 Kimi 发布了 Kimi K3 🆕 核心更新: 🔹 MoE 架构,2.8T 总参数,896 专家取 top-16 激活,原生支持 1M 上下文 🔹 原生多模态(文本 + 视觉 + 代码),覆盖长链路编程、GPU kernel 优化、3D 推理、视频编辑等场景 🔹 引入 Kimi Delta Attention(KDA)+ Attention Residuals,训练效率较 K2 提升约 2.5 倍 🔹 从 SFT 阶段即采用量化感知训练(MXFP4 权重 / MXFP8 激活),降低部署门槛 🔹 评测表现:DeepSWE 67.5、Terminal Bench 2.1 88.3;开源模型中领先,整体接近 Claude Fable 5 / GPT 5.6 Sol 🔹 模型权重将于 2026-07-27 开放下载 🔑 关键词: #kimi #moe agentic,开源 🔗 查看详情 🏄♂️ 立即体验
❤1👍1
📢 ripgrep 更新 - 15.2.0 🆕 核心更新: • 性能优化:大型代码库目录遍历性能显著提升 • 平台支持:新增 aarch64-unknown-linux-musl 预编译二进制 • 功能加强:支持 GIT_CONFIG_GLOBAL / GIT_CONFIG_SYSTEM 环境变量 • 问题修复:修复多目录搜索时 gitignore 匹配不正确的问题 🔑 关键词: #ripgrep 遍历性能,aarch64-musl,gitignore 🔗 查看详情
🐑 Ollama 更新 - v0.32.0 🆕 核心更新: - 新增交互式代理体验:运行 ollama 命令将启动一个代理,协助编码和任务委派。 - 将 Codex App 集成重命名为 ChatGPT:使用 ollama launch chatgpt`(`--restore 可恢复至常规 ChatGPT 配置)。 - 简化集成选择:`ollama launch` 菜单仅显示最流行的集成,其他集成可通过 ollama launch 访问。 - 启动较旧代理模型时发出警告:CodeLlama、Qwen2.5(-coder)、Llama 3.x、Mistral、StarCoder 及基础 DeepSeek-R1 标签会提示弃用警告。 🔑 关键词: #ollama 交互式代理, ChatGPT 集成, 简化菜单, 模型弃用警告 🔗 查看详情
🎲 腾讯混元 开源了 Hy3 🆕 核心更新: • MoE 架构,总参数 295B / 激活参数 21B(192 专家取 top-8),支持 256K 上下文 • 推理与代码能力突出:GPQA Diamond 90.4,SWE-Bench Verified 78%,对标DeepSeek V4 Pro • 幻觉率从 12.5% 降至 5.4%,多轮对话问题率从 17.4% 降至 7.9% • 原生支持 Tool Calling(vLLM/SGLang 均提供解析器),支持 MTP 推测解码加速 • 提供 BF16 与 FP8 量化两个版本,Apache 2.0 开源 🔑 关键词: #hy #腾讯混元 MoE-295B,SWE-Bench,Tool-Calling 🤗 HuggingFace | 🎲 GitHub | 🏄♂️ 立即体验
🎲 Rust 更新 - 1.97.0 🆕 核心更新: • 新增 dead_code_pub_in_binary lint,可检测二进制 crate 中未使用的 pub 项 • 整数类型新增 isolate_highest_one/isolate_lowest_one/bit_width 等位操作方法(含 NonZero 变体) • Cargo 支持自定义 lockfile 路径(resolver.lockfile-path)及 -m 作为 --manifest-path 简写 • cargo clean 新增目标目录校验,防止误删 • 符号修饰默认切换至 v0 方案,可能影响调试器/性能分析工具 • pin! 宏移除了可能导致不安全行为的 deref 强制转换 • std::char 模块常量与函数标记为弃用 🔑 关键词: #rust bit操作,Cargo,symbol-mangling-v0 🔗 查看详情
Showing the 12 most recent of 20 posts we hold for @zaobaoky. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 808,155 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“开源早报” (@zaobaoky), 708 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zaobaoky.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.