CHASERS
Ask the OTA bot who has chased your op and is still waiting on your QSL. Send it from the station running your op. The reply is the callsigns of every chaser who you have not confirmed yet. The chasers are sorted with those who have waiting longest first.
When nobody is waiting:
A chaser who has sent their chase message but whose position report has not arrived yet
is not on the list. Once their beacon arrives, OTA relays their call to you as a DE
message and they are eligible to appear in the CHASERS response until your QSL goes out.
A busy op can have more chasers waiting than one APRS message holds. In that scenario the answer comes as two numbered messages. If two messages cannot hold all the chasers the second one ends with the URL to the op’s page, where you can see all the chasers at once. The chasers dropped from the second message are the ones who have waited for the shortest time.
See Host an op for more about working a pileup.
Reference
CHASERS
See who has chased your op and is waiting on your QSL.
Replies
chasers_reply{chasers}chasers_replyNo one is waiting on your QSL.chasers_replymore at aprsota.org/{callsign}/ops/{number}chasers_replyCHASERS! {page}/{pages} {count} {chasers}
Hints
- CHASERS with no live op
CHASERS needs an op on the air. Send HOST to start one.limited to 1 per 24 hours, then silent- CHASERS from a different SSID than the op's
Your op is run by {station}. Send CHASERS from it.limited to 1 per 24 hours, then silent
Machine form
CHASERS!
Every message begins with CHASERS!, then this message's number and the count of messages, then the total number of chasers waiting, then one station call per chaser, longest waiting first. Sent to the station running the op.
- the list, one message per page
CHASERS! {page}/{pages} {count} {chasers}
The grammar every machine form shares is in the handbook's API section.