Channel
@Ruhuhub
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001727711593 |
|---|---|
| Type | Channel |
| Username | @Ruhuhub |
| Description | 无所谓 自用%转载 联系@HKShamShuiPo_bot |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Ruhuhub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:18 | 10 | no change |
| 7 Aug 2026, 12:02 | 10 | first reading |
20 posts held, back to 20 September 2025 — 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.
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 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
多打多送2.0 https://h5.10099.com.cn/market/index?id=1938508178907029506&type=activity#/index 北京5GB https://h5.10099.com.cn/market/index?id=1777915934362402817&type=activity&shortCode=x3rdoe7fvt#/index 免费领取语音权益： 1、60分钟语音链接： https://h5.10099.com.cn/campaign/a/zy5vms8dll 2、30分钟语音链接： https://h5.10099.com.cn/campaign/a/mml8pynvef 3、15分钟语音链接： https://h5.10099.com.cn/campaign/a/tavgel2st8 免费领取专属流量： 1、5…
Signed 🐟 kunst
Tips：任务管理器的进程界面，按住 CTRL 可以实时暂停（松开恢复），此时你可以慢慢查看被暂停那一刻的进程列表而不必拼手速。 我™今天才知道 分享来自 秋风のとおり道 🍁 #Windows
Signed 🐟 kunst
We need more furry trash shows
Signed 🐟 kunst
Photo, posted without a caption
Signed 🐟 kunst
File, posted without a caption
Signed 🐟 kunst
🚀 OShin 新预览版 (Preview Build) 发布! 📦 版本: v16.7.1294(1294) 📝 更新说明: refactor(Framework): 迁移至 libxposed 并本地化 YukiHookAPI 主要变更： - **框架升级**：移除旧版 `de.robv.android.xposed` 依赖，全面接入现代化的 `io.github.libxposed` (API 101) 框架及服务。 - **依赖本地化**：取消 YukiHookAPI 的远程依赖，将 `yukihookapi-core`、`yukihookapi-stub` 和 `yukihookapi-ksp-xposed` 作为本地模块完整引入，并包含了对 libxposed 的深度适配与改造。 - **配置规范化**：清理 `AndroidManifest.xml` 和 `array.xml` 中的旧版 Xposed 元数据标…
Signed 🐟 kunst
🚀 OShin 新预览版 (Preview Build) 发布! 📦 版本: v16.7.1296(1296) 📝 更新说明: feat(Scope): 优化缺失作用域判断并增加未勾选视觉提示 主要变更： - **逻辑优化**：在 `HomeViewModel` 中新增应用安装状态检查与缓存，计算缺失作用域（`missingScopes`）时自动过滤掉未安装的应用。 - **状态同步**：在 `ModuleViewModel` 与 `AppRestartViewModel` 中新增并维护 `scopePackages` 状态流，通过 `moduleAppServices()` 注册并实时监听模块作用域的变更。 - **视觉增强**：在 `AppList` 和 `AppRestart` UI 组件中新增动态阴影颜色逻辑。对于未包含在作用域内的应用，其图标阴影将显示为橙色（`0xFFF59E0B`），从而提供明确的视觉警告与状态…
Signed 🐟 kunst
🚀 OShin 新预览版 (Preview Build) 发布! 📦 版本: v16.7.1295(1295) 📝 更新说明: feat(Module): 支持动态申请缺失的Xposed作用域 主要变更： - **作用域配置**：移除 `scope.list` 静态应用列表，将 `module.prop` 的 `staticScope` 设为 false，全面转向动态作用域模式。 - **状态检测与授权**：在 `HomeViewModel` 中新增基于 `FeatureCatalog` 的作用域对比逻辑，并调用 `YukiHookAPI` 向宿主框架发起动态授权请求。 - **界面与交互**：主页状态卡片新增作用域缺失的警告状态（黄色警报）及快捷操作入口；新增 `ScopeRequestDialog` 组件，以可视化列表展示待授权的应用信息。 - **构建脚本修正**：修复了 GitHub Actions 的重打包流程。 …
Signed 🐟 kunst
File, posted without a caption
Signed 🐟 kunst
🚀 OShin 新预览版 (Preview Build) 发布! 📦 版本: v16.7.1292(1292) 📝 更新说明: chore(Proguard): 添加 YukiHookAPI 混淆规则 🔗 查阅本次提交
Signed 🐟 kunst
https://telegra.ph/疑似银狐针对不同主题-Telegram-群组实施批量化社工投递的-Winos4ValleyRAT-木马活动分析-03-21 这篇文章是一份网络安全分析报告。简单来说它揭示了一个黑客团伙正在利用 Telegram 各类聊天群大批量散播电脑病毒。 具体的操作和攻击手法可以分为以下几个关键环节： 黑客首先会批量潜伏进不同主题的 Telegram 群组，比如影视资源群、软件分享群或者求职群。 他们会根据群里的聊天内容，把病毒文件伪装成大家感兴趣的东西。例如在影视群里，病毒就会被命名为“ 接口免费TV .zip ”或者类似的资源名字。 一旦有用户下载并点击了这些文件，完整的攻击过程就会在后台悄悄开始： 第一步是触发陷阱。用户点击的往往不是真实的资料，而是一个伪装的快捷方式文件。点击后它会调用系统自带的命令行工具，在后台偷偷运行一段隐藏指令去下载真实的病毒。 第二步是转移注意力。为了不让受害者起疑心，…
Signed 🐟 kunst
https://www.vxmusic.in/
Signed 🐟 kunst
Showing the 12 most recent of 20 posts we hold for @Ruhuhub. 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“TAW-8686” (@Ruhuhub), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Ruhuhub.
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.