Channel
@Bncr_plugin_notify
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
891subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002490844602 |
|---|---|
| Type | Channel |
| Username | @Bncr_plugin_notify |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/Bncr_plugin_notify |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 23:52 | 891 | -1 |
| 20 Aug 2026, 21:34 | 892 | -2 |
| 14 Aug 2026, 12:58 | 894 | +3 |
| 7 Aug 2026, 20:04 | 891 | no change |
| 7 Aug 2026, 04:32 | 891 | first reading |
20 posts held, back to 23 March 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 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 20 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.
40 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 57.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 57.5% | |
| 👍 | 9 | 22.5% | |
| 🥰 | 7 | 17.5% | |
| 🔥 | 1 | 2.50% |
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 20 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 40reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 March 2026 to 5 July 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.
【插件更新】 订阅: xmo 插件: groupai.js 触发: 群内开启后全部消息进入命中规则触发 版本: 0.0.1 日志: 初版发布 提醒: 注意token消耗 相关指令： 群内开启回复： adminset thisgroupstart 群内关闭回复： adminset thisgroupstop 设置机器人id，用于大模型识别自己： adminset botid 机器人id 设置机器人昵称，用于大模型识别自己： adminset botname 机器人昵称 设置管理员id，用于大模型识别管理员： adminset adminid 管理员id 设置管理员昵称，用于大模型识别管理员： adminset adminname 管理员昵称 默静指定条数消息： adminset mute 输入默静条数用数字 解除默静： adminset unmute 清理上下文： admin…
【插件更新】 订阅: xmo 插件: openclawclient.js 触发: occ|oc 消息 描述: 适配 OpenClaw 2026.7.1-2 版本: 0.3.0 日志: 增加非管理员消息,门控交openclaw控制 详情: https://t.me/Bncr_plugin_notify/514 重要提示∶ 1、请先升级openclawclient的插件版本 0.6.1 升级成完整门控，后再升级无界的openclawclient插件，否则谁都能控制相对比较危险。 2、升级后群内默认只响应管理员消息，默认是public的agent，openclaw中配置public的agent，并设置此agent的最小必要权限。 3、public属于兜底agent未配置时会落到这个agent，故此agent必须进行最小化配置 4、自行做好权限分离，权限分离的起点是按agent进行限制，故支持按每个群聊单独配置agent以满足…
【适配器更新】 订阅: xmo 插件: qqBot.js 描述: qqBot适配器 版本: 0.0.8 日志: 增加入群退群事件|入群退群监控 说明: 目前机器人无需审核 新建即可拉群 拉群后给机器人设置群权限即可使用 备注: 因事件范围变更，此版本更新将触发权限重新探测
【适配器更新】 订阅: xmo 插件: tgBot.js 描述: tgBot适配器 版本: 1.4.7 日志: 新增引用RichApi发送的md格式解析成纯文本进行拼接
❤2
【适配器更新】 订阅: xmo 插件: tgBot.js 描述: tgBot适配器 版本: 1.4.1 日志: 适配同群粘性路由逻辑 粘性路由： 1、同群多bot自动指定第一个收到消息的bot接收和回复消息 2、绑定粘性后bncr重启前均由该bot负责群内回复 3、粘性bot发送失败时，尝试轮询bot重试，并重新确定粘性路由 4、不接受群内手动指定粘性路由bot
❤3
【适配器更新】 订阅: xmo 插件: tgBot.js 描述: tgBot适配器 版本: 1.4.0 日志: 按qqBot思路修改适配多bot支持
❤3
【适配器更新】 订阅: xmo 插件: qqBot.js 描述: qqBot适配器 版本: 0.0.3 日志: 多bot支持 说明: 目前机器人无需审核 新建即可拉群 拉群后给机器人设置群权限即可使用
❤1👍1
【适配器更新】 订阅: xmo 插件: qqBot.js 描述: qqBot适配器 版本: 0.0.1 日志: 初版发布 说明: 目前机器人无需审核 新建即可拉群 拉群后给机器人设置群权限即可使用 支持功能∶ ✅ 私聊 ✅ 群聊 ✅ 文本收发 ✅ 媒体收发(图片|视频|音频) ✅ md语法解析 ✅ 群内真@ ✅ 权限探测 ✅ 自动重连WS 不支持功能∶ ❌ 音乐卡片 ❌ 文件发送
❤1👍1
【适配器更新】 订阅: xmo 插件: tgBot.js 描述: tgBot适配器 版本: 1.3.9 日志: 优化bot_token可能泄露问题
【适配器更新】 订阅: xmo 插件: wxBot.js 描述: @tencent-weixin/openclaw-weixin 协议的微信适配器 版本: 0.0.6 日志: 优化已知问题
【插件更新】 订阅: xmo 插件: openclawclient.js 触发: occ|oc 消息 描述: 适配 OpenClaw 2026.6.10 版本: 0.2.5 日志: 增加单次对话模式 详情: https://t.me/Bncr_plugin_notify/514
【适配器更新】 订阅: xmo 插件: tgBot.js 描述: tgBot适配器 版本: 1.3.3 日志: 使用Rich API解析Markdown; 依赖变更:grammy
👍3❤1
Showing the 12 most recent of 20 posts we hold for @Bncr_plugin_notify. 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 — 319,387 of 1,626,884entries 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“无界插件更新公告” (@Bncr_plugin_notify), 891 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/Bncr_plugin_notify.
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.