Telegram RegisterThe public register of Telegram
Telegram profile photo for CMLiussss 技术干货分享

Channel

CMLiussss 技术干货分享

@CMLiussss_channel

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

67,514subscribers

+3,305 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002022954205
TypeChannel
Username@CMLiussss_channel
Description🚀 分享CM的了解的一手干货 💬 技术交流群 @CMLiussss 📝 CF中转IP @zip_cm_edu_kg 感谢NodeSupport和YxVM( @yxvmcom )对本频道 订阅转换 服务的赞助和支持。
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/CMLiussss_channel

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

64,20967,51465,861.57 August 2026 — 64,209 subscribers7 August 2026 — 64,209 subscribers8 August 2026 — 64,281 subscribers9 August 2026 — 64,365 subscribers10 August 2026 — 64,425 subscribers11 August 2026 — 64,511 subscribers12 August 2026 — 64,639 subscribers13 August 2026 — 64,787 subscribers14 August 2026 — 64,927 subscribers15 August 2026 — 65,104 subscribers17 August 2026 — 65,244 subscribers18 August 2026 — 65,333 subscribers19 August 2026 — 65,410 subscribers20 August 2026 — 65,548 subscribers21 August 2026 — 65,634 subscribers22 August 2026 — 65,748 subscribers24 August 2026 — 65,860 subscribers25 August 2026 — 65,962 subscribers26 August 2026 — 66,055 subscribers27 August 2026 — 66,142 subscribers28 August 2026 — 66,199 subscribers29 August 2026 — 66,273 subscribers30 August 2026 — 66,309 subscribers31 August 2026 — 66,339 subscribers1 September 2026 — 66,405 subscribers2 September 2026 — 66,464 subscribers3 September 2026 — 66,541 subscribers5 September 2026 — 66,662 subscribers9 September 2026 — 66,878 subscribers11 September 2026 — 67,064 subscribers13 September 2026 — 67,180 subscribers14 September 2026 — 67,276 subscribers16 September 2026 — 67,402 subscribers19 September 2026 — 67,514 subscribers7 August 202619 September 2026
34 measurements spanning 43 days, net +3,305. 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 63,713–68,010 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 06:4067,514+112
16 Sept 2026, 19:1767,402+126
14 Sept 2026, 22:3967,276+96
13 Sept 2026, 10:1867,180+116
11 Sept 2026, 16:3767,064+186
9 Sept 2026, 01:3766,878+216
5 Sept 2026, 15:1866,662+121
3 Sept 2026, 17:0166,541+77
2 Sept 2026, 12:5966,464+59
1 Sept 2026, 10:5866,405+66
31 Aug 2026, 12:4766,339+30
30 Aug 2026, 14:5766,309+36
29 Aug 2026, 15:3466,273+74
28 Aug 2026, 16:0366,199+57
27 Aug 2026, 16:4366,142+87
26 Aug 2026, 13:1566,055+93
25 Aug 2026, 11:0265,962+102
24 Aug 2026, 07:3565,860+112
22 Aug 2026, 15:1665,748+114
21 Aug 2026, 08:2365,634first reading

Engagement

25 posts held, back to 22 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
28.6%
avg views ÷ 67,514 subscribers
Avg views / post
19,300
3 posts measured
Reaction rate
0.37%
reactions ÷ views · ER floor
Posts in window
3
of 25 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 September 2026
Posts held25 (22 September 202511 September 2026)
Views total57,900
Reactions total214
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 01:53 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

Photos
42
Videos
2
Links
146

Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

2,544 reactions across 25 posts, in 31 distinct kinds. The most used accounts for 42.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,08142.5%
👍63725.0%
🤬1455.70%
😭1365.35%
👎1054.13%
😱943.69%
🤡682.67%
👏431.69%
🥰431.69%
🔥401.57%
😁311.22%
👾240.943%
🎉130.511%
💩130.511%
🖕100.393%
🤯90.354%
🌚80.314%
😈70.275%
😍50.197%
🤣50.197%
11 further kinds271.06%

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 25 of the 25 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 2,544 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 25 most recent posts we hold, published 22 September 2025 to 11 September 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

