用了秒按头
Signed 明非 (回归版) 路

Channel
@piyanhui
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,969subscribers
-6 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002593530375 |
|---|---|
| Type | Channel |
| Username | @piyanhui |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/piyanhui |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 22:26 | 1,969 | -5 |
| 9 Aug 2026, 01:10 | 1,974 | -1 |
| 8 Aug 2026, 09:35 | 1,975 | first reading |
16 posts held, back to 4 August 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. It is computed over the 5 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 16 (4 August 2026 – 7 August 2026) |
| Views total | 2,999 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:35 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.
9 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 77.8% | |
| 🤮 | 2 | 22.2% |
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 5 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 9reactions 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 4 August 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.
用了秒按头
Signed 明非 (回归版) 路
WeChat-lm 微信小程序渗透测试工具箱 1. 一键扫描 wxapkg 文件,自动检测微信本地目录并列出所有小程序包 2. 智能解密 wxapkg,支持 V1/V2 两种加密方式,自动识别加密状态 3. 批量解包处理,多线程并发提取,显示实时进度与包类型 4. 小程序信息在线查询,输入 AppID 即可获取名称、主体、描述等详情 5. 敏感信息深度扫描,覆盖手机号、身份证、密钥、云服务令牌等 48 项规则 6. 签名算法自动分析,识别 MD5/SHA/HMAC/AES/RSA/SM4 等加密模式 7. Chaos VM 检测与提取,自动生成 sign_helper.js 辅助动态签名 8. JS 反混淆引擎,解码字符串表、Base64、Unicode、FromCharCode 等多层混淆 9. 隐藏逻辑检测,自动发现调试接口、后门代码、特权操作等可疑逻辑 10. mitmproxy 双代理套件一键生成,下游解密+上游重签名…
路明非频道突破222人现在 瓜分500积分直接在下方评论!!!!!! (截止到今晚12:00人人有份)
Signed 明非 (回归版) 路
@linuo_love 我孙子
Signed 明非 (回归版) 路
#小程序://粤居码丨粤治安/mVpfJpGDihcHxlq 有限制全国户籍地
❤2
#小程序://CBA官方球迷商店/D7FZzWVGAukB1ag 哎呀好麻烦你们自己去研究 这个包url = "https://logtake.weidian.com/h5collector/webcollect/3.0" 卡四 我的 -我的银行卡 来自于明非 @ggffhvh
File, posted without a caption
我是给
🤮2
Signed CD分享社区【技术分享】
微信小程序 兵证通 某些傻逼拿个破口子卖出甚至2u一天的p3 穷疯了一个个的 不能用在这里改密码 抓紧操死 "idPwd": encrypt("xjp@8964Dick"), "confirmPwd": encrypt("xjp@8964Dick"),
把车牌号和车主二要素丢评论底下你们就可以走了
自己抓一下登录过期了 渤海湾轮渡船票官网/nKhcBkb81ktdrVz
谁再说我是诈骗犯?就丢出证据来
❤2
Signed 陆柏言
Showing the 12 most recent of 16 posts we hold for @piyanhui. 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 — 562,667 of 1,340,412entries 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“屁眼汇” (@piyanhui), 1,969 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/piyanhui.
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.