Channel
@v2raya_notification
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
828subscribers
+5 since we began measuring on 17 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001384399931 |
|---|---|
| Type | Channel |
| Username | @v2raya_notification |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/v2raya_notification |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 20:41 | 828 | +2 |
| 18 Sept 2026, 23:41 | 826 | +3 |
| 17 Sept 2026, 03:22 | 823 | first reading |
20 posts held, back to 1 April 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 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 20 August 2026. An engagement rate over an empty window would be a number about nothing.
https://daeuniverse.pages.dev/ We have add rpm support to our self-host linux repository, follow the instruction to use it. NOTE: deb packages have all moved to /apt sub-folder, Debian series users should update your repo config with the instruction.
# Juicity install script, and our self-hosted debian repo has changed all of the software which can be worked as the server side(like juicity, v2ray) run with the nobody user. To make sure there server software can run properly, you need to make sure the nobody user has the permission to read the configuration files, and if you have SSL certificates, the nobody user also needs to have permission to read the SSL certi…
https://github.com/Glassyiris/honk A Rust-rewrites dae with Clash API
https://github.com/v2rayA/v2rayA/releases/tag/v2.4.4 中文： 从上一个正式版（v2.2.7.5）以来的破坏性更改： 1. 使用“杂交”的 v2raya_core，无需再单独安装 v2ray/xray。下游如果需要打包，需要初始化对应的 git 子模块，v2raya_core 是混合了 v2ray/xray 代码的成品，与本体分开，以 MPL 2.0 协议提供。 2. 数据库从 BoltDB 迁移至 SQLite 以解决不同 CPU 架构下可能的数据库文件不互通的问题，启动时程序会自动执行数据迁移，但建议用户在升级前备份旧的配置目录。同时，用户名和密码不会迁移，用户需要生成新的用户名与密码。 3. Tun 实现改用 v2rayA 组织下的 TinyTun 提供 4. 全面禁止 AllowInsecure 5. Windows 服务改用原生 Golang 实现 6. GUI…
https://github.com/v2rayA/v2rayA/releases/tag/v2.4.3
https://github.com/v2rayA/v2rayA/releases/tag/v2.4.1 需要留意的事项： 1. VLESS 协议的支持完整度可能被破坏。 2. 建议 Linux 用户迁移到 daeuniverse 下的 dae、daed 项目。v2rayA 未来的代码质量与更新都难有保证。 ——————————— Important Notes: 1. Full support for the VLESS protocol may be compromised. 2. Linux users are advised to migrate to the dae and daed projects under daeuniverse. The future code quality and updates for v2rayA are difficult to guarantee.
https://github.com/v2rayA/v2rayA/releases/tag/v2.4.0 破坏性更改： 1. 改用 v2rayA 自己的、一个杂交出来的核心，不再查找、启动 v2ray 或 xray。v2rayA 本体不再承担任何协议功能。 2. 默认 dat 资源的查找路径被替换成 XDG_DATA_DIRS/v2raya，例如 /usr/share/v2raya。 3. 前端能批量导出节点。 需要留意的事项： 1. VLESS 协议的支持完整度可能被破坏。 2. 建议 Linux 用户迁移到 daeuniverse 下的 dae、daed 项目。v2rayA 未来的代码质量与更新都难有保证。 ——————————— Breaking Changes: 1. v2rayA now uses its own hybridized core and no longer searches for or la…
https://github.com/v2rayA/v2rayA/releases/tag/v2.3.4 破坏性更改： 1. 抛弃了 sing-tun，改为用 rust 搭配 AI 实现的 tinytun，不过看起来更不稳定了，所以这次还是测试版。 2. 新的 DNS 设置前端，同时整个前端改为使用 vite 来构建，避免被锁在旧版本 nodejs。 3. 通过 @olicesx 的 outbound 分支支持 ss2022，同时 ss 与 trojan 协议的后端可以自行选择。 需要留意的事项： 1. Tun 其实完全没法子用，不管是以前引用 sing-tun 还是现在引用 tinytun 的二进制。 2. 建议 Linux 用户迁移到 daeuniverse 下的 dae、daed 项目。v2rayA 未来的代码质量与更新都难有保证。 ——————————— Breaking changes: 1. We have…
https://github.com/v2rayA/v2rayA/releases/tag/v2.3.1 自 2.2.7.5 版本以来的破坏性更改： 1、Windows 数据存储目录变更，通过 Windows 服务运行的 v2rayA 数据目录会保存到 C:\ProgramData\SYSTEM\v2rayA\ ，通过命令行调用管理员权限运行的 v2rayA 则是 C:\ProgramData\Administrator\v2rayA\ 目录，与此对应，安装程序也不会把数据保存在安装目录之下。 2、Windows 安装程序抛弃了 WinSW 服务外壳，现在 v2rayA 本身能直接作为 Windows 服务运行，因此，Windows 用户需要卸载旧版本、迁移数据库文件后再安装新版本。 3、由于 Shadowsocks 协议与 Trojan 协议完全迁移到了 daeuniverse/outbound 的实现，使用这两种类型节点的…
https://github.com/v2rayA/v2rayA/releases/tag/v2.3.0 If you have some fixes, please PR to main branch. Known issues: 1. Windows Installer: v2ray won't stop while v2rayA service stops. 2. Windows Installer: WinSW has been dropped, you may need to uninstall old installation before installing. 3. Shadowsocks 2022 might be broken. 4. C:\etc\v2raya might be created to store database and JSON but it's a mistake.
https://github.com/v2rayA/v2rayA/pull/1822 If you have some fixes, please PR to vibed_unstable branch.
https://github.com/v2fly/domain-list-community/issues/3055 Recent database updates of GeoSite may cause regular expression recognition errors. Users who are unable to start the program are advised to update to the latest version of the database.
Showing the 12 most recent of 20 posts we hold for @v2raya_notification. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“v2rayA - 通知频道” (@v2raya_notification), 828 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/v2raya_notification.
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.