Telegram RegisterThe public register of Telegram
Telegram profile photo for 博客园 - 开发者的网上家园

Channel

博客园 - 开发者的网上家园

@cnblogs_com

On this record: Growth · Engagement · Posts · Citations · Cite this entry

124subscribers

+7 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-1002319262268
TypeChannel
Username@cnblogs_com
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live5 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/cnblogs_com

Growth

117124120.56 August 2026 — 117 subscribers7 August 2026 — 118 subscribers9 August 2026 — 118 subscribers21 August 2026 — 122 subscribers29 August 2026 — 123 subscribers5 September 2026 — 124 subscribers6 August 20265 September 2026
6 measurements spanning 30 days, net +7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 116–125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 12:20124+1
29 Aug 2026, 01:35123+1
21 Aug 2026, 14:38122+4
9 Aug 2026, 04:45118no change
7 Aug 2026, 09:32118+1
6 Aug 2026, 19:51117first reading

Engagement

20 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Aug 2026, 04:28 UTC1 viewsread 9 August 2026
Photo

来自速搜推荐 @SSOU 📢环球异事|未解之谜|奇闻... 📢纪实说|圆桌派|马末都 📢皇冠招商 皇冠娱乐 PA... 📢bgc越南 bgc小菲 ... 📢迷迷糊糊 📢四大赌场🇵🇭本地妹妹 📢利博私网🅰️万利私网�... 📢激情四射免费在线匹配裸聊... 📢皇冠私网🅰️亚星私网�... 📢万利网址 万利注册 PA... 📢金沙飞投真人视讯百家乐 📢缅甸赌场线上网投部-东南... 📢TK商城盘-外汇秒合约招... 📢😍😍Coser图集鉴... 📢PA注册 PA网址 PA... 👉流量互推规则介绍💥 以下是广告推荐 📢🔰开元官方🔥代理70%|电子棋牌|AG百家乐 📢 TeleTop 中文索引 📢 飞驰号铺 [主营:飞机号 开会员 代充星星] 📢182体育 2026世界杯指定投注平台、 免实名、不限ip、u存u提无上限 📢 全网最全面、最便宜的自助引流服务 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHe

9 Aug 2026, 04:13 UTC1 viewsread 9 August 2026
Photo

AI 写代码总跑偏?用 spec-superflow 把规划引擎和执行纪律焊成一条流水线 你肯定遇到过这种场面。你对 AI 说一句「帮我给项目加个权限控制」,它二话不说唰唰改了四十多个文件。改到一半你才发现,它默认做的是 ABAC,而你要的根本是 RBAC。更酸爽的是,proposal 写了、design 画了,合并之后你才意识到行为根本不对,因为实现阶段没人盯着测试,也没人卡 revi cnblogs​.com • Aug 9, 2026

9 Aug 2026, 04:05 UTC1 viewsread 9 August 2026
Photo

❤️欢迎来到 TGRSS —— Telegram 上最智能、最全能的 RSS 自动内容矩阵! 在这里,你不需要手动刷新网页、不需要下载 App、不需要错过任何热点。 TGRSS 通过实时 RSS 订阅 + 自动化推送,为你打造了一个“内容永不缺席”的私人信息流: 实时全球新闻:科技、财经、国际大事,一秒不落 成人专区(18+):精选故事、幽默、亲密建议与行业动态(纯链接推送,安全隐私优先) [❤️‍🔥赞助商]TGFOX矩阵机器人 👩🏻‍⚕️广告投放: @TGRSS123 🚀支持200+频道同时投放,所有频道每天推送一次

9 Aug 2026, 03:22 UTC1 viewsread 9 August 2026
Photo

RankMixer 中 Semantic Split 与 Auto Split 的 Token 构造方式分析 RankMixer 中 Semantic Split 与 Auto Split 的 Token 构造方式分析 在 RankMixer 中,原始推荐特征需要先被组织成若干 Token,再进入后续的 Token Mixing 和 Per-token FFN。不同 Token 构造方式,本质上决定了模型在 cnblogs​.com • Aug 9, 2026

8 Aug 2026, 15:30 UTC3 viewsread 9 August 2026

