Telegram RegisterThe public register of Telegram
Telegram profile photo for Nite的小窝

Channel

Nite的小窝

@nitechan

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

10,852subscribers

-212 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001231968979
TypeChannel
Username@nitechan
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live1 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/nitechan

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

10,85211,06410,9587 August 2026 — 11,064 subscribers8 August 2026 — 11,064 subscribers9 August 2026 — 11,058 subscribers10 August 2026 — 11,056 subscribers11 August 2026 — 11,053 subscribers12 August 2026 — 11,049 subscribers13 August 2026 — 11,050 subscribers14 August 2026 — 11,049 subscribers16 August 2026 — 11,042 subscribers17 August 2026 — 11,036 subscribers18 August 2026 — 11,032 subscribers19 August 2026 — 11,029 subscribers20 August 2026 — 11,028 subscribers21 August 2026 — 11,024 subscribers23 August 2026 — 11,019 subscribers24 August 2026 — 11,013 subscribers25 August 2026 — 11,008 subscribers27 August 2026 — 11,010 subscribers28 August 2026 — 11,003 subscribers31 August 2026 — 11,000 subscribers31 August 2026 — 10,997 subscribers2 September 2026 — 10,996 subscribers3 September 2026 — 10,995 subscribers4 September 2026 — 10,992 subscribers7 September 2026 — 10,986 subscribers10 September 2026 — 10,975 subscribers12 September 2026 — 10,969 subscribers14 September 2026 — 10,963 subscribers15 September 2026 — 10,961 subscribers17 September 2026 — 10,956 subscribers28 September 2026 — 10,934 subscribers5 October 2026 — 10,922 subscribers9 October 2026 — 10,898 subscribers13 October 2026 — 10,890 subscribers14 October 2026 — 10,889 subscribers18 October 2026 — 10,888 subscribers19 October 2026 — 10,885 subscribers22 October 2026 — 10,883 subscribers23 October 2026 — 10,879 subscribers25 October 2026 — 10,874 subscribers26 October 2026 — 10,873 subscribers27 October 2026 — 10,868 subscribers27 October 2026 — 10,870 subscribers29 October 2026 — 10,868 subscribers30 October 2026 — 10,863 subscribers31 October 2026 — 10,862 subscribers1 November 2026 — 10,852 subscribers7 August 20261 November 2026
47 measurements spanning 85 days, net -212. 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 10,820–11,096 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
1 Nov 2026, 00:4010,852-10
31 Oct 2026, 02:0910,862-1
30 Oct 2026, 02:1010,863-5
29 Oct 2026, 01:4010,868-2
27 Oct 2026, 23:1010,870+2
27 Oct 2026, 01:0710,868-5
26 Oct 2026, 03:5710,873-1
25 Oct 2026, 03:0010,874-5
23 Oct 2026, 08:5710,879-4
22 Oct 2026, 09:2810,883-2
19 Oct 2026, 23:0010,885-3
18 Oct 2026, 21:2810,888-1
14 Oct 2026, 22:1710,889-1
13 Oct 2026, 14:3110,890-8
9 Oct 2026, 14:5910,898-24
5 Oct 2026, 03:5610,922-12
28 Sept 2026, 13:3610,934-22
17 Sept 2026, 18:2010,956-5
15 Sept 2026, 16:5910,961-2
14 Sept 2026, 03:5510,963first reading

Engagement

33 posts held, back to 15 June 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 39 pages 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 33 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

238 reactions across 25 posts, in 19 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9439.5%
❤3313.9%
🥰208.40%
😢177.14%
💊135.46%
🆒125.04%
🌚114.62%
🤣104.20%
👻83.36%
💯52.10%
🌭41.68%
✍20.84%
🐳20.84%
😐20.84%
🏆10.42%
👀10.42%
👌10.42%
😨10.42%
😴10.42%

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

Measured over the 33 most recent posts we hold, published 15 June 2026 to 1 September 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

1 Sept 2026, 18:32 UTC606 views1 reactionsread 3 September 2026

把玩 Quadlet 这一年多,攒下的经验整理成了一个 skill:Quadlet Creator 🛠️(之前发过一次,今天重新整理了一下) 🤖 思路是让 AI Agent 干活:丢给它一条 docker run、一个 compose.yaml,甚至一个仓库地址,它帮你转成 Quadlet 配置。转之前会先把要人拍板的决策列清楚——rootless 还是 rootful、卷怎么挂、端口有没有冲突、凭据填什么,确认完才动手生成文件。env 文件、挂载配置、辅助脚本这些也一并保留。 🖥️ 我服务器上二十多个服务全是 podman+quadlet 跑的,这套流程踩过的坑基本都写进去了。想上手 podman+quadlet 或者正从 Docker 往这边迁的,直接用 👇 npx skills add https://git.nite07.com/nite/quadlet-creator-skill.git -g 📦 git.ni…

👍1

1 Sept 2026, 15:00 UTC688 viewsread 3 September 2026

