22 Jul 2026, 18:11 UTC73 viewsread 8 August 2026
Forwarded from @TVBoxOSCFile
Credit: #q215613905 Commit: 0409954033a44582b431d89934e3980900f4a265 Changelog: 修正python32包部分设备莫名闪退 移除旧quickjs遗留代码
Channel
舒夏博客交流频道
@sxbai
On this record: Growth · Engagement · Posts · Citations · Cite this entry
602subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001124124621 |
|---|---|
| Type | Channel |
| Username | @sxbai |
| Created | Between 1 June 2017 and 31 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/sxbai |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:25 | 602 | -2 |
| 14 Aug 2026, 00:54 | 604 | -1 |
| 8 Aug 2026, 03:05 | 605 | no change |
| 7 Aug 2026, 12:34 | 605 | first reading |
Engagement
4 posts held, back to 9 July 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 1 pageof 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 4 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
12 Jul 2026, 08:55 UTC191 viewsread 8 August 2026
File
History & AI Recommendations: Users can now selectively delete individual watch history, search history, and playback progress records. This granular control ensures that AI recommendations align more closely with user expectations. Cloud Drive Features: Added a "115 to 123" rapid transfer (instant save) feature, enabling unlimited playback. Note: This requires a QR code login to authorize 123 Cloud Drive via OpenLis…
11 Jul 2026, 12:09 UTC73 viewsread 8 August 2026
Forwarded from @TVBoxOSCFile
Credit: #q215613905 Commit: 2f2948813fceae53a8eef1abfe3fd1ca6b24fc86 Changelog: 优化m3u文本解析
9 Jul 2026, 16:49 UTC84 viewsread 8 August 2026
Forwarded from @TVBoxOSCFile
Credit: #q215613905 Commit: 5b4cfbfbfd94ca4acc35c01152159a0826aed422 Changelog: 分类顶部下拉刷新 优化js加载 优化python加载 解决部分手机弹出导航栏的问题 优化详情线路解析 jar加载过滤壳验证 代理地址兼容 修正手机上偶发样式异常 进度条支持焦点移动 python稳定性调整 修正主页偶发的闪退 Revert \"详情退回时异常兜底\" This reverts commit 23cedebdbe10b05e9d09b8501bb538d23924817e. 详情退回时异常兜底
Showing the 4 most recent of 4 posts we hold for @sxbai. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“舒夏博客交流频道” (@sxbai), 602 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/sxbai.
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.