官网恢复正常了,不建议用谷歌浏览器访问,会提示高风险 需要重新复制订阅链接更新节点,更新订阅需要挂梯子,暂不支持直连更新 所有用户已补偿10天时间

Channel
免流云更新频道|优惠活动通知
@mlycloud
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,514subscribers
+510 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002113753199 |
|---|---|
| Type | Channel |
| Username | @mlycloud |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/mlycloud |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 13:02 | 3,514 | -26 |
| 13 Sept 2026, 01:39 | 3,540 | +34 |
| 8 Sept 2026, 18:17 | 3,506 | -15 |
| 3 Sept 2026, 20:36 | 3,521 | -20 |
| 31 Aug 2026, 08:29 | 3,541 | -158 |
| 28 Aug 2026, 01:04 | 3,699 | +10 |
| 25 Aug 2026, 00:07 | 3,689 | +118 |
| 21 Aug 2026, 01:06 | 3,571 | +143 |
| 17 Aug 2026, 14:59 | 3,428 | +198 |
| 14 Aug 2026, 00:57 | 3,230 | +228 |
| 10 Aug 2026, 18:05 | 3,002 | -41 |
| 8 Aug 2026, 02:57 | 3,043 | +39 |
| 7 Aug 2026, 13:31 | 3,004 | no change |
| 7 Aug 2026, 12:24 | 3,004 | first reading |
Engagement
21 posts held, back to 6 April 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 2 pages 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
23 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 52.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 52.2% | |
| 💩 | 5 | 21.7% | |
| 👎 | 2 | 8.70% | |
| 💔 | 2 | 8.70% | |
| 👍 | 1 | 4.35% | |
| 😁 | 1 | 4.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 21 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 6 April 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
后面会有补偿,不要着急
官网服务器嗝屁了,目前官网无法访问,订阅无法更新,节点正常使用,等我换官网服务器恢复
💔2
官网、国外节点都已修好,所有人增加5天时长
💩5
北京节点已经切换到非80 443端口,请各位免流大佬注意免流情况
👎2❤1
新增北京节点,包含80和443端口,请更新订阅食用
❤2😁1
自动检测脚本已经上线了,出现故障会在3分钟之内自动修复完成,修复后需要大家更新订阅使用
❤1
为保证节点运行更稳定,国外节点已设置为每8小时更换一次新ip,需要及时更新订阅获取最新的节点地址
👍1
现在修复节点,会自动将节点域名直接修改为节点的ip地址,所以每次修复后,都需要更新一下订阅节点就好了,不需要再等待域名解析生效了
湖北bgp线路恢复正常了,刷抖音不需要等待了,秒加载
订阅链接已更新修复国内直连无法更新的问题,有需要请到官网复制最新订阅、
湖北节点已切换至bgp网络
Showing the 12 most recent of 21 posts we hold for @mlycloud. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“免流云更新频道|优惠活动通知” (@mlycloud), 3,514 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/mlycloud.
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.