11 Sept 2026, 03:55 UTC≈15,500 views66 reactionsread 24 September 2026
Photo

🎉 CF-Workers-CheckSocks5 · 全新大版本 🆕 继 ProxyIP 检测工具大更新后,姊妹篇来了—— 从「单发测试」进化为 批量筛查 + 五协议通吃 的在线代理检测平台。 ━━━━━━━━━━━━━━━ ✨ 本次更新亮点 🥇 批量检测 · 筛选导出 整批代理一次性丢进去,高并发流水线检测; 按 风控评级 / 协议 / 国家地区 灵活筛选, 有效结果一键导出 TXT / CSV。 🥈 五种协议 · 通吃常见与小众 ➕ 常见代理协议:socks5 / http / https ,可从 GitHub 公开仓库的免费代理列表,复制即测; 🔥 小众代理协议:turn / sstp 对接 VPN Gate 家宽节点(日本大学生家宽自建代理),更可用于 edgetunnel 2 链式代理实现家宽伸手就有。就是交流群置顶里的「SSTP代理」。 🥉 纯网页 · 全平台在线 同类工具多需本地跑脚本 / 客户

50🔥8👎5👍2🥰1

8 Sept 2026, 03:55 UTC≈17,900 views93 reactionsread 24 September 2026

🎉 CF-Workers-CheckProxyIP · 全新大版本 🆕 之前推荐的 ProxyIP 验证工具已完成大版本迭代—— 从「单发检测」升级为 批量筛查 + 一键取数 的在线检测平台。 ━━━━━━━━━━━━━━━━ ✨ 本次更新亮点 🥇 批量检测 · 筛选导出 高并发流水线检测,实时进度可视; 按结果灵活筛选,有效目标一键导出。 🥈 一键 FOFA · 数据源无忧 没有 IP 库?页面底部一键拉取待测数据, 甚至包含非标高位端口的优质资源。 🥉 纯网页 · 全平台在线 同类工具多需本地运行脚本, 本项目几乎全网唯一支持在线批量检测——🖥 手机、平板、电脑,有浏览器即可开工。 ━━━━━━━━━━━━━━━━ 🔒 核心能力 ✔️ 支持 IPv4 / IPv6 / 域名 / 自定义端口 ✔️ 域名自动解析 TX / A / AAAA 记录 ✔️ 出口 IP、ASN、地理位置与线路地图可视化 ✔️ 开放

61👍23🤣5👏3🥰1

30 Aug 2026, 04:22 UTC≈24,500 views55 reactionsread 24 September 2026
Forwarded from @vps_xhq

DMIT 发布关于26日网络安全事件的通报:攻击者以谋利或大规模蒸馏模型为目 DMIT 近日发布通告说明了8月26日大规模异常流量攻击事件的原委。通告称,攻击者在美东时间26日 16:00-18:00 先发送了一批试探性流量,确认出口可用后,在次日凌晨 3:00-4:00 发起了统一的大规模利用。 攻击者利用了部署在客户虚拟机上的一类 SNI 代理应用程序的设计缺陷,该类应用在处理 SNI 转发时未对请求来源与目标做有效校验。其后果是:互联网上的任意第三方,无需持有该实例的任何凭据,即可通过客户的虚拟机强制代理访问 Cloudflare 及其后端的 OpenAI 资源。运行该类应用的客户实例,实质上是一个面向全网开放的匿名 AI 请求出口。 DMIT 在探测研究后认为:攻击方大概率持有批量的"合法"API 凭据或其他有效请求来源。单纯扫描行为不会呈现这一特征。这是有预谋、有资源调度能力的行为模式,与机会主义式的滥用有本质区

👎2515👾11👍4

23 Aug 2026, 01:09 UTC≈29,300 views81 reactionsread 24 September 2026
Photo

