How qitoqito/psyduck works
PsyDuck is a configurable JD activity-task runner for Qinglong. A user invokes a task through main.js; it dynamically loads the matching parser task and initializes it with command-line parameters. The README documents account selection, timing, concurrency, caching, proxy options, and notifications as framework capabilities. The source excerpts confirm task dispatch, Qinglong management, and file decryption, but do not show how task implementations connect to most shared utilities or integrations; those links are therefore omitted.
Main entry points: common.js Common utilities · qlCreate.js Qinglong manager · main.js Task entry · jd Activity tasks
Components 16
Task execution
- Task entry
main.js - Profiles
config/profile.js
JD activities
- Activity tasks
parse/jd
Framework services
- Common utilities
util/common.js - Relay proxy
util/relayProxy.js - User agents
util/userAgent.js - JD algorithms
util/jdAlgo.js - H5ST signing
static/h5st/5.2.6.js - Account cache
util/cache.js - Notifications
util/message.js
Qinglong management
- File decryption
fileCrypto.js - Qinglong manager
qlCreate.js
Other components
- Operator
- Qinglong panel
- Redis cache
- JD services
Connections 8
- Operator → Task entry: runs task
- Task entry → Activity tasks: loads task
main.js - Common utilities → Relay proxy: imports
util/common.js - Common utilities → User agents: imports
util/common.js - Qinglong manager → File decryption: decrypts files
qlCreate.js - Qinglong manager → Qinglong panel: manages tasks
qlCreate.js - Activity tasks → JD services: runs activities
- Account cache → Redis cache: stores cache