Telegram RegisterThe public register of Telegram
Telegram profile photo for Chunqiu/luna Detector

Channel

Chunqiu/luna Detector

@Suxiaomingpd

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

37,291subscribers

+15,419 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003663290215
TypeChannel
Username@Suxiaomingpd
DescriptionChunqiu/luna Detector Channel, welcome to join us! Exchange Group: https://t.me/chunqiudetector -------------------------- 春秋/luna检测频道,欢迎你的加入! 交流群组:https://t.me/chunqiudetector
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/Suxiaomingpd

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 61% 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

21,87237,29129,581.57 August 202618 November 2026
66 measurements spanning 103 days, net +15,419. 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 19,559–39,604 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
18 Nov 2026, 11:4737,291+491
15 Nov 2026, 07:0536,800+654
11 Nov 2026, 22:5436,146+328
9 Nov 2026, 21:5935,818+184
8 Nov 2026, 16:1935,634+291
7 Nov 2026, 08:4735,343+225
6 Nov 2026, 12:0035,118+119
5 Nov 2026, 10:1634,999+100
4 Nov 2026, 12:5734,899+145
3 Nov 2026, 13:1934,754+105
2 Nov 2026, 14:5934,649+114
1 Nov 2026, 16:3634,535+139
31 Oct 2026, 20:0734,396+222
30 Oct 2026, 19:5734,174+147
29 Oct 2026, 16:5634,027+145
28 Oct 2026, 16:3933,882+150
27 Oct 2026, 18:5733,732+161
26 Oct 2026, 15:5633,571+135
25 Oct 2026, 15:0533,436+223
24 Oct 2026, 16:1033,213first reading

Engagement

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

ERR · 30 days
55.4%
avg views ÷ 37,291 subscribers
Avg views / post
20,700
29 posts measured
Reaction rate
0.378%
reactions ÷ views · ER floor
Posts in window
30
of 176 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 13 November 2026
Posts held176 (11 June 2026 – 13 November 2026)
Views total599,500
Reactions total2,266
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 19:54 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
32
Videos
4
Links
49

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

Video runtime
25s
Average length
25s

Measured directly from 1 video 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

8,808 reactions across 171 posts, in 36 distinct kinds. The most used accounts for 68.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6,01968.3%
❤1,08912.4%
🤬2592.94%
🤣1792.03%
😡1661.88%
🤪1601.82%
🤓1381.57%
🤔1271.44%
👻1091.24%
😱770.874%
🍌660.749%
🔥600.681%
🐳530.602%
🎃440.5%
😍420.477%
😁330.375%
🌭280.318%
🎉260.295%
🌚230.261%
🗿140.159%
16 further kinds961.09%

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

Measured over the 176 most recent posts we hold, published 11 June 2026 to 13 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.

Telegram Stars

Stars received
44
across the posts below
Posts paid on
6
of 172 we hold a reading for · 3%
Most on one post
21
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Suxiaomingpd. 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 176 most recent posts we hold for this entry, published 11 June 2026 to 13 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.

Recent posts

Telegram’s own ‘edited’ marker: 14 of 30 posts held from the last 30 days (46.7%) 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).

13 Nov 2026, 17:04 UTC≈11,100 views101 reactionsread 18 November 2026

解决办法也很简单 单独维护一个持久化密钥状态数据库就行

👍91❤4🎃3🗿3

Signed 泷泽

13 Nov 2026, 16:29 UTC≈11,300 views100 reactions1 Starread 18 November 2026

TEE伪造(9)原理解释 前置 API≥31 Session 构造用 hidden-API 豁免拿 IKeystoreService/default getSecurityLevel(1) 取 TEE 实例构造 RawBridge raw 通道不可用则整项 UNAVAILABLE 不出结论 造键 raw.ec(null,2) 参数 EC P-256 KEY_SIZE=256 PURPOSE=SIGN DIGEST=SHA-256 NO_AUTH=true NOT_BEFORE NOT_AFTER 追加 USAGE_COUNT tag 805306773=0x30000000+405 即 Tag.USAGE_COUNT_LIMIT 值1 走 generateKey 生成失败 设备 KeyMint 不支持该 tag 则 UNAVAILABLE 不误报 双开 operation 同一把键连续两次 createOperation r…

👍94❤6

13 Nov 2026, 16:01 UTC≈11,300 views89 reactionsread 18 November 2026

