Telegram RegisterThe public register of Telegram
Telegram profile photo for huamidev

Channel

huamidev

@huamidev

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

23,451subscribers

+1,744 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-1002409579184
TypeChannel
Username@huamidev
DescriptionGithub:huami1314 group: @huamichat repo: https://huami1314.github.io/devrepo/
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/huamidev

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

21,70723,45122,5797 August 2026 — 21,707 subscribers8 August 2026 — 21,727 subscribers9 August 2026 — 21,759 subscribers10 August 2026 — 21,798 subscribers11 August 2026 — 21,818 subscribers12 August 2026 — 21,839 subscribers13 August 2026 — 21,852 subscribers14 August 2026 — 22,092 subscribers16 August 2026 — 22,263 subscribers17 August 2026 — 22,326 subscribers18 August 2026 — 22,363 subscribers19 August 2026 — 22,388 subscribers20 August 2026 — 22,415 subscribers21 August 2026 — 22,448 subscribers23 August 2026 — 22,491 subscribers24 August 2026 — 22,570 subscribers25 August 2026 — 22,580 subscribers26 August 2026 — 22,611 subscribers27 August 2026 — 22,644 subscribers28 August 2026 — 22,655 subscribers29 August 2026 — 22,695 subscribers30 August 2026 — 22,755 subscribers31 August 2026 — 22,801 subscribers1 September 2026 — 22,845 subscribers2 September 2026 — 22,887 subscribers4 September 2026 — 22,963 subscribers6 September 2026 — 23,030 subscribers9 September 2026 — 23,095 subscribers11 September 2026 — 23,142 subscribers13 September 2026 — 23,164 subscribers15 September 2026 — 23,179 subscribers17 September 2026 — 23,212 subscribers19 September 2026 — 23,257 subscribers27 September 2026 — 23,451 subscribers7 August 202627 September 2026
34 measurements spanning 51 days, net +1,744. 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 21,445–23,713 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
27 Sept 2026, 01:2123,451+194
19 Sept 2026, 17:3723,257+45
17 Sept 2026, 06:1723,212+33
15 Sept 2026, 07:1523,179+15
13 Sept 2026, 15:5523,164+22
11 Sept 2026, 20:2123,142+47
9 Sept 2026, 11:5523,095+65
6 Sept 2026, 07:2023,030+67
4 Sept 2026, 00:2122,963+76
2 Sept 2026, 12:3422,887+42
1 Sept 2026, 10:5722,845+44
31 Aug 2026, 10:1222,801+46
30 Aug 2026, 12:3522,755+60
29 Aug 2026, 13:0322,695+40
28 Aug 2026, 13:3822,655+11
27 Aug 2026, 13:2322,644+33
26 Aug 2026, 14:4322,611+31
25 Aug 2026, 13:3322,580+10
24 Aug 2026, 14:4622,570+79
23 Aug 2026, 01:0422,491first reading

Engagement

91 posts held, back to 29 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 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.1%
avg views ÷ 23,451 subscribers
Avg views / post
5,170
38 posts measured
Reaction rate
0.326%
reactions ÷ views · ER floor
Posts in window
38
of 91 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 37 of 38 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 September 2026
Posts held91 (29 July 2026 – 25 September 2026)
Views total196,504
Reactions total632
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 01:26 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
246
Videos
26
Links
123

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

Video runtime
39s
Average length
13s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

1,457 reactions across 90 posts, in 4 distinct kinds. The most used accounts for 44.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤65044.6%
🤡56638.8%
👍20914.3%
🔥322.20%

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

Measured over the 91 most recent posts we hold, published 29 July 2026 to 25 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
4
of 91 we hold a reading for · 4%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @huamidev. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 91 most recent posts we hold for this entry, published 29 July 2026 to 25 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

25 Sept 2026, 07:32 UTC≈3,540 views16 reactionsread 27 September 2026

18PM 的 AVS60W 的头你们买的啥呀?什么价?

🤡13👍2❤1

Signed huami

24 Sept 2026, 13:47 UTC≈4,760 views27 reactionsread 27 September 2026
Video

这一段在致敬 Lumenic https://t.me/huamidev/2557

🤡20❤5👍2

Signed huami

24 Sept 2026, 08:32 UTC≈4,710 views24 reactionsread 27 September 2026

报了个数据安全的省赛玩玩🐶

👍13🤡10❤1

Signed huami

23 Sept 2026, 09:41 UTC≈5,490 views22 reactionsread 27 September 2026
Photo

现在的诈骗分子那么猖獗吗 发一条不够 一天内发那么多条

🤡20❤2

Signed huami

23 Sept 2026, 07:33 UTC≈5,160 views10 reactionsread 27 September 2026

接下来优化一版相册发送的 然后解决一些问题(现在可以说 然后就暂时不弄插件开发这些了 最近特别忙 抽空维护一下软件 暂时没有考虑其他计划了。

👍7❤3

Signed huami

22 Sept 2026, 11:57 UTC≈5,660 views28 reactionsread 27 September 2026

哦对了 以后都不会支持 iOS14 了 因为 Xcode27 强制选择 iOS15 了 手持 iOS14 的建议尽快换机吧。

🤡27❤1

Signed huami

22 Sept 2026, 11:56 UTC≈5,580 views21 reactionsread 27 September 2026
Photo

再也不把汽水音乐挂后台了

🤡19❤2

Signed huami

22 Sept 2026, 01:11 UTC≈5,630 views32 reactionsread 27 September 2026

Apple 回复我 48 小时内帮我解决 具体细节原因不告诉我。

🤡29❤2👍1

Signed huami

21 Sept 2026, 17:48 UTC≈5,810 views19 reactionsread 27 September 2026

Apple 沒有任何原因的把我的所有 App 的 build 全部標記為了已失效 目前開發團隊不在工作時間。。 無語死了

🤡18❤1

Signed huami

21 Sept 2026, 15:50 UTC≈6,000 views22 reactionsread 27 September 2026
File

新增系统原生相册选择 修复点击聊天记录偶尔进入礼物页面的问题 修复艾特提醒在迁移聊天记录后的逻辑问题 原生相册开启后在聊天页面将会以系统原生的 picker 展开选择 比微信原来的MediaPicker 好用超级多 *如果你想查看那张图片的大图 就点下边正中间的显示内容 预览完 右上角勾就行了

👍17❤5

Signed huami

21 Sept 2026, 14:15 UTC≈5,870 views13 reactionsread 27 September 2026

不知道大家升级 27 正式版有没有这个 bug 上滑切换到任务中心 然后向右滑 会往左回弹一下,但是 27.0 有漏洞 不想升级。。

🤡9❤4

Signed huami

21 Sept 2026, 10:42 UTC≈5,920 views19 reactionsread 27 September 2026
Photo

也是体验过几次学习通了。

🤡14❤3👍2

Signed huami

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

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 3 registered channels — 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.

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

“huamidev” (@huamidev), 23,451 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/huamidev.

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.