新增gotify通知: GOTIFY_URL= # Gotify url GOTIFY_TOKEN= # Gotify X-Gotify-Key GOTIFY_PRIORITY=2 # Gotify 推送消息优先级 位置config.ini message节点

Channel
推送鸭
@qitoqito
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
1,016subscribers
+0 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 | -1001514891112 |
|---|---|
| Type | Channel |
| Username | @qitoqito |
| Created | Between 1 August 2021 and 31 March 2023— 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 | 7 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/qitoqito |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 09:07 | 1,016 | +1 |
| 24 Aug 2026, 12:34 | 1,015 | -2 |
| 20 Aug 2026, 13:18 | 1,017 | -1 |
| 17 Aug 2026, 11:36 | 1,018 | -1 |
| 10 Aug 2026, 19:13 | 1,019 | +3 |
| 8 Aug 2026, 03:58 | 1,016 | no change |
| 7 Aug 2026, 05:16 | 1,016 | first reading |
Engagement
20 posts held, back to 6 March 2025 — 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 29.0%
- avg views ÷ 1,016 subscribers
- Avg views / post
- 295
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 held
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 2 August 2026 |
|---|---|
| Posts held | 20 (6 March 2025 – 2 August 2026) |
| Views total | 295 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 05:16 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.
Reaction mix
76 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 57.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 44 | 57.9% | |
| ❤ | 20 | 26.3% | |
| 🔥 | 9 | 11.8% | |
| 🥰 | 2 | 2.63% | |
| 👏 | 1 | 1.32% |
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 15 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 76reactions 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 6 March 2025 to 2 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
关于删本子:最近库里删了一些有豆子的脚本,请蛋定。删掉的基本都是些黑号本和火爆本,像国补和盲盒这些脚本对运行设备有强验证,基本上只要验证信息对不上,运行后会立马黑号。现在只留了些相对安全的本子,一天跑个 60+ 应该没问题。问题本测试后如没问题会重新添加上。 关于一天一失效:如果你的号现在还是一天失效几次,应该是跑了别人家的脚本。这边基本不会有这种问题。 关于 relayApi 和 relayProxy:这些都是吃瓜网友分享的工具包,本身就不是为了跑狗东脚本使用,作者对框架做了死限制。如果你想问自己写的脚本怎么接入,这边没法给你解答,你还是直接去原作者主页提问看看比较快。
👍12
BUG龙一直出BUG 使用外网的用户,要及时关停服务,避免财产损失
❤2
psyduck一键安装: 创建青龙应用 ,权限: 环境变量,定时任务,订阅管理 git clone https://github.com/qitoqito/onekey.git && cd onekey && sh ./psyduck.sh 安装流程: https://github.com/qitoqito/psyduck/blob/main/install.md 刚开始用的可以按照这个安装,已安装的忽略这条推送
👍2❤1
Signed 可达鸭
测试过多次,部分号凌晨跑,极易掉ck,包括打开jdApp 白天运行不会 如果都是大晚上掉ck的,可以调整下定时任务 https://t.me/qitoqito/154
Signed 可达鸭
目前库可使用relayApi提供的新接口 能支持动态TLS指纹模拟,现有libressl模式,浏览指纹都是固定的,很容易被识别 如果想测试使用,可以自行打开config.ini 在global节点处添加 request=true [global] request=true (11.27) 目前已加入随机指纹数据,数据获取应该没有问题
❤2
Signed 可达鸭
如果安装了relayApi 默认是不会开启转发服务的 需要在脚本配置添加 relay=true 如果开启全局转发autoRelay 如部分不想使用, 要在脚本变量添加 relay= false 如想修改全局转发autoRelay config.ini [env] autoRelay=true|false
👍2❤1
Signed 可达鸭
框架已正常接入relayApi服务🙈🙈🙈
❤3👍2🔥2
Signed 可达鸭
新增config配置变量delayTo 脚本生成的定时任务会设置在几点后 已添加的定时任务,需要先删除 [env] delayTo=6 # 6点之后才会跑脚本
Signed 可达鸭
近期调整了parse目录,非bug龙环境 拉库后需执行 node create.js解混淆
👍3
Signed 可达鸭
跳过缓存: 脚本运行过程会记录账户的运行状态,重复执行脚本会跳过已完成的账户 但会遇到部分活动需要重复运行,但是账户状态已在缓存中而无法执行的情况 需要删除缓存,才能继续运行 1. 可使用Redis管理工具 连接Redis服务器,选择DB2(默认db2),找到日志里面的[Key] xxxxx字段,搜索该字段并删除 2. 使用debug字段 在脚本节点处添加 debug=1 重新运行脚本后,记得删除debug=1 3. 命令行操作 task qitoqito_psyduck/main.js jd_task_xxx -debug 1 没有Redis管理工具的,可以使用 https://github.com/qishibo/AnotherRedisDesktopManager/
Signed 可达鸭
大牌token: 使用N1盒子用户,sign服务获取token有部分限制,可以在config.ini env节点处添加 isvObfuscator=true 添加后,将使用脚本预留的form参数请求token (10 token)
Signed 可达鸭
Showing the 12 most recent of 20 posts we hold for @qitoqito. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“推送鸭” (@qitoqito), 1,016 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/qitoqito.
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.