Channel
@AquaDX_Updates
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
62subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002244249727 |
|---|---|
| Type | Channel |
| Username | @AquaDX_Updates |
| Created | 17 August 2024 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/AquaDX_Updates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 05:58 | 62 | +1 |
| 10 Aug 2026, 04:46 | 61 | no change |
| 8 Aug 2026, 20:00 | 61 | first reading |
18 posts held, back to 17 August 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 18 posts for this entry, the most recent from 30 July 2025. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 of the 18 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 17 August 2024 to 30 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
# 关于 AquaDX / MuNET 查询 Bot 的一些将来的变动 为了给将来推出的 Bot 2.0 做准备，以及匹配现在 MuNET 的迁移和普及，AquaDX / MuNET 最近将进行一些变更 ## 正在停止对 Telegram Bot 的更新 从 2025 年 8 月开始将不会对 Telegram Bot @AquaDXBot 进行更新，现有的功能仍然可以继续使用，将来也不会更新到 Bot 2.0（Bot 2.0 将不会进行多平台适配） ## 正在逐步停止对 QQ 官方 Bot 的支持 QQ 号为 3889289636 的 Bot 将会在 2025/8/15 停止接受新的绑定，原先已经绑定的各位可以继续使用。请各位群主和管理员尽量换成 QQ 号为 3087530651 的 Bot。 可以同时保留两个 Bot 并开启“融合模式”来同时享受按下 / 弹出菜单的便利以及 UserBot 的功能，只需要在同时拉了两个 …
❤1
经过一段时间的内测，我们认为 MuNET（也就是我们正在建设的新服务器）已经足够稳定，可以向大家开放使用了！因此，我们决定正式启动公测阶段。 现在，所有 AquaDX 中国用户——无论是个人玩家还是机台主——都可以无缝迁移到 MuNET，无需担心任何数据丢失。对于机台主，我们还提供了工具，可一键迁移曾在您机台上游玩的所有玩家数据。 迁移后，你将享受到更强大的 Net 支持和更顺畅的连接体验，未来也会有更多由凌莞开发的新功能陆续上线！ 虽然说 Net 上很多功能现在仍然处于施工状态，但是现在我们已经拥有 AquaDX 的几乎全部功能了，并且新玩家入坑也可以直接首选 MuNET 了 迁移方法及相关说明详见文档：https://docs.qq.com/aio/DRU9hUnVSS1dEZ09B?p=HfmUUHfpKeRSJDuD97fwAI
Bot 已加入分数表功能，触发方式：12 ?(分数|成绩)[图列]?表
好的现在 bot 已经更新了 1.50 的数据，请求 b50 之类的时候会自动根据账号的数据选择合适版本的定数和图标
已经修复了游戏名字超过八个字符时 UserAll 保存失败的问题
做了一个类似 AstroDX 的跳过 打完音符会出现
#AquaDXBot 修复了以下命令的异常 /search cranky /search trust /search 1726
Photo, posted without a caption
做了个 prism 皮肤
把 Bot 的 Web 内容架构从 @cloudflare/next-on-pages 迁移到了 @opennextjs/cloudflare 其中大多数时间都在修上游的 Bug
MaiChartManager 1.2.0 新增功能： - 将乐曲导出为 Maidata，可选是否包含 BGA - 重新设计的批量操作对话框，可以跨 Opt 选择乐曲，以及排序和筛选 - 增加了批量删除功能 - 增加了批量导出成新的 Opt 以及批量转换成 Maidata 的功能（赞助版功能） 优化和修复： - 修复了导致有多个谱面的乐曲无法导入的问题 - 重构了处理乐曲列表的模块 - 修复了无法记住一些选项的问题 AquaMai 的更新： - 重构了 SelectionDetail 的界面，现在字体大小会跟随屏幕大小了 - 增加了多语言功能，可以设置 Mod 内界面的语言 - ImmediateSave 将在保存过程中显示一个提示 - 增加了灰网时显示错误原因的功能 - 增加了窗口调节功能的开关，以及调整了选项位置（需要重新设置选项） - 增加了锁定帧率的功能，用于解决一些游戏问题 - 增加了自定义键位的功能 - 将隐藏…
以后这里改成 AquaDX / AquaMai / AquaDX Bot / MaiChartManager 的更新频道，这四个组件的更新日志之类都将在这里发布 AquaDX 为服务器程序，官方服务器 AquaDX.Net 跟随程序滚动更新 AquaMai 为 Sinmai 的拓展 Mod，采用滚动 + 跳跃更新，但是同步 MaiChartManager 更新版本号。MaiChartManager 每次更新时会携带发布时的 AquaMai 快照版本并可管理那个版本的设置。 大家可以通过 MaiChartManager 跳跃更新 AquaMai 或者通过 CI 频道获得滚动版本 但是 CI 版本可能会突然出现未通知的配置文件变化之类 * CI = 持续集成，每个 Commit 自动构建 AquaDX Bot 目前有 Telegram，QQ 自走和 QQ 官方三个平台，共用一份核心程序并同步滚动更新 MaiChartMan…
Showing the 12 most recent of 18 posts we hold for @AquaDX_Updates. 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 — 976,177 of 1,549,704entries 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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“AquaDX / AquaMai / AquaDX Bot / MaiChartManager Updates” (@AquaDX_Updates), 62 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/AquaDX_Updates.
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.