windows安装codex desktop和cc-switch,接deepseek v4 flash 背景 最近在公司用codex有一阵了,不过怎么把这个东西玩得6,还在探索中。家里也有台windows,就准备也把codex装上,结果发现还有些之前没遇到的幺蛾子,就在这里完整记录一遍。 本文主要就是安装codex windows desktop版本,接deekseek v4 flash(最近这个de cnblogs​.com • Aug 8, 2026

8 Aug 2026, 14:37 UTC3 viewsread 9 August 2026
Photo

面向 .NET 开发者的 RocketMQ 入门指南(二):RocketMQ 如何让业务消息更可靠 目录可靠不等于只处理一次一条消息经过三次责任交接Producer 将消息交给 BrokerBroker 接管消息并负责存储Consumer 处理完成后再确认RocketMQ 内建的重试与死信状态消息进入 DLQ 后如何兜底gRPC/POP PushConsumer 如何完成一次重试服务端内部:不可见 cnblogs​.com • Aug 8, 2026

8 Aug 2026, 13:28 UTC3 viewsread 9 August 2026
Photo

别再把整页 HTML 塞给 Agent:Firecrawl 把网站变成可用上下文 现在给 AI Agent 接大模型已经不难,真正麻烦的往往是另一件事:怎样让它稳定地读懂网页。 你当然可以直接请求一个 URL,但拿回来的可能是几百 KB 的 HTML、导航栏、Cookie 弹窗、脚本、广告、延迟加载内容,以及一堆对回答问题没有帮助的噪声。 遇到 JavaScript 渲染、分页、 cnblogs​.com • Aug 8, 2026

8 Aug 2026, 12:53 UTC3 viewsread 9 August 2026
Photo

【Agent Harness】Gliding Horse 最新升级:把“智能闭环”真正跑通的一次深度优化 Gliding Horse 最新升级:把“智能闭环”真正跑通的一次深度优化 摘要:Gliding Horse 本次升级聚焦“智能闭环”的落地,重点打通记忆系统的一致性写入与预取链路、修复 SA 编排层的“假成功”问题、为安全门禁补充合规工具白名单,并新增日志实时镜像以消除长任务“无输出假死”。升级后 cnblogs​.com • Aug 8, 2026

8 Aug 2026, 12:01 UTC3 viewsread 9 August 2026

MySQL 磁盘 80% 告警,碎片 52G,我差点 TRUNCATE 掉正在写入的业务表 大家好,我是老张。 连着写了三天博客安全系列,今天换个话题——生产踩坑。 上周写个人博客后台写嗨了,差点在生产环境捅个大篓子。 ⚠️ 声明:本文基于真实生产环境排查案例编写,已对 IP 地址、实例名、库名/表名、密码等敏感信息做脱敏处理,命令可直接复制执行。 "磁盘 80% 告警,碎片 5 cnblogs​.com

8 Aug 2026, 11:53 UTC3 viewsread 9 August 2026

从 PHP 到 AI + Golang,程序员自救转型手记(五十九):前后端自定义后台入口实现 这是一个系列 Blog,作者将以一个 PHP 全栈工程师的身份,利用 AI 工具(claude code、codex、deepseek、豆包等):从零开始学习 golang 语言,并最终完成 ai-go-admin(github | gitee)开源项目的制作(欢迎 star~),全程记录分享。 在 cnblogs​.com • Aug 8, 2026

8 Aug 2026, 11:13 UTC3 viewsread 9 August 2026

【adviskv】#04:PUT 链路 在 Storage 内部的 Replica 的设计与实现(上) 日期: 2026.8.8 写在开头的开头 AdvisKV 是我用 C++17 从零写的一个分布式 KV 存储系统原型,包含 Catalog、Topo、Storage、SDK 四个主要模块,覆盖建库建表、路由查询、KV 读写、副本数扩缩容、坏副本替换、Raft、WAL/snapshot 恢复,跑了 g cnblogs​.com • Aug 8, 2026

8 Aug 2026, 09:25 UTC3 viewsread 9 August 2026

Hot-Plug 实战:运行期管理 Solon 插件 Solon 框架的 solon-hotplug 模块为业务插件提供了热插拔能力,允许在不重启主程序的情况下动态加载、启动、停止和卸载插件。该功能适用于需要持续运行的应用,如网关或多模块单体系统,可避免服务中断。 cnblogs​.com • Aug 8, 2026

Showing the 12 most recent of 20 posts we hold for @cnblogs_com. 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.

Mentions

Named by 24 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 22 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“博客园 - 开发者的网上家园” (@cnblogs_com), 124 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/cnblogs_com.

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.