origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,NH
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
+ by_state <states>
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
or
acc/ann by G,M,2
+for american states
+
+ acc/ann by_state va,nh,ri,nh
+
You can use the tag 'all' to accept everything eg:
acc/ann all
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,NH
origin <prefixes> really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,NH
some examples:-
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+you can now use 'by' as a synonym for 'call' so:
+
+ by = call
+ by_dxcc = call_dxcc
+
+and so on
+
You can use the tag 'all' to accept everything eg:
acc/route all
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
+'call' means the callsign that has spotted 'by' whoever.
+
For frequencies, you can use any of the band names defined in
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
acc/spot 3 all
+for US states
+
+ acc/spots by_state VA,NH,RI,MA,ME
+
but this probably for advanced users...
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
necessary to traverse the network(s) to logon to the cluster <callsign>.
+=== 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
+This command will completely remove a one or more callsigns
+from the US States database.
+
+There is NO SECOND CHANCE.
+
+It goes without saying that you should use this command CAREFULLY!
+
+Note that these callsign may be re-instated by any weekly updates from
+the FCC.
+
=== 9^DELETE/USER <callsign> ...^Delete this user from the User Database
This command will completely remove a one or more users from the database.
means gimme it).
The important thing to remember is that if you specify a 'reject'
-filter (all the lines in it say 'reject/spots' (for instance) then if
+filter (all the lines in it say 'reject/spots' (for instance)) then if
a spot comes in that doesn't match any of the lines then you will get
it BUT if you specify an 'accept' filter then any spots that don't
match are dumped. For example if I have a one line accept filter:-
don't try this at home until you can analyse the results that you get
without ringing up the sysop for help.
+Another useful addition now is filtering by US state
+
+ accept/spots by_state VA,NH,RI,ME
+
You can arrange your filter lines into logical units, either for your
own understanding or simply convenience. I have one set frequently:-
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
+'call' means the callsign that has spotted 'by' whoever.
+
For frequencies, you can use any of the band names defined in
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
origin <prefixes> really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,ME
some examples:-
rej/route all (equiv to [very] restricted mode)
+as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
+
=== 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
=== 0^SET/TALK^Allow TALK messages to come out on your terminal
=== 0^UNSET/TALK^Stop TALK messages coming out on your terminal
+=== 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
+This command allows you to add or alter a callsign in the US state
+database. Use with extreme caution. Anything you do here will be
+overwritten by any weekly updates that affect this callsign
+
+ set/usdb g1tlh nh downtown rindge
+
+see also DELETE/USDB
+
=== 0^SET/WCY^Allow WCY messages to come out on your terminal
=== 0^UNSET/WCY^Stop WCY messages coming out on your terminal
=== 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
Show the HF DX spots breakdown by band for the last 31 days
-=== 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
-Show the HF DX Spotter table for your country for the last 31 days
+=== 0^SHOW/HFTABLE [prefix ...]^Show the HF DX Spotter Table
+Show the HF DX Spotter table for the list of prefixes for the last 31 days,
+if there are no prefixes then it will show the table for your country.
+
+Remember that some countries have more than one "DXCC country" in them
+(eg G :-), to show them (assuming you are not in G already which is
+specially treated in the code) you must list all the relevant prefixes
+
+ sh/hftable g gm gd gi gj gw gu
+
+Note that the prefixes are converted into country codes so you don't have
+to list all possible prefixes for each country.
=== 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+=== 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
+Show the City and State of a Callsign held on the FCC database if
+his is being run on this system, eg:-
+
+ sh/usdb k1xx
+
=== 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
Show the VHF DX spots breakdown by band for the last 31 days
-=== 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
-Show the VHF DX Spotter table for your country for the last 31 days
+=== 0^SHOW/VHFTABLE [prefix ...]^Show the VHF DX Spotter Table
+Show the VHF DX Spotter table for the list of prefixes for the last 31 days,
+if there are no prefixes then it will show the table for your country.
+
+Remember that some countries have more than one "DXCC country" in them
+(eg G :-), to show them (assuming you are not in G already which is
+specially treated in the code) you must list all the relevant prefixes
+
+ sh/vhftable g gm gd gi gj gw gu
+
+Note that the prefixes are converted into country codes so you don't have
+to list all possible prefixes for each country.
=== 0^SHOW/WCY^Show last 10 WCY broadcasts
=== 0^SHOW/WCY <n>^Show last <n> WCY broadcasts