Keep the bars docked to the window out of the navigation bar (#885)
❤16🥰3

Channel
@NeoZygisk
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,171subscribers
+814 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003249146972 |
|---|---|
| Type | Channel |
| Username | @NeoZygisk |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/NeoZygisk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 18:56 | 2,171 | +789 |
| 11 Aug 2026, 07:06 | 1,382 | +22 |
| 8 Aug 2026, 00:11 | 1,360 | +3 |
| 7 Aug 2026, 22:20 | 1,357 | no change |
| 7 Aug 2026, 12:15 | 1,357 | first reading |
16 posts held, back to 14 April 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 16 (14 April 2026 – 7 August 2026) |
| Views total | 17,792 |
| Reactions total | 219 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 22:20 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.
482 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 51.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 247 | 51.2% | |
| 🔥 | 74 | 15.4% | |
| 👏 | 72 | 14.9% | |
| 🎉 | 45 | 9.34% | |
| 🥰 | 15 | 3.11% | |
| 👍 | 13 | 2.70% | |
| 😢 | 11 | 2.28% | |
| 😱 | 5 | 1.04% |
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 16 of the 16 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 482reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 14 April 2026 to 7 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.
Keep the bars docked to the window out of the navigation bar (#885)
❤16🥰3
Keep what saved instance state is restored through (#875) Fix the scope targets no filter can reveal and the routes that lead nowhere (#876) Bypass the notification flags on the Android 15 builds that carry them (#882)
🥰8❤7
Supports Android 17 QPR2 Beta2 Supports GrapheneOS 17 Fixed some known issues
👏15❤7
🎉 Vector 2.2 Release 🎉 Vector 2.2 is a hotfix for 2.1, and it brings libxposed API 102 — where a module can be swapped out without taking the process down with it. If you installed the manager as a separate app, uninstall it before updating: a 2.1 manager cannot talk to a 2.2 daemon. A parasitic manager needs nothing. 🩹 What 2.1 got wrong 🪝 No hooks in release builds. Modules loaded, and then nothing happened. R8…
❤28🎉11🥰2
🎉 Vector 2.1 Release 🎉 Vector 2.1 is the first release built on libxposed API 101, the newly published standard, and it ships with a manager rebuilt from scratch and support for the latest Android platforms. Where 2.0 was the definitive close of the API 100 era, 2.1 opens the next one: the framework, the daemon, and the manager have all moved to API 101. ⭐️ libxposed API 101 With API 101 now published, the ecosys…
❤15🥰1
Rewrite the manager in Compose Screenshots from the current branch, on a Pixel 6 running Android 17. You can download it through Github Actions.
🔥24❤8🎉7
Fix libxposed API 101 conformance (#794) Brings the framework in line with the API version master vendors, checked throughout with test modules that assert the documented behaviour and log pass/fail, on a Pixel 6 running Android 17. hookClassInitializer never worked: it aborted the process, and once that was fixed the hook still could not fire, because resolving <clinit> through JNI runs the initialiser during the lo…
❤20👏2🔥1
Fix daemon crash from the Android 17 IServiceConnection change (#784)
❤11👏2
3040-3046 Clarify libxposed modules loading process (#662) Ensure miscPath is initialized for system_server modules (#678) Implement missing auto_include feature in daemon (#681) Disable dex obfuscation for debug builds (#670) Fix original method invocation argument spreading (#701) Fix empty module list and blank README pages (#765) Fix dex2oat compatibility state constants drifting from AIDL Fix Re-optimize crash o…
❤31
libxposed API 102 has been released to the Maven Central Repository
❤19
终于要放假了,于是做了个三个月的计划。希望能好好照顾自己,随心所欲,把精力全部都放在提升自己上。 开源项目与公司管理 1. 处理掉所有的 issue 和 pull-request: Vector, NeoZygisk, TEESimulator。 2. 学习 Compose UI 设计,实现 Vector 管理器的设计。 3. 更新个人网站,可能还需要设计公司的商业网站。 基础技术加强 长时间依赖于 AI,不仅会失去编程的乐趣,还会丧失自信、消磨自己的独特性与价值。 1. C++ 复习:阅读 Professional C++ 2. Rust 复习(网页即可):The Rust programming language, Comprehensive Rust 3. 操作系统:Three Easy Pieces 4. 内核,虚拟机和嵌入开发:Linux Kernel Development, Hardware and soft…
👏50❤19🔥6
Unofficial https://github.com/JingMatrix/Vector/pull/750 DO more testing and get feedback🥳
🔥12👏3❤1
Showing the 12 most recent of 16 posts we hold for @NeoZygisk. 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.
Citation-graph rank — 86,123 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“JingMatrix Promotion” (@NeoZygisk), 2,171 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/NeoZygisk.
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.