Telegram RegisterThe public register of Telegram

Channel

密语 CipherTalk

@CipherTalk

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,577subscribers

+55 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003320887497
TypeChannel
Username@CipherTalk
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/CipherTalk

Growth

1,5221,5771,549.57 August 2026 — 1,522 subscribers7 August 2026 — 1,522 subscribers8 August 2026 — 1,527 subscribers11 August 2026 — 1,577 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +55. 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 1,514–1,585 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 10:221,577+50
8 Aug 2026, 20:171,527+5
7 Aug 2026, 21:341,522no change
7 Aug 2026, 21:161,522first reading

Engagement

20 posts held, back to 23 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
50.5%
avg views ÷ 1,577 subscribers
Avg views / post
797
20 posts measured
Reaction rate
0.233%
reactions ÷ views · ER floor
Posts in window
20
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 10 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (23 July 20267 August 2026)
Views total15,937
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 21:34 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.

What this channel posts

Video runtime
39s
Average length
39s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

23 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 39.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍939.1%
😱730.4%
626.1%
👀14.35%

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 10 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 23reactions 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 23 July 2026 to 7 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

7 Aug 2026, 16:51 UTC60 viewsread 7 August 2026

做一个手机软件,P2P连接,专门对接密语的Agent,大家感觉有需要吗

7 Aug 2026, 10:31 UTC150 viewsread 7 August 2026
Photo

