接着把task部分复制进行转换 前面已经说过 通过url方式添加的模块是无法进行修改参数虽说可以通过scripthub进行修改 但是我还是比较推荐通过本地新建方式添加 图3中转换完的task参数点击预览 可以看到转换后surge格式的参数如图4 把它复制下来前往surge模块 - 新建本地模块添加

Channel
云深月浅
@yunshenyueqian
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
3,084subscribers
-58 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001819876318 |
|---|---|
| Type | Channel |
| Username | @yunshenyueqian |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/yunshenyueqian |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 26 Sept 2026, 19:17 | 3,084 | -21 |
| 17 Sept 2026, 07:57 | 3,105 | +1 |
| 13 Sept 2026, 07:19 | 3,104 | -1 |
| 9 Sept 2026, 01:15 | 3,105 | +1 |
| 3 Sept 2026, 23:18 | 3,104 | -8 |
| 31 Aug 2026, 21:14 | 3,112 | -6 |
| 28 Aug 2026, 22:25 | 3,118 | -2 |
| 26 Aug 2026, 08:25 | 3,120 | -2 |
| 23 Aug 2026, 04:26 | 3,122 | -8 |
| 19 Aug 2026, 13:07 | 3,130 | +3 |
| 16 Aug 2026, 21:43 | 3,127 | -5 |
| 13 Aug 2026, 13:59 | 3,132 | -2 |
| 11 Aug 2026, 00:35 | 3,134 | -8 |
| 7 Aug 2026, 13:31 | 3,142 | no change |
| 7 Aug 2026, 12:49 | 3,142 | first reading |
Engagement
8 posts held, back to 20 June 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 20 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
⚠️而有些作者可能在脚本中并未标注cron参数 或者整个脚本链接就包含cron参数 如果不会本地模块添加的话可以前往脚本UI里添加。有些脚本运行步骤可能比较多 可能会超过默认的5s 所以可以提高超时时间
签到脚本比通知脚本多了一步获取cookie/token的步骤 打开此脚本链接可以看到有3个部分 分别为task,rewrite和mitm 从语法可以看出是属于quantumult 其中task就是签到的脚本参数 而rewrite和mitm部分就是获取token/cookie的 所以复制rewrite和mitm部分的内容(包括rewriti/mitm这个标题) 前往scripthub进行转换 图2选择本地文本内容 然后把内容粘贴进去 转换后复制链接去模块那里选择url方式添加,添加成功后打开阿里云盘即可看到成功获取token的弹窗。⚠️因为token/cookie获取成功后不需要重复获取 所以获取后可以把该模块关掉
示例脚本:https://gist.githubusercontent.com/Sliverkiss/33800a98dcd029ba09f8b6fc6f0f5162/raw/aliyun.js
签到脚本使用步骤
#
还有如果想手动运行也可以去脚本编辑器里测试,也可以修改一些参数。图2点击载入即可找到所有添加的脚本。⚠如果显示timeout可以尝试点击左下角齿轮-点击模拟执行-点击超时-选择180秒然后重新执行
当然 cron也可以通过脚本UI添加 图3所示红色部分为脚本类型 绿色部分为cron表达式 紫色部分为脚本链接 因为脚本是远程链接 所以脚本位置选远程 根据对应位置正确添加即可,添加完成后可以长按该脚本,点击测试执行可以立刻运行一次脚本
Showing the 8 most recent of 8 posts we hold for @yunshenyueqian. 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.
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.
@Quantumultxxxx · 20,863
Telegram ranks this channel #20 of 37 here — alongside 36 others — read 25 September 2026
@deb_dylib · 22,201
Telegram ranks this channel #21 of 23 here — alongside 22 others — read 21 September 2026
@ddm1023 · 49,094
Telegram ranks this channel #39 of 41 here — alongside 40 others — read 26 August 2026
This channel appears in 3 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“云深月浅” (@yunshenyueqian), 3,084 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/yunshenyueqian.
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.