3 Jan 2026, 13:35 UTC159 viewsread 10 August 2026
敲，打算以后一个月更一次，写好的文章不会提前发出来。🍉
Channel
桃桃的应用空间
@HuTaoApplication
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
44subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002213298002 |
|---|---|
| Type | Channel |
| Username | @HuTaoApplication |
| Description | 传本频道是桃依在 telegarm 单独的应用空间 主要放信息技术相关的 Blog 与之前的个人 Blog 区分开来 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HuTaoApplication |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 16:01 | 44 | no change |
| 7 Aug 2026, 14:26 | 44 | first reading |
Engagement
16 posts held, back to 23 November 2024 — 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 16 posts for this entry, the most recent from 3 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 8
- Videos
- 1
- Links
- 22
Lifetime counters from Telegram’s own channel header, read 10 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.
Reaction mix
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 50.0% | |
| 🤣 | 1 | 50.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 3 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 2reactions 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 23 November 2024 to 3 January 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.
Recent posts
3 Jan 2026, 13:35 UTC142 viewsread 10 August 2026
今天突然好奇，用 Rust 编写 Windows 驱动咋样，看到例子[1]，实在有点炸裂。 在例子中，基本使用的是原始绑定层（raw bindings），直接暴露 C API，相当于在写 C 代码，只是用 Rust 语法。导致所有 WDF API 调用都需要 unsafe。一个简单的 Print 需要大量样板代码。写的时候你会发现非常难受。而且还抵消了 Rust 的内存安全优势。 相比隔壁 Linux 的 Rust 驱动支持更成熟，虽然说框架使用的是中间层作为安全抽象，依然逃不过因为 FFI 边界调用需要 unsafe ，但开发者实际用起来舒服很多。 // 驱动开发者使用的 API kernel::pr_info!("Driver loaded\n"); 相比之下 Windows 的 Rust 驱动支持，复杂度激增。 // 需要把字串符转换为 CString let string = CString::new("Driver l…
3 Jan 2026, 13:34 UTC95 viewsread 10 August 2026
下面是一个使用EPT技术实现对抗反调试的项目，其中著名的反作弊程序TX驱动也使用了这个技术。 EPT 全称叫 Extended Page Tables，是 Intel 平台上的虚拟化页表技术。其中 AMD 对应的是 NPT ，全称叫 Nested Page Table。 工作原理： 传统内存访问： 虚拟地址 → 物理地址 虚拟化环境（内存访问隔离）： 客户机虚拟地址 → 客户机物理地址(GPA) → 宿主机物理地址(HPA) 其中EPT主要负责客户机物理地址和宿主机物理地址之间转换。 这样一个特性，就很轻松实现。 通过 EPT/NPT 修改特定内存页的权限（如设为不可执行） 当目标代码执行时触发 VM-Exit Hypervisor 捕获并处理 并且隐蔽性极强，在 Ring 0 系统操作层无法查看其修改内容，具体来说无法通过读取 EPT 表去查看那些内存页设置的权限，更没办法查看宿主机物理地址，因为 Hypervisor 运行在…
31 Oct 2025, 00:11 UTC136 viewsread 10 August 2026
忘记把些文章转发公共频道了 其实很久之前写好了 （） 😋
31 Oct 2025, 00:11 UTC127 viewsread 10 August 2026
解锁/固化SSH小米路由器脚本 https://github.com/openwrt-xiaomi/xmir-patcher 连接 SSH 修改小米路由 RA Lifetine 修复 Android15 ipv6 网络不可达的问题 编辑文件 vim /etc/config/dhcp 找到 config dhcp 'lan' 添加 option ra_lifetime '1800' 感谢某位不愿意透露姓名的三月七群友提供的脚本 PS：这个脚本怎么把整个 Python 打包进仓库了 离谱
31 Oct 2025, 00:11 UTC97 viewsread 10 August 2026
Android 15+ 部分设备在某些路由器下遇到 IPv6 路由获取不正常 具体表现 设备上 WiFi 设置里能看到 IPv6 地址，但实际上测试（如 test-ipv6.com、mtr 工具）不通。 根本原因 Android 15 新增了对IPv6路由通告(RA)的要求，在Android 15 的源码 IpClient.java [1]，引入了一个新参数：DEFAULT_ACCEPT_RA_MIN_LFT（最小可接受前缀/路由终生期），默认值设为180秒，即接收到的路由RA生存时间，必须大于等于180秒才被接受。这意味着，如果路由器发送给客户端的 IPv6 RA（路由通告）报文的「Router Lifetime」字段小于180秒，中会直接丢弃该RA信息。 部分路由器，如小米、TP-Link部分型号会自行修改RA报文的参数，把 Router Lifetime、prefix lifetime 设置非常短。列如在小米的AX6…
31 Oct 2025, 00:09 UTC82 viewsread 10 August 2026
如何使用 Windbg 排除程序错误 今天从另一台电脑打开某大型动作软件，需要 InitSettingCN 才能运行，但是一启动就闪退了，服了，无奈之下打开 Windbg 进行调试。 以调试模式启动程序，选择 Start debugging → Launch executable 选择需要调试的文件。 这里是因为启动就崩溃，所以说直接点击 Go 让其执行下去即可，并观察输出。 (4bf0.2da8): CLR exception - code e0434f4d (first chance) (4bf0.2da8): CLR exception - code e0434f4d (first chance) (4bf0.2da8): CLR exception - code e0434f4d (!!! second chance !!!) "“System.Windows.Media.FontFamily”的类型初始值设定…
11 Jun 2025, 04:32 UTC326 views1 reactionsread 10 August 2026
Photo
本来不想发的，但是绷不住了，这也太变态了。获取系统信息偷偷上传，这代码一眼AI写的，太sh*t了。吓得我赶紧把服务器的 alist 清理了，现在有没有替代品都不知道。 Update：已经确认该公司劣迹斑斑，无法保证后续二进制可执行文件安全，建议跑路。 https://github.com/AlistGo/alist/issues/8649#issuecomment-2961048289 https://github.com/AlistGo/alist/pull/8633 https://www.v2ex.com/t/994143 https://www.v2ex.com/t/1138125
👍1
21 May 2025, 18:44 UTC259 viewsread 10 August 2026
Android 15+ 部分设备在某些路由器下遇到 IPv6 路由获取不正常 具体表现 设备上 WiFi 设置里能看到 IPv6 地址，但实际上测试（如 test-ipv6.com、mtr 工具）不通。 根本原因 Android 15 新增了对IPv6路由通告(RA)的要求，在Android 15 的源码 IpClient.java [1]，引入了一个新参数：CONFIG_ACCEPT_RA_MIN_LFT（最小可接受前缀/路由终生期），默认值设为180秒，即接收到的路由RA生存时间，必须大于等于180秒才被接受。这意味着，如果路由器发送给客户端的 IPv6 RA（路由通告）报文的「Router Lifetime」字段小于180秒，中会直接丢弃该RA信息。 部分路由器，如小米、TP-Link部分型号会自行修改RA报文的参数，把 Router Lifetime、prefix lifetime 设置非常短。列如在小米的AX60…
10 Apr 2025, 03:09 UTC293 viewsread 10 August 2026
前天 alist 直接被端，真的无话可说。GitHub 这种大型开源的社区，这种绝对是自动化封杀的，为了那 Tos 宁可先杀，先不管有没有错，最后遭殃的是焦虑的客户等待工单还有一天面对几万工单的客服。 根据 GitHub 透明度报告 在2024年至少有30K的账号和30K的项目被端，恢复完整访问权限的寥寥无几。what can I say。
5 Jan 2025, 04:48 UTC465 views0 reactionsread 10 August 2026
Nginx使用OQS提供的椭圆曲线 在网上和GPT找不到教程干脆写一个存档 前提：需要openssl版本大于3.0 编译 oqs-provider git clone https://github.com/open-quantum-safe/oqs-provider.git cd oqs-provider cmake -S . -B _build && cmake --build _build && cmake --install _build 配置openssl文件 vim /etc/ssl/openssl.cnf [openssl_init] providers = provider_sect [provider_sect] #加载OQS default = default_sect oqsprovider = …
3 Jan 2025, 16:05 UTC338 viewsread 10 August 2026
原贴 此地仅作为存档 https://tieba.baidu.com/p/9378338548 大家新年快乐！！#(太开心)新的一年从榜单开始吧！因为是昨晚熬夜查的，如果有错漏请大家多多包涵#(阴险)，帮忙指正一下谢谢~ 以下是注意事项： 1.计算投稿在1/1/2024 0:00 - 31/12/2024 23:59期间的作品。 2.投稿包括R18，R18率是全时间的。 3.这个排名的目的是向大家推荐各种令人喜爱的角色，希望大家都能抱着好奇的心情去了解不熟悉的角色和作品，说不定会有意外的惊喜哦~ 4.所用图片下方都标明了id和画师，如果有喜欢的请去Pixiv关注吧~ 5.本排行完全是个人统计，不保证数据准确性，排名也不代表角色或者作品人气，请勿用于黑吹婊，如需转载，请注明出处。 6.绿色部分为人工部分，不含AI作品。浅红色部分为AI作品数据。
Showing the 12 most recent of 16 posts we hold for @HuTaoApplication. 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.
Mentions
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.
Cite this entry
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.
“桃桃的应用空间” (@HuTaoApplication), 44 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/HuTaoApplication.
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.