Telegram RegisterThe public register of Telegram
Telegram profile photo for 查询精神状态

Channel

查询精神状态

@laike9m_ch

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

827subscribers

+2 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-1002107300983
TypeChannel
Username@laike9m_ch
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/laike9m_ch

Growth

8258318286 August 2026 — 825 subscribers6 August 2026 — 825 subscribers13 August 2026 — 829 subscribers20 August 2026 — 831 subscribers28 August 2026 — 828 subscribers11 September 2026 — 827 subscribers8276 August 202611 September 2026
6 measurements spanning 36 days, net +2. 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 824–832 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 20:16827-1
28 Aug 2026, 05:14828-3
20 Aug 2026, 08:12831+2
13 Aug 2026, 13:17829+4
6 Aug 2026, 15:18825no change
6 Aug 2026, 12:49825first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1155.0%
🫡420.0%
👍210.0%
😁210.0%
😢15.00%

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 20 reactions 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 2 July 2026 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 Aug 2026, 20:21 UTC164 viewsread 6 August 2026
Photo

Jeff Dean 把这篇离职推文删掉了,还好我眼疾手快🙄

1 Aug 2026, 19:17 UTC323 views2 reactionsread 6 August 2026

核心主旨与诉求 自动化 AI 研发的风险: 前沿 AI 公司正接近实现 AI 研发自动化。技术迭代速度正在急速加快,可能很快超出人类理解、掌控和确保安全的能力范围。 单方面放缓的困境: 在激烈的商业与国际竞争压力下,任何单一公司或国家都难以独自选择放慢脚步。目前全球缺乏主动控制和调节前沿进展节奏的工具。 联合诉求: 签署者请求美国政府支持一项国际合作努力,开发所需的技术与治理工具,以便有能力主动调节(Pace)自动化 AI 研发推进的速度,从而为建立安全防线、加强监管争取宝贵时间。 主要签署人代表 声明汇集了业内多位重量级学者与领袖(均以个人身份签署): John Schulman(Thinking Machines 首席科学家) Jakub Pachocki(OpenAI 首席科学家) Jared Kaplan(Anthropic 联合创始人兼 CSO) Shengjia Zhao(Meta AI 首席科学家)

😁2

29 Jul 2026, 01:13 UTC393 viewsread 6 August 2026

眼睛深度分级。有点意思 https://www.zhihu.com/question/2061014192115676470/answer/2064710694474462060

26 Jul 2026, 08:21 UTC354 views2 reactionsread 6 August 2026

https://fixupx.com/i/status/2081291779056468167

👍2

23 Jul 2026, 17:53 UTC≈1,820 viewsread 6 August 2026

好家伙 https://fixupx.com/OmniTools_AI/status/2080134663881019513

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“查询精神状态” (@laike9m_ch), 827 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/laike9m_ch.

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.