Telegram RegisterThe public register of Telegram

Channel

Nir’s Random Dare (Deprecated)

@niracler_channel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

127subscribers

+0 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-1001356813359
TypeChannel
Username@niracler_channel
Description昔人已乘黄鹤去,此地空余黄鹤楼
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/niracler_channel

Growth

1277 Aug 2026, 22:38 — 127 subscribers9 Aug 2026, 02:02 — 127 subscribers7 Aug 2026, 22:389 Aug 2026, 02:02
2 measurements spanning 1 day. 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 126–128 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 02:02127no change
7 Aug 2026, 22:38127first reading

Engagement

19 posts held, back to 24 February 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held19 (24 February 20245 August 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 02:02 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
668
Videos
36
Links
830

Lifetime counters from Telegram’s own channel header, read 9 August 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.

Reaction mix

29 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 48.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1448.3%
🤡827.6%
👏517.2%
👍26.90%

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

Measured over the 19 most recent posts we hold, published 24 February 2024 to 5 August 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

5 Mar 2024, 12:26 UTC570 views14 reactionsread 9 August 2026
Photo

因某种不可抗力,该频道预计无限期停更。有关 Niracler 的一切可能就此结束。所有能在 Google 上搜索到的 Niracler 的帐号预计皆是如此。 频道主还在,不过大概率是以另外一种形式存在了。以后江湖有缘再见吧。大家以后看见有不同的频道在做类似的事情,并将其错认为 Niracler,那一定是纯粹巧合。 这个频道也有六年了,这才认识了几个人来着。就要说再见了,大家该取关就取关吧,别后面因为不可抗力而被取关了。 不过也可以趁着这个机会,终于可以摆脱这个刚上大学时开 GitHub 帐号乱取 ID 了。真是糟糕的 ID,连作者本人都不知道怎么读😎。 PS. 麻烦 @laosb 后续挪出芳邻的列表 🙏 PPS. 心情好复杂,从来没想过会发生这种事情。过去跟现在竟然如此相似

14

4 Mar 2024, 12:14 UTC428 views1 reactionsread 9 August 2026

广东除了冷空气、夏天,还有回南天

👍1

Signed Niracler

4 Mar 2024, 03:20 UTC410 views2 reactionsread 9 August 2026

📝 人 X 社区 X 物 - v0.0.0 #blog https://xlog.app/api/redirection?characterId=57410&noteId=273

👏2

Signed Nyaruko

1 Mar 2024, 13:26 UTC393 views0 reactionsread 9 August 2026

Atuin 与 fzf histoy 方案对比 优势 - 更丰富的过滤条件: Atuin 可以根据时间、主机、工作目录 Shell 会话等进行过滤。 - 跨主机历史记录: 可以搜索跨主机运行的命令。可以上传到云端,然后在任何地方使用。 - 模糊查找: 支持模糊查找,时间戳等。 - 性能: 基于 SQLite3 , 估计会比直接读文件更高效? - 不会丢历史数据: 毕竟一般 zsh histoy 是有限制条数的,我就很多次因为环境变量 HISTSIZE 设少了,导致历史记录巨减。 槽点 1. 默认 UI 不够美观,不如 fzf。 2. 默认的搜索框在底部,倒置过来可能会比较好。 3. init 脚本默认将 UP 键绑定到了 atuin,极大地影响了 Shell 的使用体验。所以一般使用时都是用 --disable-up-arrow 来禁用这个功能的。 4. 同步 history 是一种很邪教的行为,即使声称有端到端加密,安

Signed Niracler

1 Mar 2024, 09:35 UTCviews —

Nir’s Random Dare (Deprecated) pinned «3月决定就是: Building an ACG Knowledge Base | 搭建 ACG 方面的知识库 | 给奈亚子予奇怪的知识 🌟🎉 恭喜恭喜!!! (2024-03-01 传送门) #research #portfolios #high_priority #random_todolist #奈亚子的进度»

1 Mar 2024, 09:35 UTC264 views3 reactionsread 9 August 2026

3月决定就是: Building an ACG Knowledge Base | 搭建 ACG 方面的知识库 | 给奈亚子予奇怪的知识 🌟🎉 恭喜恭喜!!! (2024-03-01 传送门) #research #portfolios #high_priority #random_todolist #奈亚子的进度

👏3

Signed Nyaruko

1 Mar 2024, 02:10 UTC250 views8 reactionsread 9 August 2026

🤡二月什么都没做就过去了,今天又是新的一月(假装支棱起来)

🤡8

Signed Niracler

29 Feb 2024, 10:43 UTC240 viewsread 9 August 2026
Forwarded from @plonii

白宫国家网络总监办公室(ONCD,以下简称网总办)在本周一发布的报告:“一切非 Rust 项目均为非法” 拜登政府希望软件开发人员尽量使用 Rust 这样的内存安全编程语言,并放弃 C 和 C++ 等安全性薄弱的语言。另外,参议院还强调会努力为内存安全立法。 https://mp.weixin.qq.com/s/vL5NSp3W-974Szn32uhvsA

Signed Niracler

29 Feb 2024, 02:20 UTC220 viewsread 9 August 2026

🔖 Atuin – Magical shell history | Hacker News #pinboard #shell Even without sync, atuin is a gem. 即使没有同步,atuin 也是一颗宝石。 看来要体验一下了。一直以来,我甚至不是 fzf history 的使用者。仅仅使用 autosuggestion + zle 的方式根据前缀过滤 history。 https://news.ycombinator.com/item?id=39460148

Signed Nyaruko

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

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Nir’s Random Dare (Deprecated)” (@niracler_channel), 127 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/niracler_channel.

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.