📦 猫猫TProxy 更新 主要更新: • Go 辅助内核正常时优先使用 Go 加速 • Go 不可用时自动切回 Shell,不影响基础代理 • Go helper 更新到本地内置 0.3.2,体积降至约 2.56 MB • 初次安装优先使用本地包 • 更新优先从 Gitee 下载,失败再用本地包 • 只安装比设备当前版本更高的 helper • 不绑定固定版本、文件大小或 SHA256 • 安装后自动显示 Go helper 版本并点亮按钮 • helper 异常时显示“Shell模式” • Web 面板密码增加显示/隐藏按钮 • 取消 yq 固定指纹限制 • 优化冷启动恢复、启动快照和故障转移 BUG 反馈:@cuty_contact_bot 项目地址:欢迎 Star

Channel
Cuty的碎片空间
@cuty_github
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
28subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003908640095 |
|---|---|
| Type | Channel |
| Username | @cuty_github |
| Created | Between 1 April 2026 and 27 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/cuty_github |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:08 | 28 | no change |
| 13 Aug 2026, 00:48 | 28 | first reading |
Engagement
16 posts held, back to 27 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 261.6%
- avg views ÷ 28 subscribers
- Avg views / post
- 73.3
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 16 held
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 8 August 2026 |
|---|---|
| Posts held | 16 (27 April 2026 – 8 August 2026) |
| Views total | 293 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:48 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.
Reaction mix
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 of the 16 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 27 April 2026 to 8 August 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.
Recent posts
🚀 Clash Rule-Set v8(07.28)已发布 新增全局均衡 优化地区节点识别 增强 DNS、hosts 与嗅探兼容 优化规则源及自动校验 详细更新内容:点击此处
Go 语言重构版,兼容性更好 BUG 反馈:@cuty_contact_bot 项目地址:欢迎 Star
7.21优化:精简策略设置,规则统一由配置模板管理;重整网络规则、设备直连及故障修复分类;保留旧配置兼容,继续支持 iptables/ip6tables 的 legacy/nft 后端。 7.22更新:精简约 12.8% 冗余代码,修复潜在隐患并全面优化策略与订阅性能。 7.27更新:修复误判核心带来的 Tproxy 规则黑洞问题。 BUG反馈:@cuty_contact_bot 项目地址:欢迎 Star
新增 Crypto 加密货币分流组,使用独立图标与加密货币规则集。 Lite 版新增 PayPal 金融分流组。 Lite 版已补齐完整分流组,如有需要可以自行修改Yaml文件启用。 Wise 分流组调整为 PayPal 金融分流。 PayPal 现在覆盖 PayPal、Wise 及其他金融平台规则。 注意 原 Wise 策略组已移除;升级后请在客户端中重新选择 PayPal 分组的节点。 Crypto 可单独选择节点,不影响其他金融平台流量。
7.14更新:这一版本修了一下上传模板会出现Failed to fetch的问题,问题最少的版本👍 7.18更新:解决了更新订阅耗时很长以及控制API响应慢的问题,真正的问题最少的版本 BUG反馈:@cuty_contact_bot
❤1
Lite版分流展示 https://github.com/Chunlion/Clash_Rule-Set
Signed 𝙲𝚞𝚝𝚢
https://github.com/Chunlion/Clash_Rule-Set 新增 新增 家宽节点 策略组,同步到完整版与 Lite 版的 YAML / JS。 AI Services 优先选择 家宽节点,其次再走美区相关节点。 家宽节点 图标使用 home icon。 README 新增完整版与 Lite 版节点分组对比表,并补充 emoji 标识。 调整 家宽节点 放在欧洲分组下面、其他分组上面。 家宽节点可同时存在于对应地区分组和家宽分组。 家宽匹配仅按家宽关键词过滤,不再把美国节点作为家宽组回落。 README 中服务策略组、区域策略组说明已同步当前配置。
Signed 𝙲𝚞𝚝𝚢
TCP Peek + Splice / vpso-mux 实现原理 TCP Peek + Splice / vpso-mux 和 Nginx Stream 使用同一套 443 单入口配置。Web 域名、证书、Web 反代引擎后端、Web 白名单和 Xray SNI 分流记录都不需要另起一套;3x-ui 面板、订阅和 Xray 入站仍按本地监听填写。第一次使用时先运行 主菜单 [19 443 单入口管理中心] -> [16] 查看 TCP Peek + Splice 状态 / 8444 预检,确认 vpso-mux 能在 8444 启动并转发;再运行 [17] TCP Peek 分流规则校验。只有用户随后执行 [5] 切换到 TCP Peek + Splice 模式,公网 443 才会从 Nginx Stream 切到 vpso-mux。 vpso-mux 使用 MSG_PEEK 查看 TLS ClientHello 中的 SNI…
VPS-Optimize 的 443 端口复用已经做成完整单入口方案了。 公网只开放 443,脚本按 SNI 自动分流: panel.example.com -> Caddy -> 3x-ui 面板 sub.example.com -> Caddy -> 订阅服务 site.example.com -> Caddy -> 网站/反代 REALITY SNI -> Xray / 3x-ui REALITY 未知 SNI -> 默认 REALITY 后端 也就是说,不再让 3x-ui、Caddy、订阅工具、网站、REALITY 一起抢公网 443。 当前支持三种入口模式: Nginx Stream:默认稳定模式,基于 SNI 四层分流 TCP Peek + Splice:进阶模式,自研 vpso-mux,读取 ClientHello SNI,不消费首包,优先 splice 零拷贝转发,性能更好,对…
❤1
Cuty的碎片空间 pinned «新增TCP Peek + Splice 分流引擎 - 保留 nginx_stream 作为默认稳定 443 单入口引擎 - 新增 experimental tcp_peek 引擎设计 - 引入 vpso-mux 作为独立 TCP SNI 分流器 - 使用 MSG_PEEK 读取 TLS ClientHello,避免消费首包 - 按 SNI 分流到 Caddy 或 Xray 本地后端 - 支持按路由配置 IPv4/IPv6/CIDR 白名单 - 支持 splice 零拷贝转发,并在失败时回退到普通 copy…»
新增TCP Peek + Splice 分流引擎 - 保留 nginx_stream 作为默认稳定 443 单入口引擎 - 新增 experimental tcp_peek 引擎设计 - 引入 vpso-mux 作为独立 TCP SNI 分流器 - 使用 MSG_PEEK 读取 TLS ClientHello,避免消费首包 - 按 SNI 分流到 Caddy 或 Xray 本地后端 - 支持按路由配置 IPv4/IPv6/CIDR 白名单 - 支持 splice 零拷贝转发,并在失败时回退到普通 copy - 使用 8444 作为 vpso-mux 测试入口端口 - 保留 8443 作为 Caddy 本地 HTTPS 后端端口 - 保留 1443 作为 Xray/REALITY 本地后端端口 - 增加 dry-run、测试模式、端口占用检查和回滚设计 - 补充 openssl、curl --connect-to 和 REALI…
Showing the 12 most recent of 16 posts we hold for @cuty_github. 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
Citation-graph rank — 453,874 of 1,550,164entries 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.
Forward network
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.
Cite this entry
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Cuty的碎片空间” (@cuty_github), 28 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cuty_github.
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.