Telegram RegisterThe public register of Telegram
Telegram profile photo for 开源GitHub

Channel

开源GitHub

@Qun521

On this record: Topic · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,408subscribers

-14 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001930769083
TypeChannel
Username@Qun521
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Qun521

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,4082,4252,416.56 August 2026 — 2,422 subscribers6 August 2026 — 2,422 subscribers7 August 2026 — 2,423 subscribers10 August 2026 — 2,425 subscribers13 August 2026 — 2,421 subscribers16 August 2026 — 2,419 subscribers19 August 2026 — 2,420 subscribers23 August 2026 — 2,417 subscribers27 August 2026 — 2,424 subscribers30 August 2026 — 2,422 subscribers1 September 2026 — 2,421 subscribers5 September 2026 — 2,419 subscribers10 September 2026 — 2,411 subscribers14 September 2026 — 2,415 subscribers19 September 2026 — 2,408 subscribers6 August 202619 September 2026
15 measurements spanning 44 days, net -14. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,405–2,428 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 14:172,408-7
14 Sept 2026, 21:172,415+4
10 Sept 2026, 21:002,411-8
5 Sept 2026, 19:172,419-2
1 Sept 2026, 20:532,421-1
30 Aug 2026, 04:052,422-2
27 Aug 2026, 02:452,424+7
23 Aug 2026, 17:122,417-3
19 Aug 2026, 19:552,420+1
16 Aug 2026, 22:192,419-2
13 Aug 2026, 11:252,421-4
10 Aug 2026, 05:362,425+2
7 Aug 2026, 02:252,423+1
6 Aug 2026, 09:202,422no change
6 Aug 2026, 09:192,422first reading

Engagement

21 posts held, back to 11 July 2026the 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 21 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

26 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 57.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1557.7%
👏726.9%
👍27.69%
👎13.85%
😁13.85%

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 14 of the 21 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 11 July 2026 to 6 August 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

6 Aug 2026, 22:20 UTC72 views1 reactionsread 7 August 2026
Forwarded from @Asterisk4MagiskFile

AsteriskNG v1.3.11 https://github.com/Asterisk4Magisk/AsteriskNG/releases/tag/v1.3.11 AsteriskMETA v1.1.6 https://github.com/Asterisk4Magisk/AsteriskMETA/releases/tag/v1.1.6 AsteriskBOX v1.0.6 https://github.com/Asterisk4Magisk/AsteriskBOX/releases/tag/v1.0.6

👏1

5 Aug 2026, 12:24 UTC118 viewsread 7 August 2026
Forwarded from @github_2dust

https://github.com/2dust/v2rayN/releases/tag/7.24.5

4 Aug 2026, 22:20 UTC503 viewsread 7 August 2026

#lxbox 🚀 LxBox 客户端 2.19.7 版本发布 如果您还不了解 LxBox,不妨了解一下。这个项目是 Sing-box 最新的客户端之一,并且正在以良好的速度进行开发。它的功能非常丰富,未来有可能成为 NekoBox 和 Clash 的有力竞争者。 ✨ 一些功能: • 支持 VLESS、VMess、Trojan、Shadowsocks、Hysteria2、TUIC、Naive、SSH、WireGuard、AmneziaWG 2.0 和 MASQUE • 支持 XHTTP 和 ML-KEM-768 • 一键创建和获取 Cloudflare WARP • 速度测试、延迟测试,并自动选择最佳节点 • 高级路由、分流隧道和专业规则 • 防 DPI 功能,如 TLS 分片和 SNI 混淆 • 实时监控连接、DNS 和流量使用情况 • 内置 JSON 编辑器 • 完全开源,基于 Sing-box ⚠️ 目前,该应用程序

4 Aug 2026, 13:31 UTC516 viewsread 7 August 2026

#incy 🚀 INCY 3.3.9 发布新版本 一个基于 Xray 的开源、现代客户端 INCY 是一个开源、跨平台的Xray-core客户端,专注于速度、简洁和专业功能,支持大多数流行的 Xray 协议。 ✨ 主要特性: 🔹 支持VLESS、VMess、Trojan、Shadowsocks、Hysteria2、WireGuard、SOCKS5和HTTP 代理。 🔹 支持通过订阅、链接、二维码和 JSON 文件添加配置。 🔹 支持Reality、XTLS Vision和uTLS 指纹。 🔹 具有TLS 分片功能,以提高绕过基于 DPI 的限制的几率。 🔹 能够定义路由规则,以智能地引导流量。 🔹 具有高级DNS管理,以实现更稳定的连接。 🔹 支持深度链接,用于自动导入配置和订阅。 🔹 支持加密链接incy://crypt1,以更安全地共享订阅。 🔹 具有现代用户界面,包括深色模式、多种主题以及更改应用程序图标的功能。 🔹

3 Aug 2026, 22:55 UTC568 views2 reactionsread 7 August 2026

🚀 #husi 1.4.3 husi 客户端的更新版本,适用于 Android、Windows、macOS 和 Linux,现已发布。📲💻🍎🐧 它是 nekobox 的一个高级分支,基于 singbox 内核。✅(稳定版) GitHub 链接: 🔗 https://github.com/xchacha20-poly1305/husi/releases/ 下载页面链接: 📥 https://github.com/xchacha20-poly1305/husi/releases/tag/v1.4.3

1😁1

3 Aug 2026, 22:51 UTC538 views0 reactionsread 7 August 2026
File

