https://fxtwitter.com/isukkaw/status/2115732663768347124

Channel
Sukka's Notebook
@SukkaChannel
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
6,937subscribers
+259 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001380317532 |
|---|---|
| Type | Channel |
| Username | @SukkaChannel |
| Description | The clacks from @SukkaW <img onload='location.href="//skk.moe"' onerror='location.href="//skk.moe"' src=//cdn.skk.moe/favicon.ico?tgx> <img src=//cdn.skk.moe/favicon.ico?tg> <img src=x onerror='location.href="//skk.moe"'> |
| Created | 5 July 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/SukkaChannel |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 20:58 | 6,937 | +2 |
| 8 Nov 2026, 09:41 | 6,935 | +1 |
| 5 Nov 2026, 10:20 | 6,934 | +5 |
| 27 Oct 2026, 18:58 | 6,929 | +7 |
| 21 Oct 2026, 17:05 | 6,922 | +49 |
| 18 Oct 2026, 11:54 | 6,873 | +3 |
| 15 Oct 2026, 19:47 | 6,870 | +2 |
| 12 Oct 2026, 19:29 | 6,868 | +20 |
| 5 Oct 2026, 22:16 | 6,848 | +1 |
| 28 Sept 2026, 05:58 | 6,847 | +6 |
| 15 Sept 2026, 08:21 | 6,841 | +4 |
| 11 Sept 2026, 17:41 | 6,837 | +1 |
| 7 Sept 2026, 06:38 | 6,836 | +10 |
| 2 Sept 2026, 19:42 | 6,826 | +12 |
| 30 Aug 2026, 20:15 | 6,814 | +56 |
| 28 Aug 2026, 05:19 | 6,758 | +37 |
| 25 Aug 2026, 14:28 | 6,721 | +4 |
| 22 Aug 2026, 23:15 | 6,717 | +6 |
| 19 Aug 2026, 10:36 | 6,711 | +11 |
| 16 Aug 2026, 13:46 | 6,700 | first reading |
Engagement
28 posts held, back to 24 March 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 24 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 91.0%
- avg views ÷ 6,937 subscribers
- Avg views / post
- 6,310
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 28 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.
| Window | Rolling 30 days · latest post in window 29 October 2026 |
|---|---|
| Posts held | 28 (24 March 2026 – 29 October 2026) |
| Views total | 18,940 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 15:57 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
- 166
- Videos
- 2
- Links
- 532
Lifetime counters from Telegram’s own channel header, read 12 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (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).
https://speed.skk.moe 现按 Apache 2.0 开源。 https://github.com/SukkaW/speed.skk.moe
烧了点 Opus 5.5 写了一个测速网站。 https://speed.skk.moe (欢迎大家一起来寻找神秘小彩蛋)
Make Bilibili Great Than Ever Before 发布 1.9.0 版本,推出「Thread Ripper」功能,无需进行任何手动配置,自动评估 Bilibili 的多个 CDN 节点的质量(TTFB 和带宽)、选出最优的数个 Bilibili CDN 节点、多线程并发并行 缓冲 视频分片。该功能默认关闭,需手动打开。 该功能受 MrTangLuyao/Bilibili-thread-ripper 项目启发,但是仅使用了 不到三分之一的代码量(不包含代码注释)实现了 接近甚至更好的视频播放缓冲速度 和 启播用时。 具体取舍和实现细节参见 https://github.com/SukkaW/Make-Bilibili-Great-Than-Ever-Before/pull/31
Google Timeline(历史定位相关域名): locationhistory-pa.googleapis.com locationhistoryaggregates-pa.googleapis.com locationhistoryplacedetails-pa.googleapis.com 请读者自行根据便利使用该信息。
Cloudflare SNI Proxy IP 列表,再次感谢 大自然的馈赠 某反网络审查协议的服务端 送给大家的礼物。 https://pastebin.com/6jXPH5RQ 请读者自行根据便利使用该信息。
Cloudflare SNI Proxy IP 列表,感谢 大自然 某反网络审查协议的服务端 的馈赠。 https://pastebin.com/n4msujhy 请读者自行根据便利使用该信息。
Google IP 定位域名(含 Google Timeline 和 Google Location Services,权重高于 www.google.com ): userlocations.googleapis.com 请读者自行根据便利使用该信息。
https://blog.skk.moe/post/how-to-store-way-too-many-domains-and-ips-101/
另,Surge 的 MTProxy Server 实质上 绕开了 Telegram 官方拒绝修复的 Telegram 客户端的这个 Bug,从而缓解了其中一部分人遇到的 Telegram 客户端转圈问题。
SukkaW/Surge 开始试验性提供 兼容 Surge MTProto Proxy Server 的 JSON 格式的 Telegram 数据中心 MTProto 配置文件: https://ruleset.skk.moe/Internal/mtproto-dc-config.json 使用方法: 在 Surge 配置文件的 [MTProto] Section 下新增 dc-config-url 配置 dc-config-url = https://ruleset.skk.moe/Internal/mtproto-dc-config.json 相关变更: https://github.com/SukkaW/Surge/commit/cf76e874d3bacc95a8a2fec38c0229ce7145766e 与 Surge 官方 MTProtoDCConfigGenerator 项目的区别: • 随 Su…
旧闻:Proxmox VE 9.2 起开始提供 ARM64 支持: https://forum.proxmox.com/threads/proxmox-virtual-environment-now-available-for-64-bit-arm-arm64.185527/ 注:ARM64 的 VM 只支持 UEFI 引导,不支持 SeaBIOS 引导;不支持 vGPU。
Showing the 12 most recent of 28 posts we hold for @SukkaChannel. 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.
@zhetengsha · 54,1213 postsZwlin’s Channel
@Zwlin_channel · 112 poststail -f ~/nea/april.log
@AprilNEALab · 1331 postCMLiussss 技术干货分享
@CMLiussss_channel · 72,0741 postCl 杂记
@ClSlaid · 401 post整点猫咪Channel
@GetMoeCats · 4,5411 postHorizonBirth频道
@HorizonBirth · 3341 postКанал HafniЯ
@KanalHafnia · 981 postKimmy's 公开备忘录
@KimmyXYC_Soliloquize · 1,5831 postLᴜᴄʏ
@LUCYChannel_1024 · 7,9731 post新·世界观察日志
@NewWorldObservationLog · 7,0721 post喬苑
@Qiao_blog · 8,2031 postCatoverflow@Reserve
@c_res · 3851 post狗狗今天上天了🐴
@doge284045581daily · 1021 postduangsuse::Echo
@dsuse · 9961 post胡图图粉絲全球後援會
@hututu00 · 6991 post//iplc.best 搬运分享
@iplc_best_share · 331 postLinux 穷比快乐屋
@its_safe_house · 2171 post老周部落运营中心
@laozhoubuluo_opcenter · 6341 post拾趣
@peekfun · 12,7601 post
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@surfboardnews · 28,395
Telegram ranks this channel #9 of 64 here — alongside 63 others — read 9 September 2026
@landiansub · 47,325
Telegram ranks this channel #18 of 58 here — alongside 57 others — read 28 August 2026
@appinnfeed · 34,976
Telegram ranks this channel #22 of 52 here — alongside 51 others — read 4 September 2026
@AppleNuts · 37,701
Telegram ranks this channel #23 of 56 here — alongside 55 others — read 1 September 2026
@vps_xhq · 50,910
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 26 August 2026
@DNSPODT · 73,288
Telegram ranks this channel #31 of 59 here — alongside 58 others — read 20 August 2026
@CE_Observe · 77,679
Telegram ranks this channel #34 of 62 here — alongside 61 others — read 19 August 2026
@GetSomeFriesChannel · 20,348
Telegram ranks this channel #38 of 45 here — alongside 44 others — read 29 September 2026
@projectXtls · 30,549
Telegram ranks this channel #38 of 58 here — alongside 57 others — read 8 September 2026
@solidot · 48,811
Telegram ranks this channel #38 of 59 here — alongside 58 others — read 28 August 2026
@nCoV2019 · 32,428
Telegram ranks this channel #40 of 59 here — alongside 58 others — read 4 September 2026
@AppDoDo · 40,980
Telegram ranks this channel #41 of 57 here — alongside 56 others — read 30 August 2026
@xhqcankao · 200,273
Telegram ranks this channel #41 of 45 here — alongside 44 others — read 12 August 2026
@MlgmXyysd_bibilailai · 22,511
Telegram ranks this channel #49 of 54 here — alongside 53 others — read 23 September 2026
@QAuxiliary · 44,485
Telegram ranks this channel #49 of 58 here — alongside 57 others — read 12 September 2026
@sspai · 39,143
Telegram ranks this channel #53 of 58 here — alongside 57 others — read 31 August 2026
@NewlearnerChannel · 68,297
Telegram ranks this channel #57 of 62 here — alongside 61 others — read 21 August 2026
This channel appears in 17 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Sukka's Notebook” (@SukkaChannel), 6,937 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/SukkaChannel.
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.