8 measurements spanning 16 days, net +7. 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 1,404–1,415 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 00:16
1,413
-1
24 Aug 2026, 20:05
1,414
+2
21 Aug 2026, 10:26
1,412
+7
18 Aug 2026, 07:42
1,405
-1
15 Aug 2026, 10:54
1,406
-2
12 Aug 2026, 04:35
1,408
+2
11 Aug 2026, 19:00
1,406
no change
11 Aug 2026, 18:46
1,406
first reading
Engagement
20 posts held, back to 18 October 2025 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 April 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
155 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 71.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
110
71.0%
🥰
19
12.3%
👍
10
6.45%
👏
7
4.52%
🔥
5
3.23%
🌚
2
1.29%
👎
2
1.29%
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 19 of the 20 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 155reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 18 October 2025 to 3 April 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.
🎉 检测到新的 GitHub 推送!
Commit SHA: 43bd8437ec948857e1521aa2c09e0c3f6fc496a8
refactor: refine HookItemLoader process matching and clean up code
- Fix process matching logic in `HookItemLoader` by using bitwise AND to support multiple target processes.
- Update `FakeGroupOwner` description.
- Remove redundant logging in `QQMsfReqHandler`.
- Add `Debugger.kt` to `.gitignore`.
提交者 cwuom
查看详情
🎉 检测到新的 GitHub 推送!
Commit SHA: 7ac0367bbe90bbe122c1780449c6b26ae9e0e48b
fix(MiniAppCardDirectJumpApp): support more version and fix multiple hooks
支持更多的版本并修复出现多次的 hook
(cherry picked from commit 4e9616ba778cea3983769f768d4535e2106cf150)
提交者 Nacho
查看详情
🎉 检测到新的 GitHub 推送!
Commit SHA: b9ecfa7a85c58bf337c3f2c950ba598b3b4c2088
docs: add GNU GPL v3 license
Added the GNU General Public License version 3 to the project.
提交者 INTENTION
查看详情
🎉 检测到新的 GitHub 推送!
Commit SHA: 70f6cf3e1c6a95a3f1eb5925d0ebc6ef8c65ae32
fix(QSettingsInjector): not work on 9.2.30, fixes #29
修复了 9.2.30 及以上版本设置菜单不显示 ONO 的问题
提交者 Nacho
查看详情
👏4❤2
Showing the 12 most recent of 20 posts we hold for @ono_ci. 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@ono_ci named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@kyuharute named in 1 post, 12 August 2026 – 12 August 2026
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 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“ONO CI Builds” (@ono_ci), 1,413 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/ono_ci.
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.