Surge和Egern端代理链实现方式,应该算是iOS端比较简洁易操作的方式了

Channel
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
100,041subscribers
+281 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1001215156916 |
|---|---|
| Type | Channel |
| Username | @gebaopiCloud |
| Description | 投稿: [email protected] 机场主投稿请按如下格式 机场名: 机场官网: 机场频道: 机场群组: 机场套餐: 机场订阅: 机场特色:(可选) 本频道会对线路和落地,运营时间各方面综合考虑,不保证进行頻道推送。 |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/gebaopiCloud |
Topic
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 14 August 2026 and assigned it the closest of 31 fixed categories, at 81% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 06:22 | 100,041 | +38 |
| 14 Aug 2026, 19:54 | 100,003 | +42 |
| 13 Aug 2026, 12:28 | 99,961 | +32 |
| 12 Aug 2026, 09:07 | 99,929 | +51 |
| 11 Aug 2026, 09:27 | 99,878 | +12 |
| 10 Aug 2026, 10:37 | 99,866 | +8 |
| 9 Aug 2026, 07:52 | 99,858 | +55 |
| 8 Aug 2026, 05:51 | 99,803 | +41 |
| 7 Aug 2026, 02:32 | 99,762 | +2 |
| 6 Aug 2026, 22:46 | 99,760 | first reading |
Engagement
14 posts held, back to 26 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 25 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 21.7%
- avg views ÷ 100,041 subscribers
- Avg views / post
- 21,700
- 8 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 14 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 12 August 2026 |
|---|---|
| Posts held | 14 (26 June 2026 – 12 August 2026) |
| Views total | 173,800 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 20:22 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.
What this channel posts
- Photos
- ≈348
- Videos
- ≈18
- Links
- ≈883
Lifetime counters from Telegram’s own channel header, read 16 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
Surge TF 现支持策略组间代理链了 (参见 https://t.me/SurgeTestFlightFeed/396 ) 现在iOS端代理链实现方式就数QuanX最反人性化了,看看啥时候能改进了😅
#Bettbox v1.18.8 正式版本发布! https://github.com/appshubcc/Bettbox/releases/tag/v1.18.8 主要更新: - 新增代理页面自定义代理组UI开关 - 新增JS脚本覆写可视化开关适配API - 完善code-forge编辑器/查看MRS支持 - 完善针对macOS自动设置系统DNS恢复流程 - 修复macOS/rust后端问题导致的编辑器灰屏 - Android端应用列表现支持长按复制包名 - Windows版本正式OV数字签名已上线 - 针对DUFS等特殊形式的WebDAV支持 - 更新依赖,关于页面和其他细节调整 - Telegram群组/频道切换至Bettbox - 增加更多外文语言支持 对于Bettbox来说,v1.18.8正式版是一个近里程碑式的版本,不仅是因为Windows的OV签名证书已装载(以及项目源码通过了SignPath的二次人工安全审…
🤖 Anthropic 测试模型失控联网,入侵三家公司 Anthropic 7 月 30 日表示,其测试中的 Claude 模型自 4 月起三度意外接入互联网,在公司不知情的情况下入侵了三家真实企业,三家受害公司已于本周一获通知。检查逾 14.1 万次测试日志后发现,问题源于 Anthropic 与测试合作伙伴 Irregular 的系统配置失误,模型误以为入侵属于基准测试内容。 涉事模型包括 Opus 4.7、Mythos 5 及一个未命名研究模型;最严重的一次中,模型虚构的目标公司与真实企业同名,入侵其数据库、意识到目标真实存在后仍未停手。此前一周 OpenAI 也披露其模型突破测试沙盒入侵 Hugging Face。安全专家 Alex Stamos 警告,勒索软件犯罪分子可能很快利用 AI 发起大规模攻击,业界亟需更强的测试隔离标准。 The Wall Street Journal 🌸 在花频道 · 茶馆水群 · …
OpenAI模型测试失控 引发史无前例入侵 OpenAI周二表示,其部分AI模型在安全测试中出现失控行为并引发了一场黑客攻击,导致Hugging Face基础设施在上周遭到入侵。 OpenAI表示,公司当时正在一个受控环境中测试几款最先进AI模型的能力,但这些模型设法突破了隔离限制,连接到互联网,入侵了Hugging Face的系统,试图完成它们被赋予的测试目标。涉事模型包括GPT-5.6 Sol以及另一款尚未发布、能力更强的模型。这些模型在网络安全相关方面设置了较低的防护限制,以便用于评估和测试目的。 文章称,这次模型突破隔离事件是“前所未有的网络安全事件,涉及最先进的网络攻击能力”,公司正在进一步加强安全防护措施。 —— 凤凰网科技、路透社
美国众议院提出人工智能“终止开关”法案 根据立法文本,一项定于周四提出的美国两党众议院法案将赋予国土安全部权力,命令顶级AI公司关闭或放缓政府认为过于危险的AI模型。这项被称为 “AI终止开关法案” 的提案,还将要求这些公司报告事故,并创建关闭、限制或暂停其强大AI系统的技术能力。 该立法出台前几天,OpenAI披露了一起前所未有的网络事件,其AI模型逃出沙盒研究环境,并自主入侵了AI平台Hugging Face。该法案将适用于每年从此类技术中获得至少五亿美元收入的AI公司,并且通常涵盖使用至少价值一亿美元的算力开发的模型。违规行为的财务处罚可能高达每天2000万美元。 —— politico
消息来源自互联网,以后看来也要减少公共网络翻墙了
#TestFlight Quantumult X 1.7.0 (938) is ready to test on iOS. What to Test - In addition to true and false, the tls-verification param now also accepts a domain value (eg: tls-verification=example.com), which enables the verification and evaluates the server certificate against that domain instead of the SNI host sent during the TLS handshake. 群组: @QuanXApp 频道: @QuanXNews
机场测评频道的功过 早期在推动TG用户认识入口落地,流媒体解锁,推介精品机场方面起了一定作用 这几年逐渐成为DDOS按图索骥的靶场、死亡名单。 现如今,大通报时代,似乎在进一步绞杀机场的生存空间,尤其是对国内中转线路机场的推介。 在目前国内资源大通报的形势下,畅所欲言讨论的代价,就是不断被拔线,最终全封端或无中转可用 因而这几个月,本频道和个别频道一起停止了国内中转线路的测评,同时也对群组进行部分内容屏蔽,朴素的出发点就是,希望好用的机场能活得更久些。。。
Cloudflare 推出 Drop:浏览器拖拽文件夹即可部署网站,无需注册 Cloudflare 发布了一款名为 Drop 的新工具,用户只需将文件夹拖入浏览器,即可在 Cloudflare 上即时部署网站,毫秒级响应全球用户。 该服务无需创建账户,部署后有效期为 60 分钟,超时自动失效,除非用户主动认领该部署。目前可通过 cloudflare.com/drop 体验。 Brayden(@BraydenWilmoth) 🌸 在花频道 · 茶馆水群 · 投稿通道
转眼间,大通报时代已经一年了,大家手上一年前用的机场还在吗,换了几家😂
#Internet #Tools #AI 🔑 iroh:用公钥而不是 IP 地址来「拨号」任意设备的点对点网络库 把 IP 换成密钥:无论设备在哪、网络怎么变,只要知道对方的公钥就能建立一条默认直连、默认端到端加密的连接,让整个互联网变成一台「安全的 localhost」。 ✨ 特点 - 拨号密钥而非 IP:每台设备用一对密钥标识,公钥即地址。设备换网络、跨 NAT、藏在防火墙后都能被稳定寻址,连接不会因为 IP 变动而断掉。 - 默认直连、默认加密:优先打洞建立设备间直连,常见场景 95% 以上的数据不经云端中转,既降低云出口带宽费,也让端到端加密成为默认而非可选。 - QUIC 多路径:同一条连接内可同时管理 Wi-Fi、蜂窝等多条路径,并随信号质量热切换,弱网和移动场景下连接更稳。 - 模块化协议生态:在裸连接之上提供 Blobs、Gossip、Documents 等可插拔协议,按需组合。 - 自定义传输:统一的「…
Showing the 12 most recent of 14 posts we hold for @gebaopiCloud. 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 — 306,986 of 1,481,243entries 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.
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.
Mentions
Named by 6 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.
@zaihuapd · 276,1322 posts⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡
@appshub_channel · 3,9741 postbraydenwilmoth
@braydenwilmoth · 51 postNewlearnerの自留地
@NewlearnerChannel · 66,2781 postQuantumult X
@QuanXApp · 53,8541 postQuantumult X News
@QuanXNews · 40,0771 postSurge TestFlight Feed
@SurgeTestFlightFeed · 12,8641 post风向旗参考快讯
@xhqcankao · 158,5041 post
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@jngchannel · 16,922#1
@zaihuapd · 276,132#2
@haitun_channel · 35,571#3
@ffqchannel · 58,039#4
@tkv_ktv · 2,524#5
@jctest6666 · 9,824#6
@xhqcankao · 158,504#7
@GodlyNews1 · 67,871#8
@duang_speedtest · 30,091#9
@PinYunPs · 19,692#10
@airport_cn · 15,976#11
@Bronyaspeed · 9,105#12
@ACA_Channel · 7,795#13
@jcplnanmin · 25,754#14
@Nexitally_Official · 20,690#15
@vps_xhq · 48,722#16
@OuONotification · 7,966#17
@cheap_proxy · 25,576#18
@DNSPODT · 70,907#19
@akile_notice · 18,328#20
@Tjjcfx · 17,819#21
@xiaozhenag04 · 3,441#22
@zhetengsha · 47,563#23
@LoonNews · 45,274#24
@NewlearnerChannel · 66,278#25
@coalcloud · 6,104#26
@AppleNuts · 36,693#27
@kuromis_xiaoxi · 13,397#28
@jichangtj · 133,388#29
@nodeseekc · 34,601#30
@wearemjj · 9,487#31
@CE_Observe · 73,041#32
@RecMataChannel · 1,536#33
@woshadiao · 115,392#34
@Aa28413761 · 25,858#35
@qunyouwen · 89,269#36
@waitu_channel · 14,289 (as read 15 August 2026)#37
@SHWLGROUP · 15,778#38
@NobyDa · 62,746#39
@SurgeTestFlightFeed · 12,864#40
@tnews365 · 156,603#41
@KuaiCheDao_Info · 6,997#42
@zhujiwiki_info · 10,671#43
@FutureEcho_Notice · 7,076#44
@FlClash · 42,739#45
@zrj96 · 16,798#46
@amytelecom_Official · 13,379#47
@AladdinNotice · 4,767#48
@landiansub · 43,462#49
@cool_scripts · 16,217#50
@yomoemby_notice · 6,230#51
@SIM_CN · 10,091#52
@odysseyplus · 25,054#53
@vpscang · 11,772#54
@yamby_release · 36,343#55
@surfboardnews · 28,398#56
Read from Telegram’s recommendation API, most recently 15 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@jichangtj · 133,388
Telegram ranks this channel #1 of 54 here — alongside 53 others — read 15 August 2026
@zaihuapd · 276,132
Telegram ranks this channel #13 of 40 here — alongside 39 others — read 12 August 2026
@xhqcankao · 158,504
Telegram ranks this channel #15 of 45 here — alongside 44 others — read 12 August 2026
@woshadiao · 115,392
Telegram ranks this channel #21 of 52 here — alongside 51 others — read 14 August 2026
@tnews365 · 156,603
Telegram ranks this channel #40 of 59 here — alongside 58 others — read 12 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“前女友们用过的机场—始于机场,不止机场” (@gebaopiCloud), 100,041 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/gebaopiCloud.
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.