再见🫡
😱290😭141🫡57🤡20🕊10😢6❤2🤬2
Signed Dylan
Channel
@dylan_jdpro
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
9,487subscribers
-546 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001745768919 |
|---|---|
| Type | Channel |
| Username | @dylan_jdpro |
| Created | 26 May 2022 — measured — dated from the channel’s first post |
| First recorded | 10 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/dylan_jdpro |
Hacking & security — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 17 Nov 2026, 07:11 | 9,487 | -21 |
| 11 Nov 2026, 21:49 | 9,508 | -14 |
| 7 Nov 2026, 19:47 | 9,522 | -24 |
| 5 Nov 2026, 02:09 | 9,546 | -16 |
| 2 Nov 2026, 05:27 | 9,562 | -16 |
| 29 Oct 2026, 18:40 | 9,578 | -28 |
| 26 Oct 2026, 13:26 | 9,606 | -18 |
| 23 Oct 2026, 18:10 | 9,624 | -15 |
| 20 Oct 2026, 20:09 | 9,639 | -20 |
| 17 Oct 2026, 10:55 | 9,659 | -10 |
| 14 Oct 2026, 09:06 | 9,669 | -20 |
| 11 Oct 2026, 04:00 | 9,689 | -57 |
| 5 Oct 2026, 04:21 | 9,746 | -75 |
| 26 Sept 2026, 13:56 | 9,821 | -145 |
| 17 Sept 2026, 12:42 | 9,966 | -58 |
| 15 Sept 2026, 12:21 | 10,024 | -5 |
| 13 Sept 2026, 21:39 | 10,029 | -3 |
| 12 Sept 2026, 03:41 | 10,032 | -1 |
| 10 Sept 2026, 01:22 | 10,033 | first reading |
15 posts held, back to 26 May 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 38 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 15 posts for this entry, the most recent from 17 September 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 21 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.
929 reactions across 11 posts, in 14 distinct kinds. The most used accounts for 31.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 290 | 31.2% | |
| 👍 | 219 | 23.6% | |
| 😭 | 141 | 15.2% | |
| ❤ | 121 | 13.0% | |
| 🫡 | 57 | 6.14% | |
| 🤡 | 55 | 5.92% | |
| 😁 | 12 | 1.29% | |
| 🕊 | 10 | 1.08% | |
| 🥰 | 7 | 0.753% | |
| 👎 | 6 | 0.646% | |
| 😢 | 6 | 0.646% | |
| 👏 | 2 | 0.215% | |
| 🤬 | 2 | 0.215% | |
| 😨 | 1 | 0.108% |
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 11 of the 15 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 929 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 26 May 2022 to 17 September 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.
再见🫡
😱290😭141🫡57🤡20🕊10😢6❤2🤬2
Signed Dylan
Channel name was changed to «jdpro»
💀青龙2.20.2之前版本就不要开外网了,有漏洞会被他人改密登录偷家
👍42🤡19❤5👏2
Signed Dylan
代理API模式变量 DY_RETRYKEY='无法|太多了' 切换ip关键词,多个|分隔,默认火爆切换 DY_PROXY='URL1#URL2' 多个#分割 PERMIT_API='test' 需要走API代理的js关键词,多个&分割,可不设置,支持的js都会走 DY_PROXY_RENUM='5' 获取IP失败重试次数 DY_PROXY_REDELAY='3' 获取失败重试间隔 单位秒
❤17
Signed Dylan
🔊 拉库加速换(正常拉的无视),拉不了就直接不用代理,现在代理也经常拉不了 js.googo.win
❤14🤡10👍8
Signed Dylan
变量BANPIN禁止某pin执行任务 变量ALLOWPIN只执行某pin执行任务 多个任务同pin:任务1|任务2@pin1,pin2 多个任务不同pin:任务1@pin,pin2&任务2@pin2,pin3 不指定任务只写pin 全部任务
👍11❤10🤡6
Signed Dylan
抓CK,安全和方便不能兼得!
👍46❤10😁5
Signed Dylan
农场和种豆先跑任务,助力才会有互助码
❤8👍7👎1
Signed Dylan
1、代理池模式支持全部js脚 DP_POOL='http://xxx' 代理池url PERMIT_JS='farm&plant&opencard' 需要走代理池的js关键词,多个&分割,必须设置 2、代理API模式部分支持 DY_RETRYKEY='无法|太多了' 切换ip关键词,默认火爆切换 DY_PROXY='URL1#URL2' 多个#分割 PERMIT_API='test' 需要走API代理的js关键词,多个&分割,可不设置,支持的js都会走 DY_PROXY_RENUM='5' 获取IP失败重试次数 DY_PROXY_REDELAY='3' 获取失败重试间隔 单位秒
❤12👍10
Signed Dylan
限ip越来越狠,几个白嫖代理聊胜于无 嫖二 每天1000 嫖三 签到满2000兑换
👍14❤9🥰1
Signed Dylan
拉库失败或更新不出新任务,执行 拉库|更新问题修复 任务; 没有这个任务就手动删除青龙repo下的库目录再拉;
👍8❤2
Signed Dylan
jdpro pinned «项目地址:https://github.com/6dylan6/jdpro 加群:https://t.me/+FrLpTZlvRa4zYTY1 —拉库指北— 国内机(含代理): ql repo https://js.googo.win/https://github.com/6dylan6/jdpro.git "jd_|jx_|jddj_" "backUp" "^jd[^_]|USER|JD|function|sendNotify|utils" 如果拉不动,自行寻找可用拉库代理,或者用无代理试试 无代理:…»
Showing the 12 most recent of 15 posts we hold for @dylan_jdpro. 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.
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 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“jdpro” (@dylan_jdpro), 9,487 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/dylan_jdpro.
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.