🤔 刚看到 Charm 的 Hyper 还有个 $20/月的套餐,可能比 Ollama Pro 划算不少: 套餐每天刷新 250 Hypercredits。官网目前写着 1 Hypercredit = $0.05,按这个口径算,相当于每天 $12.50 的模型额度;如果每天都刷新,30 天理论上就是约 $375 的额度。 它主要面向编程 Agent,支持 DeepSeek、GLM、Kimi、MiniMax 等模型,也能接 Claude Code、Codex、OpenCode。 不过有几个问题还没搞清楚:官网不同页面对“每日刷新”还是“按月刷新”的说法不一致,而且实际模型价格也不完全和官方一致。 群里有人用过 Hyper 吗?这家服务稳定不稳定?$20 套餐到底是不是每天刷新 250 credits,也就是每天约 $12.50 的额度?值得长期用吗? 官网: https://hyper.charm.land/

1 Sept 2026, 14:36 UTC745 viewsread 3 September 2026

😤 Ollama 改计费了,时间点卡得真准 前脚刚续费一个月,后脚就官宣改版:Pro/Max/Team 全改成按 token 计费,Pro $20 送 $60 月度额度,Max $100 送 $300。单价倒是跟各家官方牌价持平,听着不亏,但 DeepSeek 错峰半价、GLM Flash 限时五折这些官方优惠一概没有。 再横一看隔壁 GOAT:$10 给 $70 额度,7 倍面值,43 个模型连闭源都能切。Ollama 新版唯一的卖点是取消了 5 小时/每周窗口,重爆发场景不用掐表,其余真挑不出优势。 好在老套餐原样保留,这个月先跑完,下个月的事下个月再说 😅

1 Sept 2026, 08:24 UTC821 views2 reactionsread 3 September 2026

🛒 帮 DMIT 带个货 自用的一台 VPS 来自 DMIT:洛杉矶 1核/2G/20G SSD,1.5TB 月流量,$9.99/月。 线路主打对国内优化:拿来做代理服务器很合适,hysteria2、vless 这些常用协议都能稳定跑,流量也给得足;做反向代理也不错,国内访问比套 Cloudflare CDN 的线路好不少。最近有购买打算的话走我的返利链接,佣金帮我抵点月费 👇 https://www.dmit.io/aff.php?aff=25536

👍2

29 Aug 2026, 03:20 UTC≈1,460 views2 reactionsread 3 September 2026

发现个抓取引擎 trawl 🕷 自托管的 FlareSolverr 替代品:Camoufox 底座,按官方说法 Cloudflare / Turnstile / hCaptcha 都能过。四层递进——明文直抓、复用缓存会话、浏览器现解、住宅代理兜底,普通站毫秒级。 比较有意思的是 MITM 代理模式:流量全走它的代理,过墙和后续请求同一指纹,对付 cookie 带不进去的高防站。 刚跑起来还没深度用,接下来打算拿它替换手头的 flaresolverr 试水,回头跟进实测反馈。 顺手写了个 Go 封装,开源了: 📦 github.com/germondai/trawl 📦 git.nite07.com/nite/go-trawl

❤1🐳1

28 Aug 2026, 15:34 UTC≈1,450 viewsread 3 September 2026

Glm 5.3 flash 的 agent 能力怎么样?能不能代替 deepseek-v4-flash-vision-exp 作为 hermes 的主模型?用过的来交流交流。

28 Aug 2026, 02:16 UTC≈1,810 views13 reactionsread 3 September 2026
Photo

Photo, posted without a caption

🤣10😢2🏆1

21 Aug 2026, 07:19 UTC≈2,690 views7 reactionsread 3 September 2026

翻到一部很神的番《女友成堆》全是神人也是神。看的时候千万别带脑子,太乐了。

👍5👀1🥰1

20 Aug 2026, 18:58 UTC≈2,810 views23 reactionsread 3 September 2026

🎮 游戏站找不到想要的资源?试试自己动手 新教程《游戏破解指南》上线了,Windows 下 Steam 游戏手动打补丁的完整流程: - Unsteam 方案 —— 支持在线联机 - GBE Fork 方案 —— 单机 / 局域网够用 - EOS 联机(Nemirtingas 模拟器)单独讲配置 资源站没有的游戏,按教程自己破,工具清单和常见坑都整理好了 👇 https://www.nite07.com/zh-cn/posts/game-crack-tutorial/

❤15👍7🐳1

11 Aug 2026, 12:31 UTC≈3,350 views2 reactionsread 3 September 2026

原来是 hermes 配置里个性设置的是 kawaii。不过我没有改过这个,之前怎么不是这样的 👀

✍2

11 Aug 2026, 08:29 UTC≈3,230 views12 reactionsread 3 September 2026
Photo

ds v4 flash 今天怎么那么喜欢发表情 🥸

🥰11❤1

9 Aug 2026, 05:12 UTC≈3,100 views8 reactionsread 3 September 2026

博客升级:支持 llms.txt,对 AI Agent 友好 🤖 小窝博客(www.nite07.com)现在支持 llms.txt 规范了: 📄 全站一个 /llms.txt 索引,中英双语列出所有文章 📝 每篇文章自动生成 .md 纯文本版,AI 可以直接抓取原文 🔗 以后让 AI 助手查我的文章,不用再啃 HTML 了 llms.txt 是 llmstxt.org 提出的规范,类似 robots.txt,但面向大语言模型。 博客:https://www.nite07.com llms.txt 直链:https://www.nite07.com/llms.txt

🥰8

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

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.

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

“Nite的小窝” (@nitechan), 10,852 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/nitechan.

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.