界面 - 优化深色使用纯黑背景的配色 - 部分加载改为内容骨架呼吸样式 网络测试 - 重做下载与上传速率显示效果(改为折线图) 其他 - 更改部分动效 #boxproxy | 赞助链接
🔥12❤1

Channel
@zero_o0
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
7,255subscribers
+938 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001758706301 |
|---|---|
| Type | Channel |
| Username | @zero_o0 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/zero_o0 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 08:56 | 7,255 | +48 |
| 5 Nov 2026, 23:49 | 7,207 | +42 |
| 2 Nov 2026, 20:45 | 7,165 | +22 |
| 30 Oct 2026, 23:45 | 7,143 | +28 |
| 28 Oct 2026, 04:37 | 7,115 | +28 |
| 25 Oct 2026, 04:21 | 7,087 | +31 |
| 21 Oct 2026, 20:20 | 7,056 | +25 |
| 18 Oct 2026, 05:26 | 7,031 | +53 |
| 15 Oct 2026, 05:20 | 6,978 | +24 |
| 12 Oct 2026, 12:09 | 6,954 | +66 |
| 5 Oct 2026, 21:21 | 6,888 | +55 |
| 28 Sept 2026, 12:17 | 6,833 | +92 |
| 18 Sept 2026, 10:01 | 6,741 | +38 |
| 14 Sept 2026, 13:01 | 6,703 | +29 |
| 11 Sept 2026, 07:36 | 6,674 | +30 |
| 6 Sept 2026, 01:55 | 6,644 | +30 |
| 2 Sept 2026, 05:34 | 6,614 | +23 |
| 30 Aug 2026, 02:37 | 6,591 | +40 |
| 27 Aug 2026, 11:23 | 6,551 | +28 |
| 24 Aug 2026, 20:57 | 6,523 | first reading |
43 posts held, back to 30 June 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 27 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 43 (30 June 2026 – 5 November 2026) |
| Views total | 37,110 |
| Reactions total | 180 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 17:38 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 11 November 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.
954 reactions across 41 posts, in 10 distinct kinds. The most used accounts for 43.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 410 | 43.0% | |
| ❤ | 343 | 36.0% | |
| 🥰 | 101 | 10.6% | |
| 🔥 | 37 | 3.88% | |
| 👏 | 35 | 3.67% | |
| ❤🔥 | 22 | 2.31% | |
| 👻 | 2 | 0.21% | |
| 👾 | 2 | 0.21% | |
| 🎉 | 1 | 0.105% | |
| 🗿 | 1 | 0.105% |
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 41 of the 43 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 954 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 30 June 2026 to 5 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @zero_o0. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 43 most recent posts we hold for this entry, published 30 June 2026 to 5 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 2 of 7 posts held from the last 30 days (28.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
界面 - 优化深色使用纯黑背景的配色 - 部分加载改为内容骨架呼吸样式 网络测试 - 重做下载与上传速率显示效果(改为折线图) 其他 - 更改部分动效 #boxproxy | 赞助链接
🔥12❤1
daeuniverse/honk 一个 linux 上的代理工具 已使用一周 感觉良好
👍20❤3
IP 质量 - 网络测试页新增 IP 质量标签页,可查询指定 IP 或当前出口 IP 面板链路 - 新增由本机发起冷连接的链路,展示 DNS、TCP、TLS、响应、首字节各阶段耗时 - 修复逻辑规则(OR/AND/NOT)无法匹配的问题,支持其中的规则集与地理数据条件 - 修正规则集按 domain、ipcidr 行为解析的匹配语义 界面 - 顶部搜索框统一描边样式,并设为透明背景 #boxproxy | 赞助链接
👍20🔥6❤4
禁用系统 IPv6 可能导致电话服务出现问题 解决办法有两个 1 apn 协议改为仅 IPv4 2 不使用禁用系统 IPv6
👍35
备份与恢复 - 支持按类别选择备份和恢复内容:应用设置、运行数据、用户脚本及核心程序 - 恢复时识别备份中实际包含的类别,显示可恢复的内容供选择 - 扩展备份范围,支持递归收集运行数据及 mihomo、sing-box 等核心程序 - 限制备份压缩文件大小为 1 GB,并加强归档校验与恢复过程保护 测速 - 重构测速引擎,支持选择 Apple、Cloudflare、Ookla 等测速来源,并记录测速来源与服务器信息 - 更新 Material 与 Miuix 两套测速 UI,调整测速数据与历史记录处理 运行文件与规则 - 改进运行文件浏览、编辑和导出流程,支持编辑草稿保留及配置校验 - 加强网络规则组编辑校验,减少无效条件或动作配置 - 优化规则提供商和地理数据的读取、缓存与并发处理 界面与稳定性 - 优化部分组件的状态稳定性及配置文件导出流程 #boxproxy | 赞助链接
❤22
网络匹配 - 支持设置多个组 - 每个组可设置独立的 AND/OR 条件树与按序执行的动作链 - 新增「取反」操作开关 面板 - 修正节点在 mihomo / sing-box 下的延迟测量 - 顶栏操作顺序调整 - 页签宽度按文字自适应,标签较长时不再挤压或裁切 - 优化节点根据提供商分组显示效果 - 支持单独对提供商分组进行延迟测量 界面 - 优化部分 UI 配色 #boxproxy | 赞助链接
👍17❤5❤🔥2
API 面板 - 新增「链路」页签,输入域名或 IP 查看实际生效的规则、规则集与最终出口(支持 mihomo 与 sing-box) - 策略延迟数据统一为单一来源,移除重复的别名解析与覆写映射 - 连接列表与节点延迟标记共用同一判定 日志 - 新增支持搜索 代码编辑器 - 校验失败时不再替换整个编辑区,保存照常执行,错误改由底栏提示 应用管理 - 关闭覆写开关时保留已选应用 其他 - 部分页面 UI 改善 - 对资源存储位置进行整理 #boxproxy | 赞助链接
❤🔥20❤6👍4🥰3
js 覆写脚本 - 对 mihomo / sing-box 支持覆写(并不通用) - 支持无配置,直接通过脚本写入启动配置 #boxproxy | 赞助链接
👍22❤6
- 优化测速逻辑 - 优化连通性检测逻辑 - 新增测速历史(最多 30 条记录,仅完整测速会被记录) #boxproxy | 赞助链接
👍23
- 网络测试位置改到工具页内 #boxproxy | 赞助链接
👍22❤3🥰1
网络测试 - 新增网络测试页面,分「连通性」与「网速」两个页签 连通性 - 新增 29 个平台的连通性检测,分 AI、社交、影音、工具四组 - 新增检测结果:延迟、状态与地区 网速 - 新增一键测速:延迟、抖动、下载、上传 - 新增实时速率曲线 - 新增测速节点信息:地区与 IP,点击可重新获取 - 新增测速说明,写明测速节点与测速方式 应用管理 - 关闭覆写开关时保留已选应用 界面 - 优化 Miuix 底栏首页图标 网络与规则 - 修复 CNIP 例外应用的 UDP 流量黑洞 - 改进 Clash 连接、日志的数据处理 其他 - 新增 coil-resvg 解析 svg 图标 (包体积增大) #boxproxy | 赞助链接
🥰25❤5👍2🔥2
应用管理 - 去掉核心模式,改为覆写应用开关 文件管理 - 导入与下载新增同名文件处理,可选覆盖或共存 #boxproxy | 赞助链接
🔥13👏5❤3
Showing the 12 most recent of 43 posts we hold for @zero_o0. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
We recorded 1 post on @zero_o0 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 registered channels — 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.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Re” (@zero_o0), 7,255 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/zero_o0.
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.