Channel
@zZPiglet
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,016subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001313119385 |
|---|---|
| Type | Channel |
| Username | @zZPiglet |
| Created | Between 1 March 2018 and 2 May 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/zZPiglet |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 13:52 | 1,016 | -1 |
| 6 Aug 2026, 21:00 | 1,017 | no change |
| 6 Aug 2026, 20:48 | 1,017 | first reading |
20 posts held, back to 2 May 2021 — 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 27 May 2023. An engagement rate over an empty window would be a number about nothing.
10 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5 | 50.0% | |
| ❤ | 4 | 40.0% | |
| 💩 | 1 | 10.0% |
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 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 10reactions 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 2 May 2021 to 27 May 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
【友情帮转】 欢迎加入Surge社区交流群，我们的群组不仅提供软件分享，更有专业的技术支持团队，解答你的任何疑问。我们定期进行技术分享，无论你是新手还是老手，都可以在这里学到有用的技术知识。 而且，我们强烈欢迎每个成员分享自己的使用经验，让我们的群组变得更加丰富多元。在这个平台上，你可以找到志同道合的朋友，共享研究科学上网啊的乐趣。 请点击链接加入我们，让我们共享网络的无限可能。期待你的加入！ @SurgeCommunity 注：请遵守相关法律法规，文明上网，理智使用代理软件。 另，可按需加入： Surge 官方频道：@SurgeTestFlightFeed Surge Pro 群： @SURGEPRO Surge TestFlight 更新自动推送频道（基于 Cloudflare Email Worker）： @SurgeTestFlightChangelog Surge Mac Changelog （v4/…
❤1👍1💩1
#微博通知 替换了 uid 接口，请测试及低调使用。 只保留了 card_type == 9 的信息，避免广告信息，暂不知是否会造成正常微博遗漏。按 VVebo 作者说法，微博索赔理由是“展示了一样的内容，但是屏蔽了广告和购买增值服务的入口”，而此次为修复 uid 接口进行的更新包含去掉返回数据的广告，所以随时删库跑路。 使用优先级建议：只使用“特别关注” > 使用“指定用户”的“用户 ID” > 使用“指定用户”的“用户昵称”
感谢 𝕩𝕚𝕟𝕚𝕒𝕟 提供的 macOS Surge 借助快捷指令快速开/关全局抓包应用场景，原快捷指令存在一些问题，如需使用请替换： https://www.icloud.com/shortcuts/256463a4e6b248f7a37191b7fe3c119e
👍1
由于谷歌快照被禁，现更换至 web.archive.org（感谢 @GetSomeFriesChannel），低调食用。 可控制参数修改为： useCache：是否在微信中用快照显示被封禁的链接 forceRedirect：是否在微信中进行强制重定向，允许的情况下可能出现循环重定向
希望有手的大佬能帮忙做一个： 【【自制】我做了个能动的 电 脑 配 件！【软核】-哔哩哔哩】 https://b23.tv/RtFAS9v
❤1👍1
微信最近封禁了（大）部分谷歌快照链接，建议更新脚本或使用 argument 参数 / BoxJs 开关关闭使用谷歌快照，最新脚本若无法在微信中 302 跳转谷歌快照则自动放弃，仅使用通知弹窗点击跳转至浏览器。
目前我已被覆盖到微信直接访问淘宝/支付宝链接，但失去了跳转功能，不知是否是微信刻意为之。 由于是直接访问，不会经过中转页面，故不会被 UnblockURLinWeChat 脚本识别。 如不想通过浏览器中转再进入淘宝/支付宝，可通过脚本来判断，如果 User-Agent 包含MicroMessenger 则发出通知跳转，可参考 UnblockURLinWeChat 脚本中 URL Schemes，或等微信再次开放直接跳转。 由于是直接访问，不会经过中转页面，通过脚本跳转的方式需要对淘宝/支付宝相关请求进行 MitM 或所有请求进行筛选，个人认为不太值，暂时不会做成脚本，如有需要可通过上述思路完成。 通过扫描二维码等方式访问淘宝/支付宝还会经过中转界面，依旧会被 UnblockURLinWeChat 脚本处理。 若有更好的思路或者方式进行跳转望不吝赐教。
❤1
https://mp.weixin.qq.com/s/7zxqex8DuuWj8cFfDhz2bw
https://www.bilibili.com/video/BV1WR4y147x4
摸鱼的时候也别忘了学习/复习知识呀： https://www.bilibili.com/video/BV1fq4y1g7hq 顺便 The Bit Player 里关于纠错码的直观解释还能帮助大家家庭和睦： How do you convey exactly what you wanna say to your spouse in a way that they understand? One way of communicating is repeating your message over and over again. But your partner may get annoyed with you. And another way is to shout louder. But that could also be misconstrued. So, what Shannon really said…
❤1👍1
来一起感受自己是废物 https://b23.tv/rfXFHs https://youtu.be/F29vrvUwqS4 https://github.com/peng-zhihui/Dummy-Robot 卷起来：https://b23.tv/WBhee8
摸🐟： 附带产品，一键快速开/关指定模块，适用于需要临时开启但又不想翻模块列表时。 [Script] moduleState = type=generic,timeout=10,script-path=https://raw.githubusercontent.com/zZPiglet/Task/master/asset/moduleState.js // use "module", "title", "icon", "color1" or "color2" in "argument": // moduleState = type=generic,timeout=10,script-path=https://raw.githubusercontent.com/zZPiglet/Task/master/asset/moduleState.js,argument=title=getCookies&module=TaskCook…
Showing the 12 most recent of 20 posts we hold for @zZPiglet. 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 — 824,037 of 1,151,006entries 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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“zZPiglet” (@zZPiglet), 1,016 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/zZPiglet.
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.