#Bettbox 链式代理可视化UI正在施工,诉求征集 起个头:单个家宽落地节点,想同时在多个订阅中生效 如果你有其他好想法,或者这一块比较困扰的点,说出来 讲诉求就行,不用考虑具体怎么做 (因为我会按自己的方式来做)
❤26

Channel
@appshub_channel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
6,899subscribers
+3,088 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003273148890 |
|---|---|
| Type | Channel |
| Username | @appshub_channel |
| Description | 不仅是 Bettbox 发布频道 群组 https://t.me/bettbox_chat |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/appshub_channel |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 15 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 12 Nov 2026, 23:07 | 6,899 | +99 |
| 8 Nov 2026, 17:57 | 6,800 | +93 |
| 5 Nov 2026, 08:49 | 6,707 | +316 |
| 2 Nov 2026, 02:27 | 6,391 | +180 |
| 30 Oct 2026, 03:28 | 6,211 | +168 |
| 27 Oct 2026, 04:19 | 6,043 | +165 |
| 24 Oct 2026, 08:05 | 5,878 | +299 |
| 20 Oct 2026, 22:05 | 5,579 | +164 |
| 17 Oct 2026, 22:36 | 5,415 | +191 |
| 14 Oct 2026, 20:49 | 5,224 | +177 |
| 11 Oct 2026, 03:20 | 5,047 | +130 |
| 5 Oct 2026, 03:37 | 4,917 | +148 |
| 26 Sept 2026, 07:19 | 4,769 | +255 |
| 17 Sept 2026, 12:37 | 4,514 | +87 |
| 13 Sept 2026, 05:56 | 4,427 | +69 |
| 9 Sept 2026, 14:01 | 4,358 | +74 |
| 3 Sept 2026, 20:01 | 4,284 | +57 |
| 31 Aug 2026, 10:58 | 4,227 | +44 |
| 28 Aug 2026, 17:32 | 4,183 | +54 |
| 25 Aug 2026, 12:19 | 4,129 | first reading |
32 posts held, back to 28 July 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 22 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 15 November 2026 |
|---|---|
| Posts held | 32 (28 July 2026 – 15 November 2026) |
| Views total | 103,490 |
| Reactions total | 703 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 07:41 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 16 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,122 reactions across 26 posts, in 20 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 461 | 41.1% | |
| 👍 | 226 | 20.1% | |
| 🔥 | 110 | 9.80% | |
| 😁 | 75 | 6.68% | |
| 🤯 | 60 | 5.35% | |
| ❤🔥 | 46 | 4.10% | |
| 🥰 | 31 | 2.76% | |
| 👏 | 29 | 2.58% | |
| 🤔 | 19 | 1.69% | |
| 💯 | 17 | 1.52% | |
| 🎉 | 15 | 1.34% | |
| 🤣 | 7 | 0.624% | |
| 🆒 | 6 | 0.535% | |
| 😱 | 6 | 0.535% | |
| 😇 | 4 | 0.357% | |
| 😢 | 4 | 0.357% | |
| ⚡ | 2 | 0.178% | |
| 🤓 | 2 | 0.178% | |
| 💔 | 1 | 0.089% | |
| 😘 | 1 | 0.089% |
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 26 of the 32 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 1,122 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 28 July 2026 to 15 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 @appshub_channel. 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 32 most recent posts we hold for this entry, published 28 July 2026 to 15 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: 7 of 19 posts held from the last 30 days (36.8%) 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).
#Bettbox 链式代理可视化UI正在施工,诉求征集 起个头:单个家宽落地节点,想同时在多个订阅中生效 如果你有其他好想法,或者这一块比较困扰的点,说出来 讲诉求就行,不用考虑具体怎么做 (因为我会按自己的方式来做)
❤26
关于Bettbox Android端报毒简单声明 https://github.com/appshubcc/Bettbox/issues/618 原本群里这种信息我们是直接忽略的,但是既然越来越多人提起,还是统一回复一下以及说一下接下来的应对方案 1.Bettbox所有源码100%公开,因为作者的洁癖甚至连崩溃上传服务都已完整清理,同时也无任何私有域名和服务(官网域名appshub.cc一直处于吃灰未启用状态,ip-api使用的是公开第三方免费服务),当前通过且仅通过github actions进行透明编译,并发布最终release,你可以完整看到源码并自行复现这里的每一步操作。同时,流程是经过Signpath开源基金会人工审核的,Readme已经提到了这一点,安全性无须担心 2.关于国产安全管家的云端拦截和误报,属于是意料之中,这里并没什么好解释的 (参考原Fork项目FlClash,因为影响力过大,近期直接进入了统一…
❤60👍8
Bettbox 托管模式高级玩法 - 接频道上条,脚本源码支持查看和导出,针对高级用户已同步开放了完全的自定义编辑,可以通过长按卡片来进入编辑页面(实验性支持) - 托管模式和脚本属于客户端附加功能,对于有足够动手能力的群友,官方代理集Providers是更为推荐的通用方案(当前订阅卡片已完整支持Providers流量信息显示),折腾和手写配置还是有很多乐趣 - 注意:虽然你也可以编辑内置脚本来完整实现自己的更加个性DNS或路由规则配置,但是涉及相关功能函数命名时需要慎重,这可能会破坏已有的内置逻辑,当使用AI进行修改时,需要进行严格约束,如果遇到问题,可通过编辑页面右上角的重置按钮来恢复初始状态 - 最后,托管模式指定外部脚本(可以实现非一键分流以外的核心功能)计划在后续的版本支持,另外,你可以主动调整脚本顶部version至较高的版本号,来避免软件升级后内置编辑后的脚本被覆盖 PS:11.…
❤30👍6🔥2
Bettbox 托管模式介绍 - 托管模式是 Bettbox 内置的基于脚本引擎的配置重写方案,可实现单订阅一键优化,或多订阅合并优化,最早起源于愚人节频道发布的一条动态,学名:全托管分流模式 - 核心特性:通过自动清洗节点、完整保留中转类机场的私有DNS、智能按地区归类、更完善的DNS/路由规则、完整的自定义分流策略组等等,从而实现真正的开箱即用和多订阅管理 - 原脚本来自 PR#517 ❤️再次致谢AIsouler ,作为订阅合并的内置处理方案,我将其同时做为托管模式的基准脚本,保留了主要逻辑和更多人使用习惯的同时,重新适配了一键自定义分流以及配合Bett-rules已有完善的DNS/路由联动策略 其他相关技巧 - 托管模式下默认不开启Urltest自动测试组,您可以根据需要开启,包括全节点自动测试组(超多订阅节点场景下不建议开启),以及从 其他设置 开启地区自动测试组(按需选择) -…
🔥18👍3❤1
#Bettbox v1.19.8 正式版更新 https://github.com/appshubcc/Bettbox/releases/tag/v1.19.8 - 更新 Mihomo 内核至 1.19.34 正式版 - 新增多平台可选 lite 精简版本(注意,精简版本不含以下内核组件: easytier,tailscale,zerotier,gVisor,fake_tcp) - 修复扫码页相机权限请求问题 by Catapult291 - Linux 端支持通过 GTK icon theme 解析本地进程图标 by VillagerTom - 新增订阅配置合并功能,支持多订阅合并统一处理 by AIsouler - 新增托管脚本与内置分流预设 (支持完全自定义),更完善的规则处理 - 替换平台图标为内置路由 SVG 矢量图标库,内置图标集 by aaANDkk - 仪表盘与配置列表支持多种订阅流量用量显示 (包含代理集显…
🔥55❤10👏6⚡2
推荐来自群友aaANDkk的完整图标库 Github地址,⭐ Star走起: https://github.com/aaANDkk/Qure_Style_SVG 1480 个 矢量SVG:其中包含 1210 个通用图标、270 个地区与组织旗帜,完全适用于Qure 风格的各类Mihomo / Clash / FlClash / Bettbox / Surge / Quantumult X等应用,(包含Flutter兼容性验证) PS: Bettbox内置托管模式图标库后续也将会切换过来
❤36❤🔥3🥰1
大的来了,新群链接: https://t.me/bettbox_chat
👍22😢4🤣3
Your community 💬 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙩 was blocked for violations of the Telegram Terms of Service based on user reports confirmed by our moderators. If you think this is not correct, you can appeal this decision by sending /appealxxxxx to this chat. 新群组: https://t.me/bettbox_chat
🤯60🤔9😱6❤3👏3😇2
⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡 pinned a photo
📢 Maru Code API 船新上线 ! 🤩 主营 Codex、Claude Code 支持模型: 💻 GPT-6 Astra 6.1 Sol Terra Luna 😒 Claude Fable 5.1 Claude Opus 5.5 Sonnet 5.5 Haiku 5.5 (目前倍率 OpenAi:0.3、Anthropic:1.7)主打稳定,不做低价流 ——偶尔做做慈善的小破站 API,站内 🍟每周星期四 会做 限时倍率活动 ,目前已运营半年有余,大群3K人,主打稳定、欢迎高校、企业等合作,感谢🙇 🎈 明码标价,自有号池,不用 Free/ 日抛plus号 🎈 透明汇率 (1:1)、倍率,痛恨 暗改 Cache Hit 商家 🎈 站内平均 Cache Hit Rate 90%+ 🤩 欢迎来蹬(<ヽω・)☆~kira! 🔗 https://api.m…
😁12❤6🤔2
#Bettbox 配套规则集项目完工 https://github.com/appshubcc/bett-rules 1.RULE-SET路由规则与DNS配置简易参考 2.如有独立域名规则问题反馈,建议直接提交到原始上游项目 v2fly/domain-list-community 3.Singbox原.db格式已恢复,全部GEO文件均包含对应的lite精简版本(注:Mihomo推荐优先使用对应的MRS格式) 4.Readme 完善,没打算写复杂的介绍对比,具体可自行体验
❤22👍10
⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡 pinned «恰饭,推荐几个自用机场 简单更新了一下另外两个机场的介绍文字,都是个人使用(过)的,萝卜或白菜,根据自己的具体预算选择即可 https://t.me/appshub_channel/381»
Showing the 12 most recent of 32 posts we hold for @appshub_channel. 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.
@appshub_channel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 4 posts on @appshub_channel 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 7 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.
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.
@appshub_channel named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡” (@appshub_channel), 6,899 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/appshub_channel.
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.