Channel
@hkdiguo
On this record: Growth · Engagement · Posts · Citations · Cite this entry
248subscribers
+247 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003798241733 |
|---|---|
| Type | Channel |
| Username | @hkdiguo |
| Created | 4 September 2026 — measured — dated from the channel’s first post |
| First recorded | 10 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hkdiguo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 18:00 | 248 | +141 |
| 10 Sept 2026, 02:22 | 107 | no change |
| 9 Sept 2026, 13:59 | 107 | +106 |
| 6 Sept 2026, 12:17 | 1 | first reading |
5 posts held, back to 4 September 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 page of 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 9 September 2026 |
|---|---|
| Posts held | 5 (4 September 2026 – 9 September 2026) |
| Views total | 147 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 02:22 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.
整个流程下来没什么问题，但是如果又来了一个 X 协议(X over HTTP)，那么我们就得继续修改 SQL 注入模块以便支持这种 X 协议，但是扫描器中可不是只有 SQL 注入检测模块，还有其他同类模块，难道每加一个新协议我还得把所有检测模块都改一遍？ 上面的递归 decode 主要是为了解码某种格式的数据里面还有另外一种格式的数据，虽然看起来这种场景比较少见，但是仔细想一下 multipart 带着 json，json 里的字符串是另外一个 json 字符串，是不是又觉得这种情况也并不少见。 如果不谈扫描质量，只关注整体项目设计以及产品中使用到的猥琐技巧，那么其中最让我眼前一亮的当属 AWVS，接下来我将详细介绍一下我从 AWVS 中学习到的 PoC 分类 接单中，黑客业务，渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系： @dust515
赛题好难我好菜，其中还有一个是比赛结束复现出来的。这里写一下两道XSS的解题思路，还有一道是P神出的关于Scrapy爬虫框架的RCE，但是赛后听说是最新版本的Scrapy，等着看官方Wp的解法。 <script> var getUrlParam = function (name) { var reg = new RegExp("(^|&)" + name + "=([^&]*)(&|$)"); var r = unescape(window.location.search.substr(1)).match(reg); if (r != null) return r[2]; return null; } 重点在这个setElement函数，通过tag.substring(0, 1)创建一个dom事件，然后从cookie种取出attrs属性进行标签属性的赋值。接下来追一下cookie是怎么入库的 var tag = getUrlPa…
因为学的是安全相关专业，在网上下载东西非常谨慎，就算通过了杀毒软件扫描，但是也怕有后门或者其他东西，毕竟我也可以静态过掉杀软。 很多软件没有官网，各种下载站的东西真的是让人不放心。所以在下载某些软件后，只要不影响功能，基本都会用sandboxie来运行软件。如果不行，则放到虚拟机里。 所以我对沙箱最初的概念就是：sandboxie，它是一个轻量级虚拟机，软件的操作都不会影响真正的系统，包括文件、注册表等等资源，可以放肆地想干嘛干嘛。 重定向，顾名思义，就是重新指定方向，也就是说沙箱能够做到让沙箱内软件操作的文件、注册表等路径重定向到其他位置（沙箱指定位置），这样软件本来想操作的资源就不会被访问或者操作，保证资源的安全性。 接单中，黑客业务，渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系： @dust515
在Tokyo Western CTF2019之前，我对postscript处于基本0知识的状态。赛后，为了看懂官方给的poc，我大概花了一周的时间对着九百多页的官方文档学习了一下这门语言（它有关的学习资料太少了Orz），以及围绕它SAFER模式展开的攻防博弈。即使是现在，我对于postscript仍处于懵懂的愚昧状态。因此，如果下文中有任何不对的地方，希望大家理解并指出，感谢大佬们给与宝贵经验。 虽说postscript只是一种打印机语言，但是它在定义的时候就具备了比较强大的文件操作能力。关于postscript的文件操作符，在Adobe官方的文档中就有一页多的相关描述。 同时，ghostscript还支持在文件操作中采用pipe的方式来进程IO的操作，也就是我们可以利用file命令来实现任意的命令执行，当然这只在Unix系统中才生效。 核心的.locksafe方法主要做的事情是限制了userparams参数以及devic…
Channel created
Showing the 5 most recent of 5 posts we hold for @hkdiguo. 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.
Named by 1 registered channel — 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“黑客技术交流顾问” (@hkdiguo), 248 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hkdiguo.
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.