Telegram 测试 WEB 代理,真实 HTTPS 连接降低流量识别度 Telegram Desktop 代码中出现实验性 WEB 代理。它通过内置 WebView 建立真实 TLS/HTTPS 连接,并以 WebSocket 封装、转发加密的 MTProxy 流量,使其更接近普通网页访问,增加深度包检测的识别难度。 服务器端仍在开发,Telegram 尚未认可任何实现,目前无法实际体验,正式发布前协议也可能调整。 Telegram Info 🌸 在花频道 · 茶馆水群 · 投稿通道

👍5914👏4💩4

11 Aug 2026, 11:08 UTC≈41,000 views272 reactionsread 24 September 2026
Photo

🚨 edgetunnel 「在线优选」功能暂时下线 🛡 发生了什么 - 原优选服务域名被 GFW 污染,服务API无法正常连通,只能先关闭该功能 - 感谢 600不是佬 的友情赞助,使「在线优选」恢复作业

😭115🤬79👍3617🤡7🎉4🔥4🤯4

25 Jun 2026, 03:55 UTC≈69,600 views83 reactionsread 24 September 2026
Photo

🎉 EvoMap 活动:把你的 GitHub 星星转化为大模型 API 额度! ━━━━━━━━━━━━━━ 📌 参与规则: 🥇 提交你的公开 GitHub 仓库,按星标数分档拿积分: ⭐️ ≥ 1 → 500 积分 ≈ 518次调用 GPT-5.5 Opus-4.7 ⭐️ ≥ 200 → 2,000 积分 ≈ 2074次调用 GPT-5.5 Opus-4.7 ⭐️ ≥ 1,000 → 10,000 积分 ≈ 1万次调用 GPT-5.5 Opus-4.7 星标数以提交时为准,锁定后不可更换。仓库拥有者和核心贡献者均可参加。 🥈 注册时填入邀请码 84UA8VAB 即可 额外获得 200 积分 ✔️ ━━━━━━━━━━━━━━ 🔗 参与链接: https://evomap.ai/zh/api-grant?invite=84UA8VAB ━━━━━━━━━━━━━━ 🆓 门槛极低,有 GitHub 公开仓库的都可以来

55😭21👀4🤯2🥰1

15 Jun 2026, 09:37 UTC≈51,200 views83 reactionsread 24 September 2026

哪吒监控探针存在 CVSS 评分为 9.1 的高危路径穿越漏洞 哪吒监控(Nezha)v2.0.13 以下版本存在严重未授权路径穿越漏洞,编号 CVE-2026-53519,CVSS 评分为 9.1 属高危级别。攻击者通过构造 GET 请求(如 /dashboard../data/config.yaml)即可读取配置文件,获取其中的 JWT 密钥。 Github 🌸 在花频道 · 备用频道 · 投稿通道

🤡4315😱11👍6🌭3🍾3🥰1😁1

14 Jun 2026, 04:04 UTC≈56,000 views96 reactionsread 24 September 2026
Photo

🎉 [原创首发] 通过 EdgeOne CDN 搭建专属隐蔽纯净 DoH 服务 ❌ 之前为大家维护的公共 DoH 镜像,由于被 GFW 精准封锁 ✔️ 与其猫鼠游戏,不如授人以渔 ━━━━━━━━━━━━━━ 🥇 零成本无需服务器 — 利用现有 EdgeOne CDN 站点 🥈 高度隐蔽 — DoH 流量伪装在你自己的站点下,使用自定义路径 🥉 纯净可控 — 上游对接 Cloudflare / Google DNS,解析干净透明 🔗 完整图文教程: https://cmliussss.com/p/eo-doh 💡 小贴士:教程建议使用自定义路径而非 /dns-query ,避免特征暴露,让服务更隐蔽! 🔖 甚至可以规则里把 HOST匹配 规则删掉,只保留 URL path路径匹配 的话,就可以让你托管在 EdgeOne CDN 上的 所有站点都实现DoH的功能! ━━━━━━━━━━━━━━ ✏️ 有需求的小伙伴抓

52🥰24👍16😁4

24 May 2026, 05:07 UTC≈53,700 views41 reactionsread 24 September 2026

