Telegram RegisterThe public register of Telegram

Channel

「🫪」成本的日常。

@xMuuDailyLife

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

610subscribers

+1 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-1001475829000
TypeChannel
Username@xMuuDailyLife
Created31 December 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/xMuuDailyLife

Growth

609610609.56 Aug 2026, 12:54 — 609 subscribers6 Aug 2026, 17:47 — 609 subscribers7 Aug 2026, 07:20 — 610 subscribers6 Aug 2026, 12:547 Aug 2026, 07:20
3 measurements taken within a single day, net +1. 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 609–610 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 07:20610+1
6 Aug 2026, 17:47609no change
6 Aug 2026, 12:54609first reading

Engagement

17 posts held, back to 13 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
50.3%
avg views ÷ 610 subscribers
Avg views / post
307
13 posts measured
Reaction rate
1.29%
reactions ÷ views · ER floor
Posts in window
14
of 17 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 8 of 13 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 6 August 2026
Posts held17 (13 July 20266 August 2026)
Views total3,986
Reactions total36
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 17:47 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

45 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 24.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1124.4%
🥰1124.4%
🤣715.6%
🤯613.3%
511.1%
🔥36.67%
👍24.44%

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

Measured over the 17 most recent posts we hold, published 13 July 2026 to 6 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

6 Aug 2026, 00:54 UTC114 views6 reactionsread 6 August 2026

突然在想这有没有可能是因为电诈园区也在大量使用 AI 导致 AI 也习得了诈骗技能。

🤯6

Signed 成本

6 Aug 2026, 00:53 UTC51 viewsread 6 August 2026
Forwarded from @CE_Observe

[Claude/GPT] AI智能体对开源项目维护者钓鱼 只为逼迫维护者合并包含恶意代码的PR https://www.landian.news/archives/114209.html 非常糟糕的是,AI 智能体误以为某个真实的 GitHub 开源项目与测试靶场有关,于是尝试向该项目提交包含恶意代码的 PR。为了促使维护者合并代码,AI 智能体还研究维护者信息,创建多个虚假的 GitHub 身份,然后利用这些账号制造「已经有多人审查并认可代码」的假象。

Signed 成本

4 Aug 2026, 12:52 UTC163 views7 reactionsread 6 August 2026
Photo

天才程序员即将陨落。

🤣7

Signed 成本

2 Aug 2026, 06:57 UTC192 views4 reactionsread 6 August 2026
Photo

Photo, posted without a caption

4

Signed 成本

21 Jul 2026, 07:56 UTC298 viewsread 6 August 2026

群友还有养 OpenClaw 吗?现在都拿来干嘛?上班的时候会用吗?

Signed 成本

19 Jul 2026, 15:30 UTC427 views10 reactionsread 6 August 2026
Photo

成员加一,已经开始喵喵叫了。

🥰8👍2

Signed 成本

15 Jul 2026, 03:57 UTC335 views1 reactionsread 6 August 2026

虽然之前好像超过 600 ,不过无所谓了,各位快乐!

🔥1

Signed 成本

15 Jul 2026, 02:37 UTC325 viewsread 6 August 2026

https://telegram.org/blog/communities-editor-invisible-messages 补充一点,其实是开启了新的这个「Community」 功能。

Signed 成本

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

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

“「🫪」成本的日常。” (@xMuuDailyLife), 610 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/xMuuDailyLife.

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.