01
Group posting
Pick a posting list, paste your copy, hit post and walk away. It opens the browser, signs in, and works down the list one group at a time with a pause between each. When it is done you get a reconciliation report: posted, pending approval, failed.
- Flow
- Two-step wizard: choose groups and copy, then set interval and publish mode
- Selection
- Select all, clear all, or quick-pick 10 / 20 / 30 / 50 groups
- Progress
- Live counter of sent N/M, posted, pending, failed, and the group currently being posted to
- Interrupt
- Stop any time; if a job hangs you can force-reset its state
- Posting lists
- Live progress
- One-click stop
- Quick-pick 10–50
- Membership detection
- Run summary
- Force reset
- Auto screenshot on error
10
Throttling & protection
Volume does not help if the account gets restricted. Settings apply across the board, intervals are randomised inside a range instead of a fixed beat, and everything stops overnight.
- Daily cap
- Maximum actions per day, default 50
- Interval
- 30–120 seconds randomised between actions
- Rest
- Fully paused 00:00–07:00 by default
- Posting
- 3 second minimum post interval, group order reshuffled each run, posting and batch jobs on the same account are mutually locked
- Daily action cap
- Randomised interval
- Rest window
- 1 like per author
- Minimum post interval
- Shuffled group order
- Per-account lock
11
Licensing & device transfer
A license key is bound to a hardware ID. Copy it to another machine and it will not run. When someone genuinely needs to move machines, they can transfer it themselves without going through you.
- Binding
- License key validation plus unique machine HWID binding
- Transfer
- Enter user ID and license key, hit transfer, done
- Unbind
- 30 minute cooldown after unbinding before it can bind again, so one key cannot be shuttled between two machines
- Account
- User ID is changeable, once every 30 days
- Key validation
- Unique HWID binding
- Device transfer
- Unbind
- 30 min cooldown
- AES-256 encryption
14
Remote repair & monitoring
When a machine in the field acts up, nobody has to drive out there. The user hits report, a ticket opens, and you connect in from the admin console. The routine ones fix themselves and log what they did.
- Tickets
- Ticket list, ticket detail and assignment history
- Remote
- Connect directly into the client machine to work on it
- Auto-fix
- Auto-repair log; routine issues resolve without anyone stepping in
- Knowledge
- Solved issues go into the knowledge base, with a review queue for learn-as-you-fix entries
- Monitoring
- System monitoring, alert log, AI task tracking, process management and one-click service restart
- Ticket list
- Remote connect
- Auto-repair log
- Knowledge base
- Review queue
- System monitoring
- Alert log
- AI task tracking
- Process management
15
Ecosystem
The program binds to 127.0.0.1 only. Posting credentials stay in your own browser, stored credentials are encrypted on disk. The only traffic that leaves the machine is license validation and version updates, over an encrypted tunnel.
- Alerts
- LINE bot pushes job results and errors in real time
- Cloud
- CLOUDSERVER handles licensing, updates and tickets
- Transport
- Cloudflare named tunnel over HTTPS 443 — no inbound ports opened
- Deployment
- One-click bundle with the runtime included; double-click to start, Stop.bat to stop
- Ports
- If 3000 is taken it rolls forward to 3001, so multiple instances do not collide
- LINE bot notifications
- CLOUDSERVER management
- Cloudflare secure tunnel
- Cross-device sync
- Open API
- One-click installer