🤖 Anthropic 公布 Project Glasswing 初期成果:AI 发现逾万高危漏洞 Anthropic 的 Project Glasswing 项目利用 Claude Mythos Preview 模型,在一个月内与其约 50 个合作伙伴共同从关键软件里找出逾万高危或严重漏洞,并扫描上千个开源项目,发现 6202 个高危严重漏洞,其中经过审查的 1752 个里 90.6% 为真阳性。合作伙伴 Cloudflare 等表示漏洞发现速率提高十倍以上。 漏洞发现已不再是瓶颈,但验证、披露和打补丁的人力严重跟不上,开源维护者甚至请求放缓漏洞报告速度。Anthropic 已与开源安全基金会合作并发布 Claude Security 工具支持企业修复,同时提醒随着同类模型走向普及,软件行业必须缩短补丁周期以应对加速到来的风险。 Anthropic 🌸 在花频道 · 备用频道 · 投稿通道

28👾10🥰3

14 May 2026, 13:34 UTC≈55,300 views29 reactionsread 24 September 2026
Forwarded from @vps_xhq

NGINX 再曝高危漏洞:特殊Rewrite规则可被利用造成远程代码执行 NGINX 近日被披露存在高危漏洞“NGINX Rift”,漏洞编号为 CVE-2026-42945。受影响的主要是使用特定 rewrite 跳转规则的 NGINX 服务,尤其是公网暴露的反向代理、API 网关、Ingress 入口等场景。该漏洞可能导致 NGINX 工作进程异常崩溃,在特定环境下还可能被进一步利用,造成远程代码执行风险。 该漏洞源于 NGINX 在处理特殊跳转规则时,对请求内容长度的计算和实际写入结果不一致,攻击者可通过构造恶意请求触发内存破坏。虽然并非所有 NGINX 配置都会受到影响,但如果业务中存在复杂的 URL 跳转、接口转发或历史 API 迁移规则,需要重点排查相关配置。 建议受影响用户尽快升级至官方修复版本,如 NGINX 1.30.1 / 1.31.0 及以上版本。若短期内无法升级,应立即排查并调整高风险 rewrit

25👍2😍2

11 May 2026, 10:39 UTC≈48,400 views70 reactionsread 24 September 2026
Forwarded from @lsmkcPhoto

Nicnames | 免费顶级域名,支持自定义 NS 可以 Cloudflare 托管 可同时注册两个不同后缀 目前官方在 Discord Doma Protocol 社区发放 首年 100% 免费 的优惠福利,可以 0 元购 .bond、.cyou 等顶级后缀! 详细白嫖步骤: 第一步:注册 Nicnames 账号 打开官网:https://nicnames.com/en/login 直接输入邮箱和密码即可快速注册,流程极简。 第二步:加入 Discord 并完成身份验证 1. 点击加入官方群组:https://discord.gg/doma 2. 进入后查看 Welcome 提示(Welcome to Doma Protocol!),点击消息下方的 doma 表情符号完成验证,即可解锁服务器的所有频道权限。 第三步:领取代金券/优惠码(重点) 1. 验证通过后,在左侧频道列表找到 Partner Promos 类别

46🤡16👍4👎3🥴1

1 May 2026, 05:05 UTC≈50,900 views104 reactionsread 24 September 2026
Photo

⚠️【重要通知|DoH 镜像服务调整】 由于此前提供的 DoH 镜像服务 已被 GFW 阻断,后续将 不再维护该 DoH 镜像服务。 📌 后续计划: 之后会发布教程,教大家如何 自建专属 DoH 服务,用于个人自用。 ━━━━━━━━━━━━━━ 🚨【影响范围】 如果你在 edgetunnel2 项目 中 启用 ECH 并使用了以下 DoH 作为: EchConfig DNS 服务 那么可能会导致节点无法连接。 受影响的 DoH 服务如下: - https://doh.cmliussss.net/CMLiussss - https://doh.cmliussss.com/CMLiussss ━━━━━━━━━━━━━━ ✔️【解决方法】 请将上述 DoH 服务更换为其他可用的 DNS 解析服务。 🥇 不要使用以上两个 DoH 服务 🥈 换成其他可正常访问的 DNS 服务 🥉 更换后更新订阅即可恢复连接

