Channel
@muniunotify
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,486subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001536442916 |
|---|---|
| Type | Channel |
| Username | @muniunotify |
| Description | 官方域名：https://muniu.app 跳转域名： https://牧牛.com 备用域名： https://muniu.go26.one 聊天群组： @muniu2022 官网教程: https://world.crisp.help/ |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/muniunotify |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 12:48 | 4,486 | no change |
| 7 Aug 2026, 12:38 | 4,486 | first reading |
18 posts held, back to 1 April 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 5 pagesof 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 17 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
63 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 82.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 82.5% | |
| 👍 | 9 | 14.3% | |
| 👀 | 1 | 1.59% | |
| 😭 | 1 | 1.59% |
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 12 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 63reactions 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 1 April 2026 to 17 June 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.
牧牛云-公告 pinned «🌐 官方域名： https://muniu.app 🔄 跳转域名： https://牧牛.com 🛟 备用域名： https://muniu.go26.one ━━━━━━━━━━━━━━ 🚀 V-Ninja 定制协议更新公告 近期我们持续对 V-Ninja 客户端进行升级与优化，修复了多个已知问题，并新增多项实用功能（包括不限于）： ✅ 支持链式代理（Proxy Chain） ✅ 支持 Mihomo 内核替换 ✅ 支持 Windows 7 系统 ✅ 优化连接稳定性与兼容性 ✅ 提升客户端性能与使用体验 …»
🌐 官方域名： https://muniu.app 🔄 跳转域名： https://牧牛.com 🛟 备用域名： https://muniu.go26.one ━━━━━━━━━━━━━━ 🚀 V-Ninja 定制协议更新公告 近期我们持续对 V-Ninja 客户端进行升级与优化，修复了多个已知问题，并新增多项实用功能（包括不限于）： ✅ 支持链式代理（Proxy Chain） ✅ 支持 Mihomo 内核替换 ✅ 支持 Windows 7 系统 ✅ 优化连接稳定性与兼容性 ✅ 提升客户端性能与使用体验 📢 官方频道： https://t.me/ninja_ss2 建议所有用户升级至最新客户端，以获得最佳的稳定性、兼容性及功能支持。 V-Ninja 将持续迭代，为大家带来更强大、更稳定、更流畅的网络连接体验。
❤10
收集了今日的反馈，做了一些升级和优化。 欢迎 openclash 客户测试使用
❤4
原生 openclash + ninja 解决方案，含图文教程。 无需再安装繁琐问题多的 openclash ninja。 等一个反馈~~~
❤3
非常抱歉，近期给（部分ios/路由器）用户带来不好的体验，因为普通协议（ss/vless）的不可抗力，机器被不断的拔线，我们无法提供稳定的服务。 多方面考虑下，本月普通协议我们暂时只能提供海外入口或直连过度，但是我们会尽量优化海外连接效果。 预计下个月我们会从新增加中转为普通协议客户提供更好的服务。 补充： 1. ninja 客户不受到影响，并且随着ninja的使用量，我们不断的增加带宽。 2. vless 协议经过测试我们发现效果不理想，近期会马上上架 anytls 协议。
❤7
机房故障，预计晚一些恢复。
❤1😭1
已初步完成 VLESS 节点上线，请及时更新订阅以获取最新节点信息。 在当前特殊时期，我们暂时无法保证服务的完全稳定，但会尽最大努力保障整体可用性，感谢您的理解与支持。 为确保平台的长期发展与技术升级，我们将逐步下架 SS 协议，请提前做好相关准备。 除 iOS 及路由器用户外，建议优先使用官方 Ninja 客户端，以获得更稳定的使用体验。 注意： 旧版本 Clash for Windows 暂不支持 VLESS Reality 协议，请及时更换为较新的客户端，例如 Clash Verge（可在官网获取）。
❤6
最新问题： 目前正在上架 vless-reatily，预计明天完成大部分部署（但不会很多线路），导致 Clash for Windows 无法支持，请及时更换客户端为 Clash Verge。 目前 默认的 ss协议依然可以在 各种传统客户端上使用，比如路由器以及 shadowrocket，但是请注意，订阅只有10分钟有效期，更新后可以不用动了。 最后尽量使用我们的 ninja 协议，随着政策收紧，我们短时间内无法确认普通协议还可以坚持多久，目前都是在苟活。
👍8❤4
ios 外部测试名额已满，请暂时用 小火箭 shadowrocket，暂时还可以挺住。。。。
我们即将下线 ssr 协议，如果您依然无法使用 ninja 官方客户端，请去官网重新获取订阅。 晚一些我们会新增 vless-reality 协议作为今后的替代。
近期官方客服非常繁忙，请客户尽可能自己研究一下，目前常见问题： 1. 安卓/桌面版一键客户端登录会出现问题，请暂时使用订阅版本的 clash v-ninja。 2. 如果使用 clash v-ninja 在手机端无法显示订阅，可以尝试使用订阅转换（https://bianyuan.xyz/），记住客户端选择（ninja） 3. ios 如果订阅失败也可以尝试使用订阅转换。 4. 如果 ios 出现订阅成功但是无法使用，请暂时 用回小火箭，后续我们会寻求部分客户帮助来debug 解决这个问题。 5. openWrt 版本不少客户无法成功使用，已提供文档请尽可能跟着文档走。 http://牧牛.com/openclash-ninja.pdf 注意： 夜里我们将强制下架 ssr协议，ss协议暂时保留（工作日随时可能故障甚至不再支持），随后会新增 VLess-Reality 直连作为公共版本的主要协议。
❤2
我们预计在今天夜里下架对 ssr 协议的支持，目前的形似无法不允许这种协议随便的使用， ss可能还会继续保留，但是具体哪天故障我们无法确定，可能在本周就不行了。 下架 ss 的同一个时间我们新增直连节点 VLess-Reality 作为替代，并会在后续持续优化相关线路。 另外，ninja 在很多方便不受到影响，如果您可以使用 ninja 协议，就继续使用即可。
❤1
Showing the 12 most recent of 18 posts we hold for @muniunotify. 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“牧牛云-公告” (@muniunotify), 4,486 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/muniunotify.
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.