新增 iPhone Air 机型预设和日文 README。 新增西班牙语,现支持 9 种语言与地区设置。 修正一些文案的翻译错误以及混翻的问题。 其他常规的优化。 更多日志..... 点点 star 冲一冲! iOS 27 上使用 Safari 下载的文件可能不完整。 如果提示 IPA 损坏或无法解压,可重新下载几次;仍有问题时换用其他浏览器。 目前尚未确认是否由 Safari 或 iOS 本身导致。
👍20❤7🔥2
Signed huami

Channel
@huamidev
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
28,494subscribers
+6,787 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002409579184 |
|---|---|
| Type | Channel |
| Username | @huamidev |
| Description | Github:huami1314 group: @huamichat 自助解封:@UnbanlyBot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/huamidev |
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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 22:44 | 28,494 | +3,079 |
| 8 Nov 2026, 11:07 | 25,415 | +202 |
| 7 Nov 2026, 05:28 | 25,213 | +73 |
| 6 Nov 2026, 08:14 | 25,140 | +91 |
| 5 Nov 2026, 10:27 | 25,049 | +106 |
| 4 Nov 2026, 07:47 | 24,943 | +48 |
| 3 Nov 2026, 04:40 | 24,895 | +73 |
| 2 Nov 2026, 01:59 | 24,822 | +78 |
| 1 Nov 2026, 03:09 | 24,744 | +79 |
| 31 Oct 2026, 05:08 | 24,665 | +101 |
| 30 Oct 2026, 05:48 | 24,564 | +47 |
| 29 Oct 2026, 04:38 | 24,517 | +42 |
| 28 Oct 2026, 02:58 | 24,475 | +35 |
| 27 Oct 2026, 05:51 | 24,440 | +39 |
| 26 Oct 2026, 05:09 | 24,401 | +80 |
| 25 Oct 2026, 02:27 | 24,321 | +50 |
| 24 Oct 2026, 04:07 | 24,271 | +43 |
| 23 Oct 2026, 05:16 | 24,228 | +34 |
| 22 Oct 2026, 01:59 | 24,194 | +32 |
| 20 Oct 2026, 23:54 | 24,162 | first reading |
173 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 142 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 173 (29 July 2026 – 11 November 2026) |
| Views total | 589,500 |
| Reactions total | 1,887 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 05:16 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.
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Measured directly from 9 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.
3,812 reactions across 172 posts, in 4 distinct kinds. The most used accounts for 36.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 1,404 | 36.8% | |
| ❤ | 1,235 | 32.4% | |
| 👍 | 1,051 | 27.6% | |
| 🔥 | 122 | 3.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 172 of the 173 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 3,812 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 173 most recent posts we hold, published 29 July 2026 to 11 November 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.
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 173 most recent posts we hold for this entry, published 29 July 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 22 of 66 posts held from the last 30 days (33.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
新增 iPhone Air 机型预设和日文 README。 新增西班牙语,现支持 9 种语言与地区设置。 修正一些文案的翻译错误以及混翻的问题。 其他常规的优化。 更多日志..... 点点 star 冲一冲! iOS 27 上使用 Safari 下载的文件可能不完整。 如果提示 IPA 损坏或无法解压,可重新下载几次;仍有问题时换用其他浏览器。 目前尚未确认是否由 Safari 或 iOS 本身导致。
👍20❤7🔥2
Signed huami
https://github.com/huamidev/GestaltX/releases/tag/v1.0.4
👍71❤13🤡8
Signed huami
目前觀察來看 27.2.1 同樣受 worse_query 影響
👍35❤3🤡3
Signed huami
留念一下.... 害怕又给我封了 原账号还未进入申诉流程(根本进不去
🔥55👍15❤7
Signed huami
GestaltX 1.0.3 • 新增分享导入:在“文件”或其他 App 中分享 plist 到 GestaltX,核验后弹窗确认导入。 • 加强设备归属校验,拒绝不匹配或无法核验的文件;本机导出的文件可携带设备校验凭证。 • 优化 MG 控制,支持新增、修改、重命名和删除键值。 • 支持恢复已核验的本机 plist,恢复前自动备份,完成后请重启设备。 重签时请保留分享扩展,并为主应用和扩展配置同一个 App Group。 通过最底下按钮导出的 plist, 可以直接分享进软件还原 🐱临时仓库:huamidev/GestaltX
❤51👍12🔥8
Signed huami
oo
👍73❤9🤡3
Signed huami
LCSign · 1.4-6 ⚠️ 使用本地安装服务需更新 本次更新 新增 - 同一动态库同时匹配主程序与扩展时,导入可选择「通过 LoadControl」「通过共享库」「LoadControl + 单独注入扩展」。 优化 - 自动匹配共同加载的共享库,无可用目标时禁用对应选项。 - 注入方式随工作区保存,支持重新选择,并逐个显示实际加载方式。 修复 - 修复原包插件、多选及排序列表中的加载方式未翻译问题。 - 修复手选 LoadControl 或组合模式仍被默认设置覆盖的问题。 - 修复共享库注入的扩展路径解析问题,切换方式时清理旧注入位置。 - 更新本地安装域名证书。 ✍️ 点击安装
❤20👍7🤡1
Signed huami
我才发现 BundleID 里的 gestalt 打成了 gestult....
🤡40❤5👍1
Signed huami
GestaltX 1.0.2 • 修复预设停用逻辑:原本不存在的字段会被删除,原本存在的字段恢复原值和类型,不再统一写入 0。 • 首次没有备份时自动创建备份,并保留修改前的字段状态,重新打开 App 后仍可还原。 • 每个预设新增“还原”按钮,支持单独还原该项,保留其他尚未应用的修改。 • 新增“移除新增字段”,用于清理确认是后来添加的字段。 • 调整 NeoSpring 的加载与触发时机,修正回到前台时提前关闭注销页面的问题。 支持 iOS / iPadOS 27.x;iOS / iPadOS 26.x 不支持本机 MobileGestalt 访问。签名至少需要一个可用 App Group。 🐱临时仓库:huamidev/GestaltX
👍18❤12🤡5
Signed huami
如果你使用 Apple ID 签名,可以尝试通过 LiveContainer 来实现。
👍16❤2
Signed huami
GestaltX 1.0.1 • 新增独立的“地区代码”选项,支持美国、中国大陆、香港、台湾、日本和英国。 • 单独修改地区代码时,保留原有销售地区后缀。 • 修复地区代码与销售地区的组合设置,现在可以同时应用。 • 通常只需修改地区代码即可尝试启用 AI,无需更改销售地区。 - 之前修改过销售地区的用户,可以先恢复设备原本的销售地区。例如原本为国行 CH/A,可将销售地区选回“中国大陆”并应用,再按需修改地区代码。应用后请重启设备。 支持 iOS / iPadOS 27.x;iOS / iPadOS 26.x 不支持本机 MobileGestalt 访问。AI 可用性及验机结果因设备与系统而异。 🐱临时仓库:huamidev/GestaltX
❤35👍11
Signed huami
修改前 切记保存好自己的原始文件
👍9❤3
Signed huami
Showing the 12 most recent of 173 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@huamidev edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 22 posts on @huamidev as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Named by 9 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“huamidev” (@huamidev), 28,494 subscribers as measured 9 November 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.