Trusted CI #239: 6cfe23803e423675fd14a913b5fff9dafafc1b2b improve: group GrapheneOS JNI hook definitions (#381)
🫡31❤12🔥6👏1💋1

Channel
@rezygisk_ci
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,623subscribers
+404 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002786581440 |
|---|---|
| Type | Channel |
| Username | @rezygisk_ci |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/rezygisk_ci |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 23:00 | 8,623 | +47 |
| 12 Sept 2026, 20:02 | 8,576 | +22 |
| 8 Sept 2026, 20:01 | 8,554 | +48 |
| 3 Sept 2026, 10:43 | 8,506 | +43 |
| 31 Aug 2026, 04:47 | 8,463 | +75 |
| 28 Aug 2026, 14:34 | 8,388 | +47 |
| 25 Aug 2026, 03:53 | 8,341 | +10 |
| 22 Aug 2026, 02:38 | 8,331 | +6 |
| 19 Aug 2026, 03:35 | 8,325 | +15 |
| 16 Aug 2026, 07:07 | 8,310 | +19 |
| 12 Aug 2026, 19:04 | 8,291 | +33 |
| 9 Aug 2026, 19:02 | 8,258 | +25 |
| 6 Aug 2026, 23:16 | 8,233 | +14 |
| 6 Aug 2026, 03:15 | 8,219 | no change |
| 6 Aug 2026, 03:07 | 8,219 | first reading |
11 posts held, back to 25 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 22 pages 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 11 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.
546 reactions across 11 posts, in 17 distinct kinds. The most used accounts for 34.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 190 | 34.8% | |
| 🔥 | 147 | 26.9% | |
| 🤡 | 65 | 11.9% | |
| 👏 | 40 | 7.33% | |
| 🫡 | 32 | 5.86% | |
| 😱 | 22 | 4.03% | |
| 🖕 | 16 | 2.93% | |
| 🤯 | 10 | 1.83% | |
| 🤮 | 8 | 1.47% | |
| 🥰 | 6 | 1.10% | |
| ☃ | 2 | 0.366% | |
| 👎 | 2 | 0.366% | |
| 🤩 | 2 | 0.366% | |
| ⚡ | 1 | 0.183% | |
| 🆒 | 1 | 0.183% | |
| 💋 | 1 | 0.183% | |
| 😁 | 1 | 0.183% |
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 11 of the 11 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 546 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 25 July 2026 to 22 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.
Trusted CI #239: 6cfe23803e423675fd14a913b5fff9dafafc1b2b improve: group GrapheneOS JNI hook definitions (#381)
🫡31❤12🔥6👏1💋1
Trusted CI #238: e42886f48eb1c9eabcc94f08a3c3af0cdbffb99e fix: gid position in A17 nativeForkAndSpecialize signature
❤48🤡4☃2👎2👏2🤮1🆒1
Trusted CI #237: dd3d608cc6d5d674e5ad9e9a8974399bbf490a5c add: GrapheneOS 17 Zygote function signatures (#378)
❤23🤮3🥰3👏1
Trusted CI #236: 946708e0337166fb80b7a9523c6b8392e1fd78c5 add: Android 17 Zygote function signatures
😱22🔥9❤3🤮2👏1
Trusted CI #235: d47cf0e4d7586b7600917d22d919e83e06446eb4 improve: error handling to parse maps functions
🔥36❤8🤯3🤮2👏1
Trusted CI #234: 8cb7b0b1ad7cf5dfcf738d252c49e51b2ca8148a improve: refactor non-Tango and Tango injection (#377)
🔥37❤7🤡5👏2
Trusted CI #233: c37ab433f57e252cfe616487735e7a153822f335 remove: unused #includes
❤35🔥8🤡8🤯4👏2
Trusted CI #232: 7408a7d62843d61c59d76e7ce0c68dccb2e4e5d1 remove: duplicated connect error logs from daemon.c
🔥20🤡8❤6🤩2👏1
Trusted CI #230: cdc30d84feeedcf2f415ba49463619fe0c43efe6 improve: make art_method_size and entry_point_offset local
❤36🤡18🔥6👏1🥰1🫡1😁1
Trusted CI #229: d592cd9c9451187875cb480e2cdcb4d129761b95 improve: robustness, simplicity and correctness of socket_utils.c
🤡22🔥17❤10⚡1👏1
Trusted CI #227: 3a70c3aaa1c57e39d8daa99551816819217b360c update: license-related files
👏27🖕16🔥8🤯3❤2🥰2
Showing the 11 most recent of 11 posts we hold for @rezygisk_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.
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.
Named by 4 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“ReZygisk CIs” (@rezygisk_ci), 8,623 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/rezygisk_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.