关于提升加密插件的安全性,接下来会做下面更新: 1、限制加密插件的能力,比如不能进行网络请求 2、提前展示风险,更显眼的展示加密插件,展示具有隐患的内容,比如展示重定向等复写 3、默认关闭加密插件功能,阅读相关条例和风险条例后才能启用 4、加密插件源准许名单,只有用户允许的域名列表中的url才能订阅加密插件,防止误装来源不明的加密插件
👍19❤1

Channel
@LoonNews
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
48,264subscribers
+3,203 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001475508058 |
|---|---|
| Type | Channel |
| Username | @LoonNews |
| Description | Loon News |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/LoonNews |
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 21 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 30 Oct 2026, 19:38 | 48,264 | +1 |
| 29 Oct 2026, 17:20 | 48,263 | -13 |
| 28 Oct 2026, 19:50 | 48,276 | -7 |
| 27 Oct 2026, 16:50 | 48,283 | +12 |
| 26 Oct 2026, 19:47 | 48,271 | -14 |
| 25 Oct 2026, 17:06 | 48,285 | +6 |
| 23 Oct 2026, 22:25 | 48,279 | -7 |
| 22 Oct 2026, 22:21 | 48,286 | +10 |
| 21 Oct 2026, 16:37 | 48,276 | +11 |
| 20 Oct 2026, 12:59 | 48,265 | +5 |
| 19 Oct 2026, 10:00 | 48,260 | +19 |
| 18 Oct 2026, 10:40 | 48,241 | +12 |
| 16 Oct 2026, 14:50 | 48,229 | +7 |
| 15 Oct 2026, 13:05 | 48,222 | +5 |
| 14 Oct 2026, 11:56 | 48,217 | -11 |
| 12 Oct 2026, 21:09 | 48,228 | +79 |
| 8 Oct 2026, 07:39 | 48,149 | +21 |
| 3 Oct 2026, 16:39 | 48,128 | +2,105 |
| 25 Sept 2026, 00:02 | 46,023 | +389 |
| 17 Sept 2026, 04:42 | 45,634 | first reading |
94 posts held, back to 17 July 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 172 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 31 October 2026 |
|---|---|
| Posts held | 94 (17 July 2026 – 31 October 2026) |
| Views total | 151,330 |
| Reactions total | 313 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Oct 2026, 16:43 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 31 October 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.
1,491 reactions across 83 posts, in 28 distinct kinds. The most used accounts for 39.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 591 | 39.6% | |
| ❤ | 543 | 36.4% | |
| 🌚 | 58 | 3.89% | |
| 🥰 | 53 | 3.55% | |
| 😱 | 48 | 3.22% | |
| 😨 | 47 | 3.15% | |
| 🎉 | 34 | 2.28% | |
| 🤣 | 24 | 1.61% | |
| 👏 | 23 | 1.54% | |
| 😡 | 9 | 0.604% | |
| 🍌 | 8 | 0.537% | |
| 🤔 | 8 | 0.537% | |
| 💯 | 5 | 0.335% | |
| 🙊 | 5 | 0.335% | |
| 🙏 | 5 | 0.335% | |
| 🤨 | 5 | 0.335% | |
| 🆒 | 4 | 0.268% | |
| 💔 | 4 | 0.268% | |
| 🫡 | 4 | 0.268% | |
| 🌭 | 2 | 0.134% | |
| 8 further kinds | 11 | 0.738% |
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 91 of the 94 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 1,597 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 94 most recent posts we hold, published 17 July 2026 to 31 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.
关于提升加密插件的安全性,接下来会做下面更新: 1、限制加密插件的能力,比如不能进行网络请求 2、提前展示风险,更显眼的展示加密插件,展示具有隐患的内容,比如展示重定向等复写 3、默认关闭加密插件功能,阅读相关条例和风险条例后才能启用 4、加密插件源准许名单,只有用户允许的域名列表中的url才能订阅加密插件,防止误装来源不明的加密插件
👍19❤1
关于加密插件我想说的是任何事物都有两面性,加密插件大家最担心就是数据安全问题,目前最应该讨论的不是删除不删除这个功能,而是如何能在闭源的情况下更好的防患数据安全,这也是以后Loon会继续加强的;如果实在接受不了加密插件也可以不使用加密插件,插件列表和详情都有明显的提示,同时Loon也是可以安装开源插件的;如果为此讨厌或者放弃Loon,那也是人之常情,选择自己喜欢的就好,毕竟很难做到让所有人满意,但Loon会尽力做产品。最后感谢所有插件作者的辛苦付出。
❤26👍3
Signed Tartarus
碰到此报错 把Loon关闭并重新打开即可。
❤11
Signed Tartarus
#TestFlight #iOS Loon 3.5.3(1014)版本已准备好在iOS 上进行测试。 - 修复优化证书逻辑带入的函数调用异常 crash - 支持私有插件,可使用配套工具进行打包:https://nsloon.app/plugin-encryptor - 插件注解支持 #!source,指定插件下载地址,当下载地址和指定不一致时给出警告提示 备注:私有插件内容不可见,请确信安装来源后再使用 3.5.3 RC 👥 频道:@LoonNews 💬 群组:@Loon0x00
❤10🤨2
Signed Tartarus
#TestFlight #iOS Loon 3.5.3(1013)版本已准备好在iOS 上进行测试。 - 修复通知点击无法进入脚本记录页面的 bug - 暂时回退之前重构的 http 引擎 3.5.3 RC 👥 频道:@LoonNews 💬 群组:@Loon0x00
👍7
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.5.0(1011)版本已准备好在 Mac OS上进行测试。 - 修复未开启 DHCP 导致网关劫持 DNS 劫持异常的 bug - 优化证书管理 - 同步 iOS bug 修复 最新包下载地址:https://github.com/Loon0x00/Loon4Mac/releases/download/0.5.0(1011)/Loon-0.5.0-beta-1011.dmg 历史版本记录:https://nsloon.app/Loon4Mac/changelog.html 👥 频道: @LoonNews 💬 群组: @Loon0x00
👍6❤4
Signed Tartarus
#TestFlight #iOS Loon 3.5.3(1012)版本已准备好在iOS 上进行测试。 - 修复 http header rewrite 异常 - 优化证书有效性识别、MITM 开关不再受证书异常控制 - 修复点击通知无法进入到相关脚本记录页面的 bug - 一些文案优化 PS:出现证书报错的,打开 app 重启下 VPN 就好了。 👥 频道:@LoonNews 💬 群组:@Loon0x00
👍8
Signed Tartarus
#TestFlight #iOS Loon 3.5.3(1011)版本已准备好在iOS 上进行测试。 - 重构 http 解析引擎,增加大量之前缺失的 RFC 文档中提及但比较少见的用例 - 修复不同配置切换导致证书使用、API 获取证书、分享证书异常的问题 - 修复 rewrite 的几个bug - PS:出现证书报错的,打开 app 重启下 VPN 就好了。 👥 频道:@LoonNews 💬 群组:@Loon0x00
❤5👍4
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.5.0(1009)版本已准备好在 Mac OS上进行测试。 - 新增网关功能,具体功能和教程见:https://nsloon.app/blog/loon4mac-gateway - 新增 DHCP 功能,具体功能和教程见:https://nsloon.app/blog/loon4mac-dhcp - 优化进程规则,加入更多匹配方式,具体见:https://nsloon.app/docs/Rule/process_rule - 性能优化,最新版本在m1 max macbook 上的回环测试为:单流上传12G,单流下载 14G,具体测试结果和测试方式见:https://nsloon.app/blog/loon4mac-tcp-performance - 优化首页布局显示 - 合并最新版 iOS 功能 最新包下载地址:https://github.com/Loon0…
👍32❤9🎉3😈1
Signed Tartarus
🎉 高德地图去广告 ⭐️ 移除高德地图开屏广告、各页面推广,精简我的页面及配置文件。 ❗️ 此版已彻底重写,不再引用上游内容。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin
👍18❤5
#TestFlight #iOS Loon 3.5.3(1008)版本已准备好在iOS 上进行测试。 - 添加域名正则 DOMAIN-WILDCARD 规则,具体见:https://nsloon.app/docs/Rule/domain_rule/#domain-wildcard ;匹配5万规则大概 0.1ms,具体测试数据见:https://nsloon.app/docs/Rule/#%E6%9F%A5%E8%AF%A2%E6%80%A7%E8%83%BD - 修复head 请求 mock异常bug - 修复本地资源更新时异常更新进度的bug,优化资源图标缓存策略 👥 频道:@LoonNews 💬 群组:@Loon0x00
👍20😱7🆒3❤1
Signed Tartarus
🎉 口袋壁纸去广告 ⭐️ 移除悬浮广告,精简我的页面。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin
❤3👍3
Showing the 12 most recent of 94 posts we hold for @LoonNews. 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.
@LoonNews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 16 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 27 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 45 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Loon News” (@LoonNews), 48,264 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/LoonNews.
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.