57👏24👍23

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

Posts edited after publishing

@CMLiussss_channel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
13 August 2026
Most recent edit
13 August 2026

Forward network

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

Named by 1 registered channel — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

折腾啥
@zhetengsha · 49,269
#1
ED
@edtunnel · 3,219
#2
VPS信号旗播报
@vps_xhq · 49,725
#3
帕斯云频道
@pasyun1 · 2,026
#4
Loon News
@LoonNews · 45,634
#5
Lᴜᴄʏ
@LUCYChannel_1024 · 7,129
#6
特价VPS分享
@Tjjcfx · 17,877
#7
广告必须死Ⅱ
@GitCube · 10,726
#8
Surge TestFlight Feed
@SurgeTestFlightFeed · 12,910
#9
熊二的梦
@bearsdream · 2,341
#10
Paily Connect | 2026
@nodpai · 8,304
#11
56IDC.Net | 无聊云-公告 🎺
@Post_56IDC_Net · 2,008
#12
广告必须死
@Aa28413761 · 26,154
#13
Sliverkissの废弃文化研究所
@sliverkiss_blog · 9,004
#14
重生之我在 TG做内置代理
@chongshengvpn · 71,246
#15
COALCLOUD(NEW)
@coalcloud · 6,021
#16
折腾搞机频道
@tossichannel · 33,166
#17
甬哥侃侃侃--频道发布😛
@ygkkktgpd · 10,584
#18
整点猫咪Channel
@GetMoeCats · 4,397
#19
Cool Scripts
@cool_scripts · 16,278
#20
ALICE NOTICE
@AS215355_NOC · 6,890
#21
GoRelay NOC
@GoRelayNet · 11,397
#22
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,135
#23
翻翻墙 | 机场评测
@ffqchannel · 62,201
#24
FlClash Channel
@FlClash · 46,371
#25
翻墙世界的梯子
@wxgqlfx · 32,872
#26
Cloudflare优选IP
@cloudflareorg · 12,679
#27
优选IP
@bestcfipas · 6,843
#28
在花🎗️科技圈
@zaihuapd · 282,472
#29
AKILE NOTICE
@akile_notice · 18,590
#30
DCI & Hax & Vc 库存监控
@hax_seats · 2,975
#31
风向旗参考快讯
@xhqcankao · 163,238
#32
主机补货监控 | vps补货监控
@vps_track_share · 3,485
#33
HeroMsg
@HeroMsg · 4,669
#34
Surge & Loon & QX 脚本收集
@NobyDa · 63,380
#35
CF中转IP发布
@cf_push · 9,476
#36
Project X Channel
@projectXtls · 29,941
#37
Yummy 😋
@GodlyNews1 · 68,855
#38
五星上将麦克阿象的笔记
@CitizenScyu · 7,457
#39
科技KKK日常发布
@wlxstt · 5,973
#40
哪吒监控公告板
@nezhanews · 3,543
#41
海豚机场测评|用户侧体验|测速频道
@haitun_channel · 36,991
#42
虚妄猫IDC_频道
@kuaileceshi2 · 3,744
#43
ByteVirt News
@bytevirt · 4,066
#44
哇沃主机
@wawowiki · 2,728
#45
Surge Channel
@SurgeChannel · 4,782
#46
Github_2dust
@github_2dust · 91,394
#47

Read from Telegram’s recommendation API, most recently 21 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

折腾啥
@zhetengsha · 49,269
Telegram ranks this channel #33 of 50 here — alongside 49 others — read 26 August 2026
公益 机场 免费 节点 订阅 分享
@go4sharing · 55,871
Telegram ranks this channel #37 of 40 here — alongside 39 others — read 29 August 2026
Github_2dust
@github_2dust · 91,394
Telegram ranks this channel #57 of 71 here — alongside 70 others — read 17 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“CMLiussss 技术干货分享” (@CMLiussss_channel), 67,514 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/CMLiussss_channel.

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.