#surfboard 🏄‍♂️ https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.34.1 🔗 新功能 🆕 - 备份与恢复:将应用程序设置和代理配置文件导出到受密码保护的存档,并在其他设备上恢复它们。支持不同版本。💾 - 子网代理组:支持 subnet 组类型,该类型会根据当前的网络环境(例如 Wi-Fi、蜂窝网络、SSID、网关)自动选择代理。🌐 - mDNS 解析:为第三方应用程序解析 .local 域名;多播流量现在直接发送。🔍 - 仪表盘现在在返回应用程序或切换标签时刷新公共 IP 地址和 DNS。📊 修复 🛠️ - 修复了内置 GeoIP 数据库文件损坏时崩溃的问题。 - 修复了在 VPN 停止后更改代理组时崩溃的问题。 - 修复了在活动重建期间切换标签时崩溃的问题。 - 在代理信息对话框中,保持系统栏显示在边缘。 - 修复了 VPN

19 Jul 2026, 12:23 UTC504 views6 reactionsread 7 August 2026
Forwarded from @yo521File

#bettbox@yo521 🚀 🚀 官方版 Bettbox 一个现代且轻量级的 Mihomo (Clash Meta) 客户端 🛠️。如果您正在寻找一个快速且易于使用的 Mihomo 客户端替代品,那么 Bettbox 是一个不错的选择 ✅。该项目基于早期的 FlClash 构建,但几乎所有方面都经过了优化,从用户界面到电池消耗和整体性能 🔋。它的目标很简单:运行更流畅,消耗更少的电量,并且始终稳定运行。 🔹 支持的协议: • VLESS (Reality / XHTTP) 🌐 • VMess • Trojan • Shadowsocks (R / 2022 / ShadowTLS / Restls) 🛡️ • Hysteria 1 & 2 • TUIC • WireGuard • Tailscale • OpenVPN • SSH • AnyTLS • Snell (v1 到 v5) • Masque • TrustT

5👏1

18 Jul 2026, 22:49 UTC492 viewsread 7 August 2026
Forwarded from @yo521File

#surfboard 🏄‍♂️ https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.33.0 🚀 新功能 ✨ - TUIC v5:支持 TUIC v5 代理协议。 - [Host] 规则集:在 [Host] 部分支持 DOMAIN-SET 和 RULE-SET 规则,用于将 DNS 服务器分配给域名列表。 修复 🛠️ - 修复了空闲连接导致持续 CPU 使用和电池消耗的问题。 - 修复了在仅 TCP 的底层代理上使用 AnyTLS/Trojan/VMess/Snell 代理时,UDP 无法正常工作的问题。 改进 📈 - 配置文件编辑器现在会在字符边界处自动换行长行。 - 改进了 TCP 数据包转发性能。

18 Jul 2026, 14:18 UTC≈1,510 views1 reactionsread 7 August 2026

#clashmeta@qun521 🥡Clash Meta 2.11.32 ♻️Clash Meta Android客户端更新 https://github.com/MetaCubeX/ClashMetaForAndroid/releases https://github.com/MetaCubeX/ClashMetaForAndroid/releases/tag/v2.11.32

👏1

18 Jul 2026, 12:31 UTC441 views1 reactionsread 7 August 2026

#camoufox 🦊 Camoufox 浏览器介绍 Camoufox 是一款轻量级、开源且注重隐私的浏览器,专为希望更好地控制自己的数字身份的用户、开发者和研究人员而设计。它旨在抵御高级浏览器指纹识别技术和机器人检测系统。 Camoufox 通过提供高级工具来管理、修改和同步浏览器指纹,努力减少用户的数字足迹,同时尽量不影响正常的网页浏览体验。 ⭐ 核心功能 🎭 抵抗反机器人系统 Camoufox 经过优化,以减少反机器人系统检测到的特征,并在各种测试中表现出色。 🖐 指纹管理和修改 (无需注入 JavaScript) ✅ 导航器信息,包括设备、操作系统、硬件和浏览器 ✅ 屏幕尺寸、分辨率和视口 ✅ 地理位置、时区、区域设置和国际化信息 ✅ WebRTC 信息的协议级管理 ✅ 控制与音频和语音 API 相关的信息 🎨 应对图形浏览器指纹识别 ✅ 保护 Canvas 免受指纹识别 ✅ 修改 WebGL、插件和上下文

1

18 Jul 2026, 11:33 UTC279 views1 reactionsread 7 August 2026
Forwarded from @yo521File

#lxbox@yo521 #lxbox 📦 LxBox 一款基于 sing-box-lx 的现代 Android 客户端 LxBox 是一款为 Android 平台开发的开源 VPN 客户端,使用 Dart/Flutter 构建,并基于定制内核 sing-box-lx。 除了 sing-box 的常用功能外,该版本还提供了以下新功能: ⚡ 原生支持 XHTTP 🛡 支持 AmneziaWG 2.0 🌐 同时管理多个订阅 🎯 智能路由和路由规则 🚀 内置服务器速度和延迟测试 📊 更好的配置和节点管理 与许多仅提供用户界面的客户端不同,LxBox 基于修改后的内核运行,并直接为用户提供一些 sing-box-lx 的新功能。 🔗 项目源代码:https://github.com/Leadaxe/LxBox

👎1

18 Jul 2026, 08:27 UTC334 viewsread 7 August 2026

TikTok+: #IP质量检测 3 种 IP 质量检测工具 🛠️ 检测 IP 的纯净度 • 检测 IP 定位是否一致: ip111.cn 🌐 • 检测 IP 纯净度: scamalytics.com/ip 🧼 • 检测原生 IP: whoer.net/zh 🕵️‍♂️ 免费苹果ID: 123dh.co TG号批发: tgpifa.cc

Showing the 12 most recent of 21 posts we hold for @Qun521. 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.

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.

免费vpn梯子机场翻墙技术
@FreeVPN8 · 44,030
Telegram ranks this channel #14 of 30 here — alongside 29 others — read 30 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“开源GitHub” (@Qun521), 2,408 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Qun521.

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.