📝 Script Hub Docker 更新 感谢 Luca 的提醒 ▎升级 Node.js 版本 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
Signed 小一

Channel
@h5683577
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
6,530subscribers
-82 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001543775171 |
|---|---|
| Type | Channel |
| Username | @h5683577 |
| Description | 脚本收集 & 教程分享 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/h5683577 |
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 89% 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 |
|---|---|---|
| 5 Nov 2026, 11:18 | 6,530 | -6 |
| 2 Nov 2026, 06:46 | 6,536 | -9 |
| 27 Oct 2026, 16:55 | 6,545 | -1 |
| 24 Oct 2026, 06:07 | 6,546 | +6 |
| 21 Oct 2026, 02:38 | 6,540 | +5 |
| 18 Oct 2026, 05:11 | 6,535 | -1 |
| 15 Oct 2026, 07:06 | 6,536 | +4 |
| 12 Oct 2026, 12:09 | 6,532 | +13 |
| 5 Oct 2026, 11:55 | 6,519 | -9 |
| 27 Sept 2026, 21:00 | 6,528 | -24 |
| 18 Sept 2026, 01:37 | 6,552 | -3 |
| 14 Sept 2026, 02:59 | 6,555 | -5 |
| 10 Sept 2026, 11:55 | 6,560 | -6 |
| 5 Sept 2026, 01:56 | 6,566 | -4 |
| 1 Sept 2026, 14:44 | 6,570 | +1 |
| 29 Aug 2026, 21:27 | 6,569 | -3 |
| 26 Aug 2026, 18:03 | 6,572 | -7 |
| 24 Aug 2026, 01:26 | 6,579 | -1 |
| 20 Aug 2026, 19:25 | 6,580 | -6 |
| 17 Aug 2026, 16:28 | 6,586 | first reading |
24 posts held, back to 11 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 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 22 October 2026 |
|---|---|
| Posts held | 24 (11 May 2025 – 22 October 2026) |
| Views total | 3,870 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 06:15 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 7 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.
94 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 76.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 72 | 76.6% | |
| 👍 | 13 | 13.8% | |
| 🤡 | 3 | 3.19% | |
| 🤮 | 3 | 3.19% | |
| 😘 | 2 | 2.13% | |
| 💯 | 1 | 1.06% |
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 23 of the 24 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 94 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 11 May 2025 to 22 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.
Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) 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).
📝 Script Hub Docker 更新 感谢 Luca 的提醒 ▎升级 Node.js 版本 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
Signed 小一
📝 Script Hub Beta 版 更新 感谢染指 等最近的努力! ▎当请求 UA 包含 Platform/macOS 时,保留 Loon for Mac 的 PROCESS-NAME 规则 ▎保持 iOS/tvOS Loon 转换诊断不变,而不是默默地发出无效的规则 ▎在 Surge 模块中保留 PROCESS-NAME,因为 Surge Mac 支持流程规则; iOS 在运行时忽略它们 ▎保留不支持的目标处理诊断,而不是强制进行非等效转换 太多了 其实我也不知道具体改了啥 请直接看 commits 👍 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤2
Signed 小一
📝 Script Hub Beta 版 更新 感谢染指和 Tartarus 等最近的努力! ▎新增了 Loon 相关的逻辑, 修复了 Surge 相关的逻辑 太多了 其实我也不知道具体改了啥 请直接看 commits 👍 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
Signed 小一
📝 Script Hub Beta 版 更新 感谢染指和 Tartarus 等最近的努力! ▎新增了 Loon 相关的逻辑, 修复了通知等 太多了 其实我也不知道具体改了啥 请直接看 commits 👍 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
Signed 小一
📝 Script Hub Beta 版 更新 热烈欢迎 染指 加入 Script Hub 开发组 🥰 并带来了本次更新 - 跟进 🎈 Loon 3.5.1+ Script v2 的新参数和原生 Rewrite Action 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤2
Signed 小一
📝 Script Hub Beta 版 更新 热烈欢迎 YuHeng @onz3v 佬加入 Script Hub 开发组 🥰 并带来了本次更新 - 优化 📈 Surge 和 🎈 Loon 对参数的处理 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤10👍4🤮2
Signed 小一
📝 Script Hub 更新 - 优化 仅进行兼容性转换 参数判断和 在脚本开头添加代码 功能 刚刚在看 Surge 的新功能:Logbook... 用 在脚本开头添加代码 或 高级操作(使用代码处理脚本的内容) 就能实现在原来没接入 这个 API ( $surge.logbook ) 的脚本里使用它 同样的 它其实也能用来给没给通知加图片/声音参数的脚本加上参数( 之前也发了 项目情况说明 1. 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 2. 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤7🤮1
Signed 小一
📝 Script Hub 更新 - 脚本转换时也使用自定义请求 Headers 如图 感谢 群友的反馈 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤4🤡3
Signed 小一
📝 Script Hub 更新 - 修复 🏂 Stash 的 transparent 重写 - 🌀 QX jq 转 📈 Surge 和 🎈 Loon 时, 包裹单引号 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤4
Signed 小一
还差八个!!!
Signed 那天我被张佩服用石头砸了一下头
📝 Script Hub 更新 - 🐿️ Egern 模块一键导入 感谢群友 @dewd117 的建议 🎲 项目地址 🥰 #ScriptHub
❤16
Signed 小一
我一定不是最后一个知道的
Signed 那天我被张佩服用石头砸了一下头
Showing the 12 most recent of 24 posts we hold for @h5683577. 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.
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.
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.
@h5683577 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.
References a handle that is not a live channel — we have no record it ever was one.
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 7 seed channels' Telegram-generated recommendation lists in total. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“张佩服应该判几年” (@h5683577), 6,530 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/h5683577.
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.