1.6.0 建议升级至此版本 此版本不支持旧版本分享的订阅码 优化画中画 优化部分源加载问题
👍24🔥3❤1
Channel
@EasyBoxUpdate
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
2,030subscribers
-82 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001844178278 |
|---|---|
| Type | Channel |
| Username | @EasyBoxUpdate |
| Created | Between 1 October 2022 and 1 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/EasyBoxUpdate |
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 16 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 08:17 | 2,030 | -6 |
| 11 Nov 2026, 16:40 | 2,036 | -2 |
| 8 Nov 2026, 02:31 | 2,038 | -6 |
| 4 Nov 2026, 14:51 | 2,044 | -8 |
| 1 Nov 2026, 11:31 | 2,052 | -3 |
| 29 Oct 2026, 08:41 | 2,055 | -8 |
| 23 Oct 2026, 05:35 | 2,063 | -3 |
| 20 Oct 2026, 12:49 | 2,066 | -4 |
| 17 Oct 2026, 11:27 | 2,070 | -2 |
| 14 Oct 2026, 20:11 | 2,072 | -3 |
| 11 Oct 2026, 05:57 | 2,075 | -3 |
| 5 Oct 2026, 06:37 | 2,078 | -2 |
| 26 Sept 2026, 22:19 | 2,080 | -9 |
| 15 Sept 2026, 19:38 | 2,089 | +1 |
| 11 Sept 2026, 21:38 | 2,088 | -3 |
| 7 Sept 2026, 07:56 | 2,091 | -8 |
| 3 Sept 2026, 00:15 | 2,099 | -1 |
| 27 Aug 2026, 12:08 | 2,100 | +1 |
| 24 Aug 2026, 17:34 | 2,099 | -3 |
| 20 Aug 2026, 20:14 | 2,102 | first reading |
20 posts held, back to 1 April 2023 — 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 19 April 2025. An engagement rate over an empty window would be a number about nothing.
304 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 79.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 243 | 79.9% | |
| ❤ | 27 | 8.88% | |
| 🆒 | 12 | 3.95% | |
| 🔥 | 9 | 2.96% | |
| 🥰 | 6 | 1.97% | |
| ❤🔥 | 4 | 1.32% | |
| 🎉 | 1 | 0.329% | |
| 😁 | 1 | 0.329% | |
| 🤪 | 1 | 0.329% |
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 18 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 304 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 1 April 2023 to 19 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
1.6.0 建议升级至此版本 此版本不支持旧版本分享的订阅码 优化画中画 优化部分源加载问题
👍24🔥3❤1
File, posted without a caption
❤12
1.5.5 升级自动去广告 优化部分闪退问题(依然存在一些留给下次) 升级exo播放器 支持配置全局UA(优先使用源提供的) 播放器设置添加自动旋转 N个优化……
👍21🔥2
File, posted without a caption
1.3.9 修复更换安全dns崩溃问题 优化直播源加载失败一直转圈 优化部分源无法加载问题
👍22
File, posted without a caption
👍29❤2😁1
1.3.5 获取阿里token调整 支持获取夸克Cookie 支持推送 支持hipy 修复N个bug 1.3.6 优化首页分类加载不出问题 修复bug 1.3.7 支持自动去广告(采用道长drpy去广告方案) 修复bug 1.3.8 修复去广告导致部分视频播放失败问题 支持备份恢复 支持后台播放(在设置中心开启) 优化部分问题
🔥4👍3❤1🎉1
File, posted without a caption
视频解析优化 播放界面滑动调整亮度音量进度优化 下载功能优化 增加弹幕功能(需资源支持) 修复投屏异常问题 EXO缓冲支持,隧道模式支持 cat js源支持 界面微调 优化N个bug
👍33🥰2❤1
File, posted without a caption
👍36❤6🥰1
修复上一版本部分bug
❤2
File, posted without a caption
👍23🆒11
Showing the 12 most recent of 20 posts we hold for @EasyBoxUpdate. 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“EasyBox更新日志” (@EasyBoxUpdate), 2,030 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/EasyBoxUpdate.
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.