12 Jun 2026, 11:34 UTC≈7,310 views0 reactionsread 7 August 2026
Posted without readable text
Channel
Surge 补全计划文书版
@LoonKissSurge
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,054subscribers
-1 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 | -1002434388872 |
|---|---|
| Type | Channel |
| Username | @LoonKissSurge |
| Created | Between 1 September 2024 and 26 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/LoonKissSurge |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 20:42 | 2,054 | -3 |
| 1 Sept 2026, 16:02 | 2,057 | +2 |
| 29 Aug 2026, 13:08 | 2,055 | +1 |
| 26 Aug 2026, 03:22 | 2,054 | +1 |
| 23 Aug 2026, 09:38 | 2,053 | -2 |
| 20 Aug 2026, 03:22 | 2,055 | -1 |
| 16 Aug 2026, 18:24 | 2,056 | -1 |
| 13 Aug 2026, 09:48 | 2,057 | +3 |
| 10 Aug 2026, 12:56 | 2,054 | -1 |
| 7 Aug 2026, 20:57 | 2,055 | no change |
| 7 Aug 2026, 15:17 | 2,055 | first reading |
Engagement
20 posts held, back to 26 October 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 1 page 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 20 posts for this entry, the most recent from 12 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
454 reactions across 13 posts, in 16 distinct kinds. The most used accounts for 52.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 237 | 52.2% | |
| ❤ | 120 | 26.4% | |
| 🎉 | 33 | 7.27% | |
| ❤🔥 | 21 | 4.63% | |
| 👏 | 9 | 1.98% | |
| 🥰 | 8 | 1.76% | |
| 👌 | 5 | 1.10% | |
| 🕊 | 5 | 1.10% | |
| 💯 | 4 | 0.881% | |
| 🤯 | 4 | 0.881% | |
| 👎 | 3 | 0.661% | |
| 🆒 | 1 | 0.22% | |
| 👀 | 1 | 0.22% | |
| 😍 | 1 | 0.22% | |
| 😭 | 1 | 0.22% | |
| 🫡 | 1 | 0.22% |
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 16 of the 20 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 454 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 26 October 2024 to 12 June 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.
Recent posts
31 Dec 2025, 13:55 UTC≈5,520 views45 reactionsread 7 August 2026
✨窗外的风把一年吹得很薄，像翻到书页末尾时，那一点几乎听不见的纸响。我们把时间叫作“年”，其实更像一盏灯：起初明亮，后来被日常的雾气轻轻围住，仍旧在。 我想，时光自有温情。温情，并不靠誓言，它更像一碗热汤的旖旎：并不蒸腾，却能让人忽然记起自己仍被世界照拂😼。于是人也不必把祝福说得宏大：若你此刻正独自收拾一年的尾声，愿你被一种安静的安稳托牢；若你正与人相聚，愿你们的笑声像聚放的烟火一样，明亮地留在记忆里。 唉，新的一年未必更顺，但我希望大家可以更柔软、更明亮一些。愿你不必把日子拧得太紧：忙的时候也给自己留有间隙，得与失来回经过时，心里仍有一处不被搅动的清欢安处。愿你把真正重要的轻轻放在掌心里护着，其余的就交给风，交给夜，交给时间去流走😀。 说到蒸汽也没什么可以送给大家的了，十八位的数字代表什么呢？不如粘贴复制一下叭～（🥺但是请不要希冀他都是能让你满意的哦） N8X3 🔤-840Y5-MCZ🤕6 DTZDX-📺J4V-2ZWH…
🎉33❤7🤯4😭1
20 Dec 2025, 16:46 UTC≈9,610 views54 reactionsread 7 August 2026
😉 模块上游提醒 🥰 BiuBiuBiu～经可莉大佬的提醒，给大家说明一下关于哔哩哔哩去广告模块的一些事情。 如您在使用来源自 Loon 的 Bilibili 去广告（来源于 Beta/Surge 直接目录下），请注意 😟： 🥰 因为一些技术上的原因您需要删除该模块，并添加此 模块 （为 Surge 原生维护版本）作为您的替代。 ✨转换自 Loon 的模块因 Bilibili 脚本问题，会导致评论区出现加载缓慢甚至无法加载的问题，Surge 原生模块可以在 Arguments 中编辑开启新特性来缓解此问题，该解决选项默认已打开，❓因两软件对于 Arguments 的实现不同，您需要安装原生版本以启用此优化～ ☕️ 碎碎念：来自 kokoryh 大佬的模块本身对于哔哩哔哩的「净化」较为彻底，有很多朋友不适应此模块，所以如果您的需求较丰富，建议选择 哔哩万象⚙️🌐✈️🪧 模块组来客制化您的需求哦。 😴晚安啦，马上就是元…
❤34👍15🥰4👀1
12 Aug 2025, 04:11 UTC≈6,920 views102 reactionsread 7 August 2026
😈重要更新预公告 我们在审视了当前的需求现状，自项目的可维护性出发，我们决定重构整体项目代码，使用完整的 CI 管道流处理方式进行全面优化。 😼项目代码编写已经完成，我们会完成基本测试后进行上线，由于本次变更结构较大，同时优化了较多的已有问题，考虑到开发者时间不甚充足，我们将会择期进行全面公开发布。 ✨在一些特性被完整释出前，我们会认真地进行评估，针对大家反映的中文 URL 等问题均进行了优化，同时对 Surge 模块也加入了流处理策略。 ✨一个可透露的更新是，本次架构更新后您不在需要使用代理进行拉取模块，我们将借助 @SharonNetwork ⚡️的 CDN 卓越线路表现，为大家提供包括 CN2、9929、CMI2 在内的顶级优化路由支撑的自托管服务。 ✨我们会选择在之后，发布一些意见征集以及投票，来让当前用户选择迁移策略、新架构的部分特性、迫切需要的功能建议。
👍79❤10🕊5👏4👎3💯1
13 May 2025, 14:51 UTC≈7,700 views61 reactionsread 7 August 2026
🔥重点更新内容通知 ✨可莉上游更新了其去广告插件的运行逻辑，本项目跟进后需要注意： 为了降低维护难度，今晚的推送会移除所有插件内的通用规则和通用复写，本地修改涉及64个去广告插件。 此后所有去广告插件将强依赖于这两个插件，也会是所有去广告插件的基础。 没装的今晚更新后大部分去广告插件将会失效。请尽快安装好，避免失效。 ✨这意味着大家需要安装 广告拦截器模块 和 HTTPDNS 屏蔽模块 并且置于模块最下方以保证优先生效，不然更新后可能存在去广告失效风险 ✨顺手安利一个我自己很喜欢的一个 哔哩哔哩模块 ，由模块作者原生维护 Surge 版本，支持视频内跳过推广，特点是去广告去的非常干净，可能部分功能被过度简化。 项目网站： surge.qingr.moe
👍47❤5👌5💯3🥰1
29 Apr 2025, 04:16 UTC≈8,170 views28 reactionsread 7 August 2026
#!name=Github 429 #!desc=解除 Github 429 限制 [Header Rewrite] http-request raw.githubusercontent.com header-replace Accept-Language en-us [MITM] hostname = %APPEND% raw.githubusercontent.com 来源 @mieqq 信息来源 水君 即可绕过 最终版本解决方案
❤24👍4
29 Apr 2025, 03:37 UTC≈7,220 views8 reactionsread 7 August 2026
针对 Github 更新 429 错误的临时解决方案 ✨感谢 @keywos 的优秀工作，我们现在针对 Surge 内更新外部规则 429 的错误提供如下临时解决方案： #!name= Github 限速 #!desc= 提取 Github Blob 内容 #!category= Key [Script] RawBlob = type=http-request,pattern=^https:\/\/raw\.githubusercontent\.com\/,requires-body=0,timeout=20,script-path=br.js [MITM] hostname = %APPEND% raw.githubusercontent.com ✨食用方法： 1. 保存 br.js 到 Surge 文件夹下 2. 新建本地模块，复制以上模块内容到本地模块中，自由命名保存。 3. 再次更新即可。 ⚠️⚠️⚠️ …
❤8
29 Apr 2025, 03:37 UTC≈7,120 viewsread 7 August 2026
File
File, posted without a caption
11 Mar 2025, 16:36 UTC≈12,400 views41 reactionsread 7 August 2026
LoonKissSurge 项目 BreakingChange 提醒 我们提请各位使用者注意，由于 JQ 特性在去广告模块中日益重要的地位，以及转换效果不佳和维护性低的现状，在综合考量其已经发布五个多月的背景下，我们决定讲目前的 Beta 分支特性 ---- JQ 模块支持并入主分支。 您需要如何处理？ ✨如果您目前使用的为 Beta 分支（Beta 文件夹）下的模块，您无需任何动作即可正常使用，仅需注意由于您在我们的 Beta 分支中，我们可能考虑在未来添加需要订阅的以及未经完整测试的转换特性到该分支中，请您注意本频道公告或者保持 Surge 功能订阅（iOS）/大版本跟随的有效性。 ✨如果您目前使用的是普通分支（Surge 文件夹下并且不是 Beta 文件夹下）的模块，您需要确认自己的功能订阅是否激活了 JQ 支持（功能订阅目前有效或过期时间不超过五个月），如果未支持您需要续订功能订阅（iOS）。 我们提醒您我们即…
👍35👏3❤2🆒1
9 Mar 2025, 05:15 UTC≈6,890 views53 reactionsread 7 August 2026
请大家帮忙点一下举报 本项目不允许在境内任何平台进行推广，并且严肃谴责一切滥用本项目进行谋利的行径。 我们知道有些人滥用开源项目，也希望大家协助维护好开源生态避免迫不得已删库等情况的发生。请大家多多点一些举报，十分感谢！ 闲鱼滥用地址：https://m.tb.cn/h.Txa4nvY 点击链接直接举报即可。 再次郑重提醒切勿违反本项目守则！
👍51👏1🫡1
27 Jan 2025, 07:29 UTC≈5,190 views28 reactionsread 7 August 2026
File
马上就是新的一年春节啦，感谢大家对于本频道的支持~ 本项目太小就不进行抽奖啦，给大家把目前收录的原生模块做了一个汇总给大家参考。 感谢项目创立一年来各位大佬的鼎力相助和和和谐有爱的开发者生态！在此不一一言谢啦。 最后： ——愿归乡者纵山川迢递，亦望君平安抵岸，拥得人间烟火满盏。 ——愿驻守者纵隔重城，亦能凭虚拟佳酿，醉倒他乡明月前。 乙巳肇端，伏惟珍摄。 谨祝春祺夏安，秋绥冬禧。✨
❤🔥21❤5👍2
31 Dec 2024, 16:20 UTC≈4,990 views30 reactionsread 7 August 2026
新年祝福🧨(੭˙ᗜ˙)੭🧧 岁序方开，宝鼎烟凝瑞气； 韶华再启，彩笔正绘新图。 玉漏声中，旧痕轻扫； 梅梢影里，新意频生。 但见雪映群山，长天澄澈； 风摇万木，众卉含情。 笙歌辞旧，愿君前程似锦； 灯火迎新，愿卿事业如虹。 万家同乐，齐祝寒梅吐秀； 千里共欢，同盼春柳摇青。 更祈人事顺达，福禄双全； 岁月安稳，笑语盈庭。 此时此刻，谨以薄词献贺： 愿频道的朋友们在新岁里扬帆远航、再筑华章！😈😈
❤22👍4🥰2👏1😍1
Showing the 12 most recent of 20 posts we hold for @LoonKissSurge. 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.
Forward network
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.
Mentions
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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Surge 补全计划文书版” (@LoonKissSurge), 2,054 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/LoonKissSurge.
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.