https://github.com/volcengine/volcengine-python-sdk/issues/54

Channel
某小学生的破事水日常
@anankkew
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
877subscribers
+8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001115558129 |
|---|---|
| Type | Channel |
| Username | @anankkew |
| Created | 21 September 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/anankkew |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 12 Sept 2026, 12:18 | 877 | +2 |
| 3 Sept 2026, 12:37 | 875 | -1 |
| 27 Aug 2026, 16:56 | 876 | -1 |
| 19 Aug 2026, 22:28 | 877 | +6 |
| 13 Aug 2026, 05:26 | 871 | +2 |
| 6 Aug 2026, 14:34 | 869 | no change |
| 6 Aug 2026, 02:15 | 869 | first reading |
Engagement
20 posts held, back to 17 December 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
「尽管目标技术精湛,在网络安全上很小心,我们的特工还是完整复制了目标的操作系统状态并且找到了利用链…」 「(口哨)你们是怎么做到的。」 「(尴尬地咳嗽)目标把整个可复现的NixOS放在GitHub并且锁了版本。」
幻兽帕鲁有 server to client RCE 可以稳定通杀,恶意服务器可以执行任意代码 0 难度,一会放 POC
玩儿帕鲁的有福了
你们 UE 5.1 这神人也有说法的
Photo, posted without a caption
稳定通杀
永远支持 altman 和杨植麟
至于 amodei,我和他不熟,祝他生意不好
原来是 LLM 生成文本啊,不知道的还以为是把输入剁成一堆拿大量文本统计出的最常见字符串组合的词元,高频组合各占一个词元而生僻词拆成更小的子词元,查询一张几万行的大对照表把每个词元换成几千维的数字串每一层除以各元素的均方根,下面把每串数字各与三个不同的矩阵相乘变出 QKV 三个值,在 Q 和 K 上按各自的位置乘一个旋转矩阵把位置信息融合进去,所有的位置用 Q、K 两两点积再除以根号 d_k 把数值压回正常量级,算完先把当前位置后面的未来词元全部用负无穷遮住,再用 softmax 把分数归一化按权重把 V 加权混合成新的数字串,并行跑好几个头再横向拼在一起,再乘一个 W_O 输出投影矩阵线性变换,把结果通过残差加回原来的数字串,省得十几层下来原始信息洗没梯度也传不回去。再过一遍 RMSNorm,扔进一个先把维度扩到约八除以三倍再缩回来的两层矩阵变换里,中间把输入拆两路一路过 SiLu 激活一路不过逐元素相乘,再把结果加回去。这个…
?Wasmer 把完整的 Gecko 引擎和 Firefox UI 编译成了 WASM, 甚至还支持 GPU 加速和 JIT feat,现在你可以在任何浏览器打开 Firefox 了 而且,Only ~50MB! https://developer.puter.com/labs/firefox-wasm/
新王登基
Showing the 12 most recent of 20 posts we hold for @anankkew. 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.
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.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“某小学生的破事水日常” (@anankkew), 877 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/anankkew.
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.