CipherTalk v2026.807.1 静默修补,亮色归位 更新内容 修复 › 修复浅色主题锁屏按钮文字不可见的问题(#332) 调整 › 调整了发布流水线与版本校验逻辑,使版本分发更顺畅,也能更早拦截异常构建。 › 维护了强制更新策略,明确最低支持版本并封禁已知问题版本。 2 commits · 2026-08-07

Signed CipherTalk

7 Aug 2026, 10:02 UTC144 viewsread 7 August 2026
Photo

CipherTalk v2026.807.0 云端的诗 更新内容 新增 › 新增 StepFun TTS 提供商支持,语音生成有了新的选择 › 图像生成新增尺寸重试机制,失败时自动换档再来一次,不再让你对着空白干等 修复 › 修复公众号消息变更事件遗漏 biz_message 识别的问题,消息不再「看不见」(#324) › 设置页 z-index 调整,弹窗不再躲到别的元素后面 › 升级 sherpa-onnx-node 至 1.13.4,修复 TopkIndex 缓冲区溢出风险(#329) › 密码验证改用常数时间比较,从时序上给暴力破解添一道墙(#328) 调整 › 发布流程与构建配置做了梳理,版本管道更稳健,往后交付会更顺 7 commits · 2026-08-07

Signed CipherTalk

6 Aug 2026, 10:09 UTC230 viewsread 7 August 2026
Photo

CipherTalk v2026.806.0 让对话在记忆里安家 更新内容 新增 › 聊天摘要落库缓存,窗口重开不再重复生成 › 摘要窗口标题栏显示联系人头像,悬停支持复制、朗读、重新生成 › RelayOne 余额胶囊与账户状态条,支持充值和 API Key 管理 › 日期跳转日历支持日/月/年逐级选择 › 删除自画像功能,克隆自画像流程优化 修复 › 修复公众号消息空白:消息库扫描范围扩展至 `biz_message_*.db` › 修复技能跨盘导入时重命名失败(EXDEV) › 修复发送按钮图标与实际状态不一致的三处问题 › 修复日历中无消息日期仍可跳转的问题 › 修复 AI 摘要窗口输入框样式与 Agent 不一致的问题 调整 › 液态玻璃贴图重建加尾沿去抖,输入框位移动画不再掉帧 › 修复 Agent 流式输出期间历史消息 memo 失效导致的卡顿 › Ag

Signed CipherTalk

4 Aug 2026, 16:38 UTC307 views2 reactionsread 7 August 2026
Photo

CipherTalk v2026.805.0 让等待,不再绕圈 更新内容 新增 › 宠物库支持滚动自动懒加载,滑到哪,加载到哪,不再一次性托底。 › 应用版本信息开始随 `setPaths` 向下游传递,为后续诊断与兼容判断铺路。 › 自定义 AI 接入指南补全,打包读取逻辑同步修正,少踩一个文档与代码脱节的坑。 修复 › 修复视频卡片无限加载:上一版引入的 `cancelled` 标志与 `videoLoading` 依赖互锁,造成必然的 loading 死循环。现在无论请求是否被取消,都会重置加载状态,并从依赖数组中移除 `videoLoading`,从根上绕开这片雷区。 › 视频文件命中逻辑进一步打磨:当 `hardlink.db` 缺少记录时(旧版本数据或备份迁移数据),改用文件大小 + md5 逐级筛选,能确定就返回,不能确定就宁可不返回,不再瞎猜。 调整 › 微信窗口锚定逻辑重写,补

2

Signed CipherTalk

2 Aug 2026, 19:25 UTC433 views4 reactionsread 7 August 2026
Photo

CipherTalk v2026.803.0 视频归航 更新内容 新增 › 添加对话架构迁移功能,新增 agent_conversations 与 agent_messages 表,并实现增量迁移逻辑,为未来功能打好地基。 › 视频查找新增 selectUniqueVideoCandidate 函数,并更新组件以支持视频缓存键构建。 › 微信密钥获取支持重启选项和用户确认提示,操作步骤更透明。 › 安装程序新增自定义欢迎页与完成页,并同步更新版本号。 修复 › 修复聊天查看无法显示视频的问题,以及导出视频无法完全导出的问题(PR #307)。 › 修复转发聊天记录时,发言人被错误计入导出成员列表的问题(PR #306)。 › 修复视频文件无法命中的问题:适配微信 4.X 的 hardlink.db 映射逻辑;针对无 md5 码的记录,改为按文件大小扫描候选,尽量命中视频文件。 调整 ›

👍4

Signed CipherTalk

30 Jul 2026, 18:23 UTC587 views1 reactionsread 7 August 2026
Photo

CipherTalk v2026.731.1 夏末补丁 更新内容 修复 › 修复导出聊天记录时,所选时间段内无消息时无法正确展示错误提示(感谢 @Tokisaki-Galaxy 提出并修复) › 修复朋友圈缩略图可显示但点击预览后裂图的问题(感谢 @kelaocai 定位到 file:// 路径丢失的根源) 调整 › 发布流程修整:将 CI 与版本发布脚本做了一次梳理,减少人工干预点,后续更新投递会更顺畅。 5 commits · 2026-07-30

😱1

Signed CipherTalk

30 Jul 2026, 17:53 UTC518 views1 reactionsread 7 August 2026
Photo

CipherTalk v2026.731.0 液态玻璃与导出重生 更新内容 新增 › **独立聊天摘要窗口**:`ChatSummaryWindow` 正式上线,AI 摘要不再挤在聊天框里,清爽得像刚擦过的玻璃。 › **液态玻璃按钮与标题栏**:窗口控制按钮、标题栏都覆盖了一层液体玻璃效果,拖动窗口时有种指尖划过水面的错觉。 › **微信自动回复**:基于 WeChat 集成,你终于可以给自己放个假,让 CipherTalk 帮你应付那些“嗯嗯”。 › **macOS 辅助功能权限检查提示**:针对 Mac 用户,现在启动时会贴心地提醒你给足权限,而不是等崩溃后才恍然大悟。 › **视频播放按钮样式 & 液态效果**:视频气泡里的播放按钮也做了液态玻璃渲染,点击之前就先被美到。 修复 › **导出图片为空 / 进程崩溃 / 明文图片损坏**(PR #293):ffmpeg 的 EPIPE 崩溃、

1

Signed CipherTalk

28 Jul 2026, 19:26 UTC531 viewsread 7 August 2026
Photo

CipherTalk v2026.729.0 流芯重塑 更新内容 新增 › Codex 订阅模型解析功能上线,模型列表获取逻辑更聪明、更稳定 › 文本生成支持流式处理,每次输出都更丝滑,不再等待一整段话的煎熬 › WcdbCore 初始化流程优化:移除陈旧的“可信时间同步”代码,启动更干净,错误处理更干脆 调整 › 更新 Mac 端动态库,适配系统底层变化,跨平台体验更统一 › 发布工程调整,版本分发链路更稳定,你收到更新通知会更准 5 commits · 2026-07-28

Signed CipherTalk

28 Jul 2026, 18:05 UTC489 views5 reactionsread 7 August 2026

iOS 端微信,插件版本,80%的封号概率,请自行侦辨,永远都不要想自己是那20%

😱5

Showing the 12 most recent of 20 posts we hold for @CipherTalk. 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 — 310,468 of 1,340,412entries 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“密语 CipherTalk” (@CipherTalk), 1,577 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/CipherTalk.

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.