storykoma.com 似乎已经有点能用的程度了

Channel
高先生的开发碎碎念(能更新一点点)
@mr_gao_it_words
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
664subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001202976193 |
|---|---|
| Type | Channel |
| Username | @mr_gao_it_words |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/mr_gao_it_words |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:27 | 664 | +14 |
| 6 Aug 2026, 17:31 | 650 | no change |
| 6 Aug 2026, 04:46 | 650 | first reading |
Engagement
20 posts held, back to 24 July 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 89.4%
- avg views ÷ 664 subscribers
- Avg views / post
- 594
- 20 posts measured
- Reaction rate
- 0.77%
- reactions ÷ views · ER floor
- Posts in window
- 20
- 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. It is computed over the 10 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (24 July 2026 – 4 August 2026) |
| Views total | 11,870 |
| Reactions total | 53 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 17:31 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.
Reaction mix
53 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 14 | 26.4% | |
| 😇 | 11 | 20.8% | |
| 😢 | 8 | 15.1% | |
| 🤣 | 8 | 15.1% | |
| 👍 | 6 | 11.3% | |
| 👏 | 2 | 3.77% | |
| 😱 | 2 | 3.77% | |
| 👀 | 1 | 1.89% | |
| 💯 | 1 | 1.89% |
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 10 of the 20 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 53reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 July 2026 to 4 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
好像也没很难啊 https://www.ether.fi/@0159488b
在AI 高速编码时代追求代码质量的难度简直堪比在银趴群找纯爱
😁4😢1
生产力大爆炸 https://zhuzhiliao.imsai.cc
我在让AI把一个代码仓库的风格 distill到另外一个代码仓库里面去
👍2
AI的超高生产力,终于有空把开源重新捡起来了,主要是现在AI在修修补补能力和文档能力真的是太吊打人类了 https://docs.rs/gotcha
👀1
dokku 好用
我现在不理解我的4c6g 的vps 怎么这么卡。 到底有没有好用的vps啊,太难了,难道要去用 cloudflare的docker了吗
Photo, posted without a caption
https://www.onorca.dev/
聊着聊着突然想起了什么,发现自己有时候说话是遵循着某一些pattern的。 之前跟ex喝完酒说“你对什么都上心,但唯独对你的这个男朋友不上心”。眼泪就流下来了。 哎,人生苦啊
😢7
草,梁圣良圣死了??!
Showing the 12 most recent of 20 posts we hold for @mr_gao_it_words. 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.
Citation-graph rank
Citation-graph rank — 197,484 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“高先生的开发碎碎念(能更新一点点)” (@mr_gao_it_words), 664 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mr_gao_it_words.
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.