We have added a "Network Connectivity Check" feature in version 3.3Fix. One particularly useful function within this is: "Number of devices using this key"—a figure representing how many devices share the same key. Here, "key" refers to the device certificate chain—such as local hardware keys, Google remote key configurations, or TEE-emulated certificate chains (via keybox). This feature allows you to determine whet…

👍84❤4😍1

13 Nov 2026, 16:00 UTC≈11,000 views100 reactionsread 18 November 2026
Photo

我们在3.3Fix版本就新增了“联网检查”功能 其中有一个“比较实用”的功能 使用此密钥的设备数:数字代表有多少设备 这里的“密钥”代指:设备证书链,本地硬件密钥/Google远程密钥配置/keybox模拟TEE证书链等。 这项功能可以用于查看本机使用的证书链是否存在多设备共用 这项功能仅搜集本机的证书链ID上传至服务器并添加到数据库,核对并统计数据得出“有多少设备是同一个“证书链ID” 当然只有使用过软件的设备才会纳入数据库统计。 数据统计仅供参考,设计初衷只是模仿软件厂商收集用户设备信息(这里指证书链ID)进行风控权重

👍91❤7😍2

13 Nov 2026, 15:25 UTC≈10,700 views114 reactionsread 18 November 2026

Update log Added 18 new consistency checks for TEE/RKP (Trusted Execution Environment / Real-time Kernel Protection) environments, covering categories "TEE Spoofing (4)" through "TEE Spoofing (13)" and "TEE Spoofing (16)" through "TEE Spoofing (23)." Threading and Concurrency Stability 1. Moved anonymous timeout-based tasks to a dedicated execution channel to prevent a single uninterruptible task from blocking oth…

👍104❤9🔥1

13 Nov 2026, 15:13 UTC≈10,900 views142 reactionsread 18 November 2026
File

更新日志 新增 - 新增 18 项 TEE / RKP 可信环境一致性检测,对应“TEE 伪造(4)”至“TEE 伪造(13)”及“TEE 伪造(16)”至“TEE 伪造(23)”。 ### 线程与并发稳定性 - 匿名超时任务改用独立执行通道,避免单个不可中断任务阻塞其他检测。 - 首次计算检测预算前同步加载历史数据,避免冷启动时使用不完整预算。 - 设备速度校准改为进程内同步单次执行,避免重复校准和并发覆盖。 - Observer 关闭时等待正在执行的回调结束,并阻止关闭后的迟到通知。 - HMA 检测只在主线程读取 Activity 状态,后台任务仅保留弱引用和 Application Context,降低页面销毁后的生命周期风险。 ### 其他修复 - 页面 Controller 状态恢复为主线程更新。 - 更新结果时同时校验底层状态,避免旧弹窗清除刚到达的新结果。 - 更新对象携带并打开自身下载地址,避免误用后续结果的…

👍128❤11🤔3

13 Nov 2026, 06:07 UTC≈12,000 views84 reactionsread 18 November 2026
File

OnePlus,rkp_key3 上一个快过期了,续上 #keybox

👍81❤3

9 Nov 2026, 06:59 UTC≈16,700 views48 reactionsread 18 November 2026
Photo

https://github.com/mingzun09/Chunqiu-Detector-Problem-solution 许可证变更提醒 License change reminder MIT→CC BY-NC-SA 4.0

👍43❤5

5 Nov 2026, 04:11 UTC≈23,100 views119 reactionsread 18 November 2026
Sticker

Sticker, posted without a caption

👍79❤21🤪10😍9

5 Nov 2026, 01:30 UTC≈21,700 views70 reactionsread 18 November 2026

检测到“风险应用”且带包名的解决教程 https://www.coolapk1s.com/feed/74811869 检测到“隐藏应用列表已生效/(2)”的解决教程 https://www.coolapk1s.com/feed/74811646

👍56❤13🔥1

3 Nov 2026, 07:03 UTC≈22,800 views57 reactionsread 18 November 2026
File

OnePlus,rkp_key2 #keybox

👍50❤6🥰1

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

Posts edited after publishing

@Suxiaomingpd edited 9 posts 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.

First edit seen
20 August 2026
Most recent edit
13 November 2026

Posts recorded as deleted after publishing

We recorded 7 posts on @Suxiaomingpd 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.

First seen missing
25 August 2026
Most recent seen missing
9 November 2026
Median time before seen missing
30 hours
Seen missing in the last 30 days
3

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.

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

“Chunqiu/luna Detector” (@Suxiaomingpd), 37,291 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/Suxiaomingpd.

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.