Telegram RegisterThe public register of Telegram
Telegram profile photo for 寒冰的小巢

Channel

寒冰的小巢

@hanbinggk

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

180subscribers

+1 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-1002320862554
TypeChannel
Username@hanbinggk
CreatedBetween 1 September 2024 and 24 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/hanbinggk

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

1791811807 August 2026 — 179 subscribers8 August 2026 — 179 subscribers24 August 2026 — 180 subscribers8 September 2026 — 181 subscribers2 October 2026 — 180 subscribers7 August 20262 October 2026
5 measurements spanning 56 days, net +1. 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 179–181 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 03:37180-1
8 Sept 2026, 23:18181+1
24 Aug 2026, 13:54180+1
8 Aug 2026, 13:15179no change
7 Aug 2026, 14:41179first reading

Engagement

18 posts held, back to 24 October 2024 — 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 18 posts for this entry, the most recent from 4 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍583.3%
💯116.7%

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

Measured over the 18 most recent posts we hold, published 24 October 2024 to 4 July 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

4 Jul 2026, 23:33 UTC185 viewsread 8 August 2026
Photo

chrome内核浏览器 如果碰到图片加载问题 看看F12报错信息 是不是因为fakeip导致的 如果是 请去chrome://flags/ 里关闭Local Network Access Checks

6 Apr 2026, 04:04 UTC980 views3 reactionsread 8 August 2026

鉴于各机场逐步使用自家dns解析自家节点域名,请各位自行在proxy-server-nameserver下的添加官方指定DNS来解析节点。或者通过nameserver-policy来进行DNS分流解析,可以设置域名指定DNS,具体格式可参考虚空终端教程。

👍3

29 Jan 2026, 17:48 UTC983 viewsread 8 August 2026
Photo

关于webrtc泄漏方面提示下 需要开启节点的udp功能,也就是zash等面板或者pc软件上显示节点有udp或者xudp字样 否则clash对于udp方面的会走direct(和你规则无关)。即stun这些或者dns方面会走直连。提示vless自建等用户,假如你的vps支持udp 。你自建导入发现没有显示udp 自己加个udp: true的参数或者在你的substore上udp选择强制开启。

21 Dec 2025, 16:32 UTC926 viewsread 8 August 2026

修复部分图标链接失效的问题,如果觉得麻烦自己把proxy-groups下面的策略组复制替换下就行。

11 Sept 2025, 17:08 UTC≈1,360 viewsread 8 August 2026

感谢逝水同学的建议 给B站部分CDN做了屏蔽优化播放,来源帖子来自 Lainbo's Blog的 感谢作者 来源帖子: https://lainbo.dev/bilibili-play-optimization?locale=zh

14 May 2025, 11:27 UTC≈1,650 viewsread 8 August 2026

修复了HK自动选择组的问题,(港前面多打了个空格)

21 Apr 2025, 16:22 UTC≈1,820 viewsread 8 August 2026

#clash 修复了下proxy-server-nameserver的dns,防止部分地区节点无法解析

21 Apr 2025, 09:37 UTC≈1,710 views2 reactionsread 8 August 2026

#clash OC支持smart策略 故添加了smart策略组版 记得更换成smart内核才可以使用,AI规则做了整合,把市面国外AI综合放一个组了,来源来自dler-io 包含openai claude copilot sora gemini deepmind grok meta ai等 具体规则可以查看链接的远程规则。

👍2

14 Apr 2025, 07:04 UTC≈1,570 viewsread 8 August 2026

#clash 规则 小吐槽:stash删除name policy设置,因为这东西经人提醒 geo这个参数一直不生效 下面clash配置文件给怪猎fakeipfilter加了防止联机问题,关于dns的解析换了个思路。应该说我不知为何geosite:geolocation-!cn这个参数在name policy里不生效 导致走的name sever做解析去了。但想了想反正我namepolicy geosite cn都搞了,其实 nameserver直接走国外dns就好了。所以就改了,规则修修补补的实在没法老找哪漏dns,就这么用这个DNS解析解决了。不影响CN方面的解析哈

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

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

“寒冰的小巢” (@hanbinggk), 180 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/hanbinggk.

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.