DeepSeek v4 Pro 正式版 0813发布了
❤27👾5

Channel
@NPatch
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
18,350subscribers
+150 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002141231601 |
|---|---|
| Type | Channel |
| Username | @NPatch |
| Description | NPatch is a rootless xposed framework that injects dex and native libraries into the target APK to provide Xposed API support inside the app process. Website: npatch.nkbe.top |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/NPatch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 12:38 | 18,350 | +46 |
| 12 Aug 2026, 15:24 | 18,304 | +14 |
| 11 Aug 2026, 14:05 | 18,290 | +32 |
| 10 Aug 2026, 11:10 | 18,258 | +17 |
| 9 Aug 2026, 09:53 | 18,241 | +22 |
| 8 Aug 2026, 11:03 | 18,219 | +19 |
| 7 Aug 2026, 12:15 | 18,200 | first reading |
18 posts held, back to 1 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 17 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 18 (1 July 2026 – 12 August 2026) |
| Views total | 74,740 |
| Reactions total | 331 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 14:05 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.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
551 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 30.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 170 | 30.9% | |
| ❤ | 127 | 23.0% | |
| 🤯 | 87 | 15.8% | |
| 💅 | 47 | 8.53% | |
| 🔥 | 44 | 7.99% | |
| 😁 | 33 | 5.99% | |
| 👾 | 18 | 3.27% | |
| 🍌 | 5 | 0.907% | |
| 🤔 | 5 | 0.907% | |
| 😭 | 4 | 0.726% | |
| ⚡ | 3 | 0.544% | |
| 😍 | 3 | 0.544% | |
| 🥰 | 3 | 0.544% | |
| 🎉 | 1 | 0.181% | |
| 💯 | 1 | 0.181% |
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 17 of the 18 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 551reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 1 July 2026 to 12 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NPatch. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 18 most recent posts we hold for this entry, published 1 July 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
DeepSeek v4 Pro 正式版 0813发布了
❤27👾5
Posted without readable text
👍41❤13🔥2
GitHub Actions is down.~
😁33👾4❤1
NPatch Remote API 是给 Xposed 模块 App 使用的轻量 Android SDK。它让模块设置界面在本地修补模式下安全连接 NPatch Manager,共享 Remote Preferences 与 Remote Files。 NPatch Remote API is a small Android SDK for Xposed module companion apps. It lets a module settings UI securely connect to NPatch Manager in Local mode and share Remote Preferences and Remote Files.
❤15👍3🤯1
outputLog 功能升級: 大幅擴充日誌記錄範圍,全面涵蓋 Legacy XposedBridge.log、Modern API 的 XposedInterface.log/context.log、框架事件及未捕獲的 Java/Kotlin 崩潰;無論是主程序或 package:* 次程序,輸出的日誌均包含時間、程序 (PID)、執行緒 (TID)、級別、TAG 與完整堆疊。 同時,為確保文件與實際實作一致,本功能明確排除模組直接呼叫 android.util.Log 的 Logcat 訊息,以及 Native fatal signal 與系統級 Tombstone 日誌。 期望能為用戶與開發者帶來更清晰、更高效的使用體驗。
👍11❤3
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
诶? 什么时候出的 Opus 5,没见社群讨论啊
❤7
当出现该页面则表示您成功了
👍13
使用该油猴脚本打开 https://claude.ai/upgrade?from=menu 选择 Max Plan,支付资料选德国,支付方式选 SPEA,使用随机生成的德国 IBAN 卡号填入直接支付就行了 https://randomiban.co/#country=DE&iban 我使用这个网站生成,反正得多试 脚本已经失效了,自行找扩展插件用吧
👍14❤3
抓到马老师了🦀
💅47🍌5❤1
測試
🔥31👾9❤7🤔5⚡3😍3
我电脑屏幕炸了😢😢😢 修好了,花了900多元
🤯86👍10😭4🔥2🎉1
Signed Neko Beillc
Showing the 12 most recent of 18 posts we hold for @NPatch. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@NPatch edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 62,904 of 1,189,255entries 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.
Named by 2 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“NPatch” (@NPatch), 18,350 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/NPatch.
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.