POTATO CLOUD 通知: 已为所有未到期的用户补偿15天
❤2

Channel
@tudouyun
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,570subscribers
+30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001879873155 |
|---|---|
| Type | Channel |
| Username | @tudouyun |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/tudouyun |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 23:21 | 1,570 | -6 |
| 11 Nov 2026, 09:00 | 1,576 | +2 |
| 7 Nov 2026, 08:28 | 1,574 | -2 |
| 4 Nov 2026, 11:06 | 1,576 | +4 |
| 1 Nov 2026, 16:10 | 1,572 | +1 |
| 29 Oct 2026, 19:40 | 1,571 | -1 |
| 27 Oct 2026, 04:17 | 1,572 | +2 |
| 24 Oct 2026, 07:18 | 1,570 | -1 |
| 18 Oct 2026, 09:15 | 1,571 | +2 |
| 15 Oct 2026, 07:04 | 1,569 | -1 |
| 11 Oct 2026, 22:22 | 1,570 | +3 |
| 5 Oct 2026, 03:59 | 1,567 | +4 |
| 26 Sept 2026, 12:20 | 1,563 | +2 |
| 15 Sept 2026, 11:20 | 1,561 | +5 |
| 11 Sept 2026, 14:38 | 1,556 | +3 |
| 6 Sept 2026, 21:42 | 1,553 | +2 |
| 2 Sept 2026, 18:44 | 1,551 | +3 |
| 30 Aug 2026, 22:05 | 1,548 | -4 |
| 27 Aug 2026, 13:53 | 1,552 | +4 |
| 21 Aug 2026, 03:51 | 1,548 | first reading |
20 posts held, back to 24 November 2025 — 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 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
25 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 64.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 16 | 64.0% | |
| ❤ | 9 | 36.0% |
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 7 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 25 reactions 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 24 November 2025 to 5 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.
POTATO CLOUD 通知: 已为所有未到期的用户补偿15天
❤2
POTATO CLOUD 通知: 月付价格已恢复,同时我们将对重置流量包的价格进行调整,调整后重置流量包的价格为月付价格+1
POTATO CLOUD 通知: iPhone /ipad用户下载软件:AppsConnect 输入识别码使用
POTATO CLOUD 通知: 鉴于当前网络状况,所有新老套餐月度付费价格下降10%,其它周期不变,恢复时间另行通知
POTATO CLOUD 通知: Apple TV os 版已上架,欢迎下载使用体验并提出问题
POTATO CLOUD 通知: 基于目前网络状况产生的问题,即日起开始排查共享订阅用户,如果你此时还在共享,请马上停止并重置订阅链接,一经发现将会被封禁,请悉知!!!
POTATO CLOUD 通知: 已上架客户端,可以前往教程下载使用,目前支持windows Mac android openwrt (IOS 上架中)
👍2
POTATO CLOUD 通知: 近期节点出现不稳定情况,厂主已经在想办法解决,后期会发放补偿,感谢家人们理解支持!
❤2
POTATO CLOUD 通知: 如果更新后发现用不了,可能是你的软件太旧不支持新协议,建议在教程下载新版软件使用
POTATO CLOUD 通知: 请大家更新订阅,旧节点将在不久后清除
POTATO CLOUD 通知: 将开始进行协议更换工作
POTATO CLOUD通知: 1.节点维护已完成,请前往网站下载最新版软件进行安装使用! 2.:目前陆续增加Hysteria 测试节点,请大家在使用过程中有任何使用问题提交工单反馈 3.工单积累较多,如有问题可在今日重新开始提交工单,依次处理! 4.补偿卡:20260406 有效期至4.13 23:59(使用此补偿卡的同时账单日也会跟随改变) 5.关于最近节点问题的说明,由于众所周知的不可抗因素,目前本机场已无法对抗,后续尽最大程度保证节点的可用性,体验上较以往会有所不同,持续时间未知,等后续发展情况而定
👍6❤2
Showing the 12 most recent of 20 posts we hold for @tudouyun. 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“POTATO CLOUD 通知频道” (@tudouyun), 1,570 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/tudouyun.
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.