https://blog.skk.moe/post/how-to-store-way-too-many-domains-and-ips-101/

Channel
Sukka's Notebook
@SukkaChannel
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,836subscribers
+158 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 |
| Created | 5 July 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/SukkaChannel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 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 | +22 |
| 12 Aug 2026, 20:44 | 6,678 | +2 |
| 6 Aug 2026, 22:50 | 6,676 | -2 |
| 6 Aug 2026, 04:47 | 6,678 | first reading |
Engagement
20 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 11 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 57.7%
- avg views ÷ 6,836 subscribers
- Avg views / post
- 3,950
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 20 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 19 August 2026 |
|---|---|
| Posts held | 20 (24 March 2026 – 19 August 2026) |
| Views total | 11,840 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 05:17 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.
Recent posts
另,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。
https://blog.skk.moe/post/pppoe-half-bridge/
https://fxtwitter.com/isukkaw/status/2081101404865970280
Location Guard Ng 脚本 现已支持 为不同网站 设置不同的模式(真实位置、低噪音偏移、中等噪音偏移、高噪音偏移、虚假位置)。 https://location-guard-ng.skk.moe https://github.com/SukkaW/location-guard-ng
https://www.windy.com/-Hurricane-tracker/hurricanes/bavi?rainAccu,26.030,119.412,5,p:cities
推荐两家免费 DMARC 报告与管理平台 • Postmark 提供的每周汇报 https://dmarc.postmarkapp.com/ ,没有 Dashboard,甚至不需要注册,每周一 会发一封汇总邮件给总结上周的发件情况 • Valimail,DIgiCert 旗下公司,相比 Cloudflare 的 DMARC 只能看过去一周的发件情况,Valimail 可以免费看过往 3 个月的发件情况,无需信用卡,提供比 Cloudflare 更完整的数据维度
https://fxtwitter.com/isukkaw/status/2064835342252036402
https://fxtwitter.com/isukkaw/status/2064833545324146960
https://fxtwitter.com/isukkaw/status/2060023175799554089
Showing the 12 most recent of 20 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.
@Zwlin_channel · 112 postsAprilNEA's Notebook
@AprilNEALab · 1351 postCatoverflow@Reserve
@c_res · 3851 postCl 杂记
@ClSlaid · 391 postCMLiussss 技术干货分享
@CMLiussss_channel · 66,6621 post狗狗今天上天了🐴
@doge284045581daily · 1041 postduangsuse::Echo
@dsuse · 8591 post整点猫咪Channel
@GetMoeCats · 4,3671 postHorizonBirth频道
@HorizonBirth · 3361 post胡图图粉絲全球後援會
@hututu00 · 7171 post//iplc.best 搬运分享
@iplc_best_share · 341 postLinux 穷比快乐屋
@its_safe_house · 2191 postКанал HafniЯ
@KanalHafnia · 971 postKimmy's 公开备忘录
@KimmyXYC_Soliloquize · 1,5301 post老周部落运营中心
@laozhoubuluo_opcenter · 6181 postLᴜᴄʏ
@LUCYChannel_1024 · 6,9271 post新·世界观察日志
@NewWorldObservationLog · 6,9461 post拾趣
@peekfun · 12,9531 post喬苑
@Qiao_blog · 8,0661 post折腾啥
@zhetengsha · 48,8191 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.
@landiansub · 44,387
Telegram ranks this channel #18 of 58 here — alongside 57 others — read 28 August 2026
@appinnfeed · 33,028
Telegram ranks this channel #22 of 52 here — alongside 51 others — read 4 September 2026
@AppleNuts · 36,872
Telegram ranks this channel #23 of 56 here — alongside 55 others — read 1 September 2026
@vps_xhq · 49,417
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 26 August 2026
@DNSPODT · 71,457
Telegram ranks this channel #31 of 59 here — alongside 58 others — read 20 August 2026
@CE_Observe · 74,118
Telegram ranks this channel #34 of 62 here — alongside 61 others — read 19 August 2026
@projectXtls · 29,900
Telegram ranks this channel #38 of 58 here — alongside 57 others — read 8 September 2026
@solidot · 44,631
Telegram ranks this channel #38 of 59 here — alongside 58 others — read 28 August 2026
@nCoV2019 · 33,188
Telegram ranks this channel #40 of 59 here — alongside 58 others — read 4 September 2026
@AppDoDo · 40,358
Telegram ranks this channel #41 of 57 here — alongside 56 others — read 30 August 2026
@xhqcankao · 160,314
Telegram ranks this channel #41 of 45 here — alongside 44 others — read 12 August 2026
@sspai · 37,991
Telegram ranks this channel #53 of 58 here — alongside 57 others — read 31 August 2026
@NewlearnerChannel · 67,021
Telegram ranks this channel #57 of 62 here — alongside 61 others — read 21 August 2026
This channel appears in 13 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Sukka's Notebook” (@SukkaChannel), 6,836 subscribers as measured 7 September 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.