🎉 青龙(QingLong)GitHub Stars 突破 20,000! 感谢每一位使用、反馈、贡献代码和分享青龙的朋友。每一颗 Star,都让青龙走得更远。🐉 🔗 https://github.com/whyour/qinglong
🎉45

Channel
@jiao_long
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
32,874subscribers
-439 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001465257366 |
|---|---|
| Type | Channel |
| Username | @jiao_long |
| Description | JavaScript/Python/Typescript/Shell脚本管理平台 |
| Created | Between 1 April 2019 and 31 October 2021 — 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 | 59 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/jiao_long |
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 9 September 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 |
|---|---|---|
| 5 Nov 2026, 22:59 | 32,874 | -4 |
| 4 Nov 2026, 19:38 | 32,878 | -8 |
| 3 Nov 2026, 22:26 | 32,886 | -4 |
| 2 Nov 2026, 23:26 | 32,890 | +3 |
| 2 Nov 2026, 02:00 | 32,887 | -9 |
| 31 Oct 2026, 22:48 | 32,896 | -6 |
| 30 Oct 2026, 20:26 | 32,902 | -11 |
| 29 Oct 2026, 20:56 | 32,913 | -3 |
| 28 Oct 2026, 23:30 | 32,916 | -7 |
| 27 Oct 2026, 23:14 | 32,923 | -5 |
| 27 Oct 2026, 01:57 | 32,928 | +3 |
| 26 Oct 2026, 05:25 | 32,925 | -2 |
| 25 Oct 2026, 03:36 | 32,927 | -9 |
| 24 Oct 2026, 04:36 | 32,936 | -5 |
| 23 Oct 2026, 04:57 | 32,941 | -8 |
| 22 Oct 2026, 01:49 | 32,949 | -5 |
| 20 Oct 2026, 18:55 | 32,954 | -7 |
| 19 Oct 2026, 21:16 | 32,961 | -5 |
| 18 Oct 2026, 22:28 | 32,966 | -4 |
| 17 Oct 2026, 20:30 | 32,970 | first reading |
25 posts held, back to 14 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 162 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 1 November 2026 |
|---|---|
| Posts held | 25 (14 June 2024 – 1 November 2026) |
| Views total | 27,430 |
| Reactions total | 89 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 07:38 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 6 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.
605 reactions across 24 posts, in 11 distinct kinds. The most used accounts for 26.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 162 | 26.8% | |
| 💩 | 120 | 19.8% | |
| 🥰 | 105 | 17.4% | |
| 👏 | 102 | 16.9% | |
| 🎉 | 68 | 11.2% | |
| 🤣 | 20 | 3.31% | |
| 🤔 | 10 | 1.65% | |
| 🥴 | 10 | 1.65% | |
| 🥱 | 5 | 0.826% | |
| 😁 | 2 | 0.331% | |
| 🤩 | 1 | 0.165% |
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 25 of the 25 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 605 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 14 June 2024 to 1 November 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: 2 of 4 posts held from the last 30 days (50.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).
🎉 青龙(QingLong)GitHub Stars 突破 20,000! 感谢每一位使用、反馈、贡献代码和分享青龙的朋友。每一颗 Star,都让青龙走得更远。🐉 🔗 https://github.com/whyour/qinglong
🎉45
青龙 v2.24.0 ✨ 新增功能: 1. Node.js 原生部署支持 Python venv 隔离;Python 依赖可使用 Git URL、requirements 文件和 pyproject.toml。订阅拉取不会自动安装仓库声明的依赖。 2. 新增通知审计日志,便于查看系统及 JavaScript/Python 脚本通知的发送结果。 3. 平台升级包支持在线暂存、离线安装、失败回退,并在迁移时保留账号、配置、环境变量、任务和脚本等数据。 🔧 修复与优化: 1. 默认 Alpine 与 Debian 镜像升级至 Node.js 24、Python 3.11,SQLite 依赖升级至 1.1.4。 2. 修复任务调度与排队、额外规则校验、订阅同步、Python 依赖安装和脚本发现等问题。 3. 修复清理系统日志时移除活跃文件、页面加载时序和升级流程中的异常,补齐中英文提示。 4. 独立远程 CLI 更新至 0.1.3,…
👏6🥰2🤔1
青龙 v2.23.0 ✨ 新增功能: 1. 新增脚本历史版本查看、对比与恢复,每个脚本最多保留 20 个版本。恢复前检查内容哈希,避免覆盖同时发生的修改。 2. 远程 CLI 更新至 0.1.2,增加脚本历史命令,完善冲突和认证错误提示。 🔧 修复与优化: 1. 普通任务与订阅调度迁移到 node-cron,保留旧规则兼容,补充宏与夏令时行为说明。 2. 修复禁用、删除或修改后旧排队任务仍执行的问题,完善超时、停止和 Shell before/after 环境传递。 3. 修复长期运行后的系统令牌失效和认证缓存并发更新;Shell API 遇到 401 会刷新令牌并重试一次。 4. 降低任务启动开销,JS/Python 通知依赖改为首次调用时加载。 5. 加固环境变量、订阅参数、路径与 SSH 配置,保留合法中文和分支别名。 6. 修复页面升级、ql update 和静态资源同步,完善升级校验、完整备份与恢复;修复 De…
💩17🥰7
推荐一个朋友做的小工具 usAge:把 Codex、Claude、Cursor 等 AI 服务的用量、剩余额度和重置时间放在一起,还能放到桌面小组件上,省得来回打开各家后台。 支持 Apple、Android 和 HarmonyOS,用量请求由设备直连服务商。 👉 https://usage.o-c.do/zh-Hans
💩6🥰3🤡2
青龙 v2.22.0 ✨ 新增功能: 1. 新增独立远程 CLI,支持命令行管理任务、订阅、环境变量、脚本等,支持 JSON 输出和中英文帮助 2. 仪表盘支持点击「今日成功 / 今日失败」查看任务明细 3. 新增客户端 IP 与代理链诊断、可信代理配置和登录 IP 黑名单 4. 新增历史运行记录清理预览、手动清理、依赖缓存清理和数据库压缩 5. 新增 WPUSH 通知,支持面板、JavaScript、Python 和 gRPC 6. 新增 ql log 命令,方便查看服务日志 🔧 修复与优化: 1. 优化任务调度、排队、停止与恢复,完善停止失败提示 2. 优化大日志分块读取,修复任务结束后日志显示不完整、中文日志名等问题 3. 加固密码存储、登录认证、两步验证和文件访问 4. 修复登录过期后页面反复刷新,完善任务参数校验提示 5. 优化大目录读取、缓存和依赖管理,减少常驻资源开销 6. 启动时保留 .env 配置,完善…
🥰13🤡7👏3🎉1
青龙 v2.21.0 更新说明: 1. 增加任务统计功能 2. 增加运行实例功能 3. 增加环境变量标签功能 4. 新增 OpeniLink 通知渠道 5. 支持自定义接收邮箱地址 6. gRPC 服务增加证书校验 7. 定时任务增加 work_dir 设置 8. 修复 CodeMirror 页面切换多实例崩溃 9. 修复 IPv6 网络连接问题 10. 修复 gRPC extra_schedules 为空时序列化报错 11. 修复 HITOKOTO 参数布尔/字符串类型处理 12. 修复 Server酱 返回错误时 undefined 异常 13. 修复环境变量 position 数据类型异常 14. 修复 Docker 健康检查 QlPort 环境变量读取 15. 其他问题修复 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 dock…
👏28🤡12🤣5💩4🥰3
👍项目推荐👍 Orange Cloud,是一个 Cloudflare 的原生 iOS 客户端。 主要特点: 使用 Cloudflare 官方 OAuth 登录(不需要 API Token) 所有数据本地存储,设备直连 Cloudflare API 支持 DNS / Workers / R2 / D1 / KV / WAF / Tunnel / Analytics 等常用功能 开源项目,目前还在持续迭代 适合经常用 Cloudflare 做网站或自建服务的人,在手机上快速查看和管理状态。 GitHub:https://github.com/chen2he/orange-cloud (也有 TestFlight 版本可以体验)
👏15🎉1🥰1
青龙 v2.20.2 (❗️重要❗️) 更新说明: 1. 修复 path 和 init 接口安全漏洞(重要) 所有版本都需要更新,要不就不要开外网 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR <容器名> -> debian 版本同步更新 版本镜像: 正式版: whyour/qinglong:latest Python3.10 正式版: whyour/qinglong:python3.10 debian 版: whyour/qinglong:debian Python3.10 debian 版: whyour/qinglong:debian-python3.1…
🤡135💩56🤣14🤔9👏8
青龙 v2.20.1 更新说明: 1. 修复获取依赖管理列表 2. notify.js 修复 TG_PROXY_AUTH 参数拼接 3. QLAPI.notify larkSecret 参数 4. 修复 cron parser 定时规则校验 5. 修复设置 baseUrl 后无法访问 6. 修复环境变量排序 7. 修复定时任务无法停止 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR <容器名> -> debian 版本同步更新 版本镜像: 正式版: whyour/qinglong:latest Python3.10 正式版: whyour/qinglong:pyt…
💩29🤡3🤩1🥰1
青龙 v2.20.0 更新说明: 1. 定时任务(cron / task)相关的大量修复 & 增强 • 修复 cron 解析错误(修复 parse cron / 升级 cron-parser) • 修复集群模式下定时任务可能不执行(race condition) • 定时任务支持订阅筛选 • 定时任务支持排序调整 • 定时任务支持自定义日志文件或无日志 • 修复任务实例默认值 • 任务支持单实例 / 多实例模式 • 修复 task 命令软链可能失败问题 2. 日志系统相关的大更新 • 修复日志目录逻辑 • 修复 pm2 日志目录 • 优化日志写入(stream pooling) 3. 环境变量(env)系统的改进与修复 • 修复环境变量复制到剪贴板时可能失败 • 添加环境变量“置顶”功能 • 修复 QlPort 与 QlGrpcPort 环境变量在 host network 模式下被忽略 • 增加全局 SSH 私钥配置 …
🥰28👏3
青龙 v2.19.2 更新说明: 1. 备份数据支持选择模块,支持清除依赖缓存 2. QLAPI 和 openapi 的 systemNotify 支持自定义通知类型和参数。 查看 3. ntfy 增加可选的认证与用户动作,感谢 https://github.com/liheji 4. 修复取消安装依赖 5. 修复环境变量过大解析报错 6. 修改服务启动方式 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR <容器名> -> debian 版本同步更新 版本镜像: 正式版: whyour/qinglong:latest Python3.10 正式版: whyour/…
🥴8🥰7👏4😁1
青龙 v2.19.1 更新说明: 1. 修复依赖是否安装检查逻辑 2. 修复文件下载 path 参数 3. 修复 python 查询逻辑 4. 修复任务视图状态筛选 5. 修复创建脚本可能失败 6. 修复重置用户名失败 7. 修复无法识别 python 依赖安装的命令 8. 其他缺陷修复 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR <容器名> -> debian 版本同步更新 版本镜像: 正式版: whyour/qinglong:latest Python3.10 正式版: whyour/qinglong:python3.10 debian 版: whyour…
🥰4🎉1
Showing the 12 most recent of 25 posts we hold for @jiao_long. 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.
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.
Named by 1 registered channel — 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.
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.
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.
“蛟龙” (@jiao_long), 32,874 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/jiao_long.
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.