Channel
@jiao_long
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
33,233subscribers
-80 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 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/jiao_long |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 06:33 | 33,233 | -3 |
| 26 Aug 2026, 08:55 | 33,236 | -3 |
| 25 Aug 2026, 08:35 | 33,239 | -7 |
| 24 Aug 2026, 06:52 | 33,246 | -2 |
| 22 Aug 2026, 17:54 | 33,248 | -5 |
| 21 Aug 2026, 08:42 | 33,253 | -6 |
| 20 Aug 2026, 10:47 | 33,259 | -4 |
| 19 Aug 2026, 11:07 | 33,263 | -4 |
| 18 Aug 2026, 10:46 | 33,267 | -7 |
| 17 Aug 2026, 09:28 | 33,274 | -8 |
| 15 Aug 2026, 19:03 | 33,282 | -5 |
| 14 Aug 2026, 10:35 | 33,287 | -15 |
| 13 Aug 2026, 03:46 | 33,302 | +3 |
| 12 Aug 2026, 06:02 | 33,299 | -7 |
| 11 Aug 2026, 06:21 | 33,306 | +1 |
| 10 Aug 2026, 03:30 | 33,305 | -5 |
| 9 Aug 2026, 05:02 | 33,310 | -1 |
| 8 Aug 2026, 01:21 | 33,311 | -2 |
| 7 Aug 2026, 01:30 | 33,313 | no change |
| 7 Aug 2026, 01:22 | 33,313 | first reading |
20 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 45 pagesof 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 19 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 27 August 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.
484 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 31.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 153 | 31.6% | |
| 💩 | 94 | 19.4% | |
| 👏 | 89 | 18.4% | |
| 🥰 | 79 | 16.3% | |
| 🎉 | 22 | 4.55% | |
| 🤣 | 20 | 4.13% | |
| 🥴 | 10 | 2.07% | |
| 🤔 | 9 | 1.86% | |
| 🥱 | 5 | 1.03% | |
| 😁 | 2 | 0.413% | |
| 🤩 | 1 | 0.207% |
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 20 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 484reactions 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 14 June 2024 to 19 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.
青龙 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…
👏24🤡12🤣5💩2🥰2
👍项目推荐👍 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…
💩28🤡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
青龙 v2.19.0 更新说明: 1. 缓存 node 和 python 依赖 2. 减少启动服务数，节约启动内存约 50% 3. 邮箱通知支持多个收件人 4. boot 任务改为在依赖安装完成后执行 5. 修复脚本管理查询子目录逻辑 6. 修复脚本管理增加文件夹 7. 修复 QLAPI 修复环境变量 remarks 8. 修复 mjs 依赖查不到 9. 修复无法删除日志文件 其他说明: 1. [非必须] 缓存 linux 依赖需要手动增加映射目录，debian 镜像映射目录 ./data/dep_cache/apt/archives:/var/cache/apt/archives， latest 镜像映射目录 ./data/dep_cache/apk/cache:/var/cache/apk 2. 此版本启动逻辑改动较大，需要删除容器，用最新镜像启动新容器，或者使用更新方法中 宿主机更新 方式更新 更新方法: ->…
🥰3💩2🎉1
青龙 v2.18.3 更新说明: 1. 脚本管理和日志管理支持下载脚本和日志 2. 修复 gRPC client 连接超时 3. 脚本管理增加强制打开文件 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 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-python…
👏3🥰2
青龙 v2.18.2 更新说明: 1. 定时任务支持 开机运行@boot 和 手动运行@once 任务 2. 脚本管理增加可预览检查，避免无法预览文件被重复保存 3. 系统设置增加时区设置 4. 修复登录失败没有提示 5. 增加重置密码命令 ql resetpwd test-passward 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/qinglong:pyt…
🥰4👏1
青龙 v2.18.1 更新说明: 1. 内置 QLAPI 增加环境变量和系统通知 api，详情见 https://qinglong.online/guide/user-guide/built-in-api 2. 移除 nedb 和 sentry，不再支持 2.10.x 版本自动迁移 3. 修复 JavaScript telegram 通知有代理时超时 4. 修复多语言翻译 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 ql update -> 宿主机更新 docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR <容器名> -> debian 版本同步更新 版本镜像: 正式版: whyour/qinglong:latest Python3.10 正式版: …
青龙 v2.18.0 更新说明: 1. 修改认证信息存储方式，不再使用 auth.json 存储 2. 修复初始化 SystemConfig 数据 3. 修改通知文件未设置时提示 4. 修复配置文件更新可能异常 其他说明： 由于安全问题，强烈建议更新 更新方法: -> 面板更新 系统设置 -> 其他设置 -> 检查更新 -> 容器内更新 执行 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 …
👏5🤡3🎉1
Showing the 12 most recent of 20 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.
Citation-graph rank — 446,808 of 1,621,120entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“蛟龙” (@jiao_long), 33,233 subscribers as measured 27 August 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.