#wloc 1.0.8 蜂窝下引导改用飞行模式 蜂窝网络下搜不到设备时, 提示从「关闭移动数据」改成了「打开飞行模式」 控制中心一键切换,方便快捷,现在 5G 网络也能 3 秒完成切换定位
❤1

Channel
@NobyDa
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
63,733subscribers
+1,067 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001167646908 |
|---|---|
| Type | Channel |
| Username | @NobyDa |
| Description | 讨论群组: @NobyDa_Chat 脚本反馈: @NobyDa_bot 合作联系: @nubida 个人博客:https://nobyda.github.io/ 个人仓库:https://github.com/NobyDa |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/NobyDa |
Technology — a classification, not a measurement. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 15:14 | 63,733 | +163 |
| 26 Sept 2026, 13:41 | 63,570 | +190 |
| 19 Sept 2026, 11:17 | 63,380 | +36 |
| 16 Sept 2026, 23:59 | 63,344 | +33 |
| 14 Sept 2026, 23:19 | 63,311 | +33 |
| 13 Sept 2026, 11:36 | 63,278 | +27 |
| 11 Sept 2026, 15:38 | 63,251 | +58 |
| 8 Sept 2026, 23:18 | 63,193 | +61 |
| 5 Sept 2026, 16:19 | 63,132 | +39 |
| 3 Sept 2026, 16:58 | 63,093 | +23 |
| 2 Sept 2026, 11:24 | 63,070 | +12 |
| 1 Sept 2026, 10:17 | 63,058 | +15 |
| 31 Aug 2026, 08:57 | 63,043 | +8 |
| 30 Aug 2026, 10:55 | 63,035 | +9 |
| 29 Aug 2026, 08:25 | 63,026 | +14 |
| 28 Aug 2026, 05:02 | 63,012 | +3 |
| 27 Aug 2026, 06:25 | 63,009 | +33 |
| 26 Aug 2026, 08:33 | 62,976 | +1 |
| 25 Aug 2026, 11:52 | 62,975 | +24 |
| 24 Aug 2026, 13:27 | 62,951 | first reading |
29 posts held, back to 24 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 125 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 6 October 2026 |
|---|---|
| Posts held | 29 (24 June 2026 – 6 October 2026) |
| Views total | 113,720 |
| Reactions total | 200 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 17:47 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 6 October 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 2 videos 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.
962 reactions across 29 posts, in 10 distinct kinds. The most used accounts for 58.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 561 | 58.3% | |
| 🌚 | 118 | 12.3% | |
| 👍 | 117 | 12.2% | |
| 😢 | 76 | 7.90% | |
| 🤩 | 33 | 3.43% | |
| 😁 | 32 | 3.33% | |
| 😱 | 10 | 1.04% | |
| 🔥 | 7 | 0.728% | |
| 🎉 | 5 | 0.52% | |
| 👏 | 3 | 0.312% |
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 29 of the 29 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 962 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 24 June 2026 to 6 October 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.
#wloc 1.0.8 蜂窝下引导改用飞行模式 蜂窝网络下搜不到设备时, 提示从「关闭移动数据」改成了「打开飞行模式」 控制中心一键切换,方便快捷,现在 5G 网络也能 3 秒完成切换定位
❤1
Beta Updates New Features - IP Rewrite - Added the [IP Rewrite] section, which handles packets entering Surge VIF at the IP layer based on their destination address, before they reach any rule or policy. Available actions:- reflect: Swaps the source and destination addresses and sends the packet back to its sender. - reject: Responds with a TCP RST to connection attempts and with an ICMP administratively prohibited …
❤2
🪐 Biliverse 哔哩万象: ⚙️ Enhanced v0.6.x 已发布 Created by 反正不是阿狗 Available in 🎈Loon、📈Surge、🏂Stash、🚀Shadowrocket、🌀Quantumult X 部分功能兼容性取决于平台代理能力 本次为 v0.6 系列首个正式版本,只支持新版粉色国内与国际版。 What's New? 1. 新增「Biliverse 哔哩万象」应用内设置入口 • 可直接从「我的」页面进入「Biliverse 哔哩万象」; • 无需再通过 BoxJS,即可在 Bilibili App 内完成复杂、详细的设置; • 现阶段仍会继续向下兼容 BoxJS 一段时间;随着后续增加更多设置控件,未来版本可能不再兼容 BoxJS。 2. 「首页标签页」改由原生「分区」页面管理 • 点击 BoxJS 的「[首页] 标签页」会打开当前版本的「分区」页面; • 可在「分区 → …
❤46👍6
赶场 1.3.0 preview(审核中) 官网地址 同时即将推出订阅制,欢迎大家关注我的小红书账号 正式上线时将在频道开启抽奖活动,月度、年度、终身会员 本次有非常多的功能更新和 UI 优化 新增 - 深色模式(跟随系统 / 浅色 / 深色),App 图标可选四款 - 订阅 Pro - 票根墙:历史票根全屏浏览 - 开票倒计时:提醒 + 灵动岛 / 实况窗 - 影厅座位表与座位视角图,支持投稿 - 有票场次可标「已转票」,账目按净支出算 修复 - 扫票挂错场次 / 缺贴纸白描边、票价口径不一致 - 发现页与票夹切换时空白闪屏 - 性能优化
❤11👏2🌚1
做了一个新的收藏工具:Kepori 🌿 平时在小红书、X、YouTube、B 站或网页看到喜欢的内容,收藏之后经常就再也找不到了。 所以我做了 Kepori,把散落在不同平台的内容统一收进一个地方: 🔗 分享 / 粘贴链接,一键收藏 📖 文章、图片统一整理和阅读 🗂️ 用空间分类自己的灵感和资料 🔍 忘记标题,也能通过内容重新找到 不想做一个「收藏吃灰」的地方,而是希望收藏过的东西,真的能被重新发现和用起来。 Kepori:让每一次「先存着」,都有后来的「用上了」。 TF 链接 小红书账号 希望大家可以关注一下小红书账号,感兴趣的可以进下小红书群聊提提建议,谢谢大家 🙏
👍18❤9
今晚你们会抢首发转手卖掉吗?
👍24❤4😱2
#白嫖模型 #agentrouter #签到 #中转站 点击 链接1 链接2 注册,(内含 aff,双向可获得 $50.00 奖励),需搭配 CPA 请求头 使用。 注册需要 GitHub或 Linux.do,再绑定邮箱。 每日签到(25 刀) 账户密码:绑定邮箱,再点邮箱登录,点忘记密码,就会给你邮箱发一个重置链接,然后再登录后修改密码 -----> agentrouter_MUTU-8888 🎉 登录成功,签到奖励已到账 💰 当前余额:$525.00 📊 累计消耗:$3.96 -----> agentrouter_MUTU-6666 🎉 登录成功,签到奖励已到账 💰 当前余额:$175.00 📊 累计消耗:$0.56
❤17🔥1
🚀 JSBox IPA 工具发布 一款基于 JSBox 的 App Store / IPA 管理工具,主要用于: 📦 安装历史版本 App 支持查找并安装 App 的历史版本,方便回退旧版本。 🛒 查看已购 App 登录 Apple ID 后查看账号已购买的 App。 👥 多账号管理 支持管理多个 Apple ID,切换不同账号查询已购内容。 ⸻ 🔗 JSBox 插件 / 发布页 https://liuguogy.github.io/JSBox-addins/?q=show&objectId=6aa0db905018686533aa2551 💻 GitHub 仓库 https://github.com/dompling/Jsbox-Ipa ✍️ 已购签名服务 https://sap.domplings.com 🔑 签名 Key 5f131ec5e7360f483e1594c22d3489277984b1d64…
❤21🔥1
#wloc 了解wloc https://github.com/Yu9191/wloc 测试在27 beat8 系统完美定位 不依赖电脑独立app即可完成 晚点会先内测等到正式版出了公开仓库
🤩31❤3
IPA工具箱 3.0 - 正式发布 - 修复登录失败 - 解决一些已知问题 安装链接 💡若提示 “找不到 <plist”,请将 Apple 请求走代理
😢5❤3
#Claude Code #孙割 #景甜 #今日话题 https://x.com/sunyuchentron/status/2092946505611252166?s=46 https://x.com/sunyuchentron/status/2092947840960176289?s=46 https://x.com/sunyuchentron/status/2092948676746658213?s=46 https://x.com/sunyuchentron/status/2092950726003789836?s=46 实在没忍住想要分享,北大才子最后还是在 Claude Code 劝说下止步😂
😁4❤3🌚1👍1😱1
Stash 的 Android 版本现已上架 Google Play。这是一个早期版本——核心能力已经完整可用,功能仍在快速迭代中,欢迎测试,更欢迎提意见。 当前版本已支持: - 基于域名、IP-CIDR、GEOIP、GEOSITE 与进程名的规则分流 - 支持 Shadowsocks / Shadowsocks2022、VMess、VLESS、Trojan、Snell、Hysteria 1/2、TUIC、AnyTLS、WireGuard 等协议 - 可视化编辑节点、策略组与规则,以及带语法高亮的配置编辑器 - 连接列表、HTTP 请求检视、DNS 检查、测速、流媒体检测等诊断工具 - 远程控制器,可连接局域网内的另一个 Stash 或 Clash 实例 💡 作为早期版本,功能和稳定性与 iOS 版仍有差距,我们会保持快速的更新节奏,把功能逐步补齐。 如遇到任何问题,请通过 Telegram 向我们反馈,你的反馈会帮助我…
❤19👍9🔥1
Showing the 12 most recent of 29 posts we hold for @NobyDa. 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.
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.
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.
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.
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.
Read from Telegram’s recommendation API, most recently 21 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.
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.
This channel appears in 56 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Surge & Loon & QX 脚本收集” (@NobyDa), 63,733 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/NobyDa.
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.