Telegram RegisterThe public register of Telegram
Telegram profile photo for 小潼是废物。

Channel

小潼是废物。

@xiaotong_channel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

86subscribers

+0 since we began measuring on 3 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001872356328
TypeChannel
Username@xiaotong_channel
Description小潼是废物。
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live3 November 2026
Measurements held2
On Telegramt.me/xiaotong_channel

Growth

863 Nov 2026, 03:47 — 86 subscribers3 Nov 2026, 04:22 — 86 subscribers3 Nov 2026, 03:473 Nov 2026, 04:22
2 measurements taken within a single day. 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 85–87 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 04:2286no change
3 Nov 2026, 03:4786first reading

Engagement

17 posts held, back to 21 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
2274.4%
avg views ÷ 86 subscribers
Avg views / post
1,960
2 posts measured
Reaction rate
0.221%
reactions ÷ views · ER floor
Posts in window
2
of 17 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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held17 (21 July 2026 – 30 October 2026)
Views total3,912
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 04:22 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
41
Links
29

Lifetime counters from Telegram’s own channel header, read 3 November 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

14 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1285.7%
👍214.3%

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

Measured over the 17 most recent posts we hold, published 21 July 2026 to 30 October 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

Telegram’s own ‘edited’ marker: 1 of 2 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

30 Oct 2026, 04:44 UTC≈3,620 views8 reactionsread 3 November 2026

打扰米那桑了喵 小潼想说一下就是之前在测试 KernelSU SELinux Hide 时发现的一个时序侧信道问题喵,这个检测点目前已经公开了,对应的修复也已经通过 #3936 合并了喵(也许还存在一些玄学) 小潼之前在测试 #3877 的时候,发现它似乎引入了新的可观测时序侧信道特征,检测思路就是利用 /proc/thread-self/attr/current 的 context 解析时序差异,借助 App Zygote 的 PROCESS__SETCURRENT 权限,向自身线程的 attr/current 写入两种长度相同的无效输入,分别记录内核拒绝写入所需的时间: A:u:r:selinux_hide_probe_invalid:s0 B:\n:r:selinux_hide_probe_invalid:s0(首字节换成换行符) 然后小潼在测试过程中发现,在 SELinux Hide OFF 的情况下,A 的耗 时通…

❤7👍1

16 Oct 2026, 15:45 UTC292 viewsread 3 November 2026
Photo

现在的 Sui 是 基于 view 的 Material + MIUIX 两套 UI 组合喵

23 Sept 2026, 17:46 UTC474 viewsread 3 November 2026

此提交后的更新内容: 1. 新增 ADB Root 管理入口,可直接在 Sui 中选择「关闭」「下次启动启用一次」或「始终启用」,不用自己动 marker 文件 https://github.com/XiaoTong6666/Sui/commit/c83e85a55482c25f517212309c20d02e52b66472 2. 新增 KernelSU Shell 防重新提权功能。启用后,Sui Shell、Rish、Shell 模式 Shizuku API 及其 UserService 进程树不可以再次通过 KernelSU 获取 root 权限(https://github.com/tiann/KernelSU/pull/3509/ 感谢原神佬喵) https://github.com/XiaoTong6666/Sui/commit/2465053afad18ddffffbb0eff803081f24bfb4d7 …

23 Sept 2026, 06:15 UTC262 views2 reactionsread 3 November 2026
Photo

https://github.com/XiaoTong6666/FuseHide/commit/c981383f0bbbd0bdc66091543e4ee8343fd424a5 给 FuseHide 的主页进行了重构,参考了 KernelSU 的首页的风格喵

❤2

23 Sept 2026, 06:13 UTC233 viewsread 3 November 2026

https://github.com/XiaoTong6666/MaiHoku 小潼的自用 Xposed 模块喵( 目前可以对官方 tg 客户端尝试关掉 sms fee,把无来源转发和显示用户id/dc给加上了,参考nekogram

22 Aug 2026, 18:34 UTC305 viewsread 3 November 2026
Photo

https://github.com/XiaoTong6666/Sui/commit/5a508d1c65d5e71fdbe5e82391a5f9846816c65e 兼容部分仍通过旧版 Shizuku Binder 广播协议获取服务的应用: 应用直接发送 Intent("rikka.shizuku.intent.action.REQUEST_BINDER").setPackage("moe.shizuku.privileged.api") 然后在 extras 中携带回调 Binder 喵 Sui 现在会在 system_server 的 Binder 层拦截 IActivityManager 的 broadcastIntent / broadcastIntentWithFeature 事务,识别 REQUEST_BINDER 请求,并通过回调返回 Sui 的 Binder 建立连接喵 但是还是有一些取舍,先用用看吧喵…

22 Aug 2026, 16:43 UTC237 views1 reactionsread 3 November 2026

他们都看不起我,偏偏我也不争气,无人扶我凌云志,我自己也上不去。 人人都笑话我,偏偏我也最好笑,但凡我有点本事,也不至于一点本事也没有。 与其逼自己一把,不如放自己一马。 是金子总会发光,偏偏我是老铁。 生活给我一巴掌,我说没上次响。 能打败我的人,我也不跟他们打。 没有人可以利用我,因为我没有用。 生活反复捶打我,使我肉质QQ弹弹。 爱笑的人运气不会太差,因为运气差的人笑不出来。 前途一片黑暗,黑黑的我只好睡觉。 强者从不抱怨环境,但我是弱者,我不仅抱怨环境,我还抱怨强者。

👍1

17 Aug 2026, 07:21 UTC301 viewsread 3 November 2026
Photo

https://github.com/XiaoTong6666/FuseHide/commit/4b3a2ba839565000bd826d895007fd9bc80e5701 FuseHide 现已支持以 Zygisk + Dobby 作为 native hook 后端了喵。构建完成后,只需要将生成的 APK 后缀重命名为 ZIP,即可直接作为 Magisk、KernelSU 等模块刷入喵~ 相关功能已经在这个提交中加入了喵~ 当然,小潼不会移除原有的 Xposed 后端的喵。在日常使用以及开发、测试和调试过程中,小潼个人还是会优先选择 LSPosed / Vector 之所以新增 Zygisk 支持,主要也是考虑到部分用户并不喜欢或不使用 LSPosed / Vector 现在 FuseHide 同时提供 LSPosed / Vector 和 Zygisk 两种注入方式,大家可以根据自己的使用环境和偏好进行选择喵~ …

14 Aug 2026, 19:17 UTC179 viewsread 3 November 2026
Photo

https://github.com/XiaoTong6666/ZygoteNextProbe 依旧isolated,依旧ns,依旧扫mountinfo init 以 root 身份启动 zygote_next: https://android.googlesource.com/platform/system/zygote/+/refs/tags/android-17.0.0_r1/zygote/zygote_next.rc#1 zygote_next 处理 spawn 请求时直接调用 fork() ,随后进入 child re-initialization; 这些函数本身没有经典 zygote 的 CLONE_NEWNS/MS_SLAVE 初始化: https://android.googlesource.com/platform/system/zygote/+/refs/tags/android-17.0.0_r1/zyg…

12 Aug 2026, 12:45 UTC159 viewsread 3 November 2026
Photo

试了下可以用,挺好的,感谢波老师的x64lkm喵

8 Aug 2026, 19:31 UTC194 viewsread 3 November 2026

该玩具已传 Github 网盘 https://github.com/XiaoTong6666/MaiHoku

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“小潼是废物。” (@xiaotong_channel), 86 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/xiaotong_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.