If the connection to AGW goes away or AGW is not loaded when dxspider starts
up, then there was no retry mechanism for restarting the connection. Now
it will try to connect every 30 seconds if AGW is enabled and there is no
connection present.
Which is a big can of worms. Had a good shift around and changed
set/user to be a real command (rather than an alias), renamed the
existing command (which on I use) to set/uservar and sorted the
Aliases so that unset/node still works.
This involves making sure that the timestamp is within 15 mins of "now"
to be accepted. This has other rollover effects in that I don't send an
"old" C record on startup anymore, just send an A record followed by a K.
These days a newly minted C record will be along in 15mins or so anyway.
Made sh/newc terminal width aware.
Added CTY-1709 cty.dat data.
You will need IO::Socket::INET6 to use INET6 capability.
Also I have enabled PC92 slugging and set it to 1 minute as default.
Also I have put code in to handle empty first node slots in PC92.
Since the beginning I have had set/isolate be unidirection, so that I could
see the far node's config, but he could not see mine. This is too confusing
for yer modern sysop and I have now made it such that only the local configs
are remembered, regardless of what is sent back to me. I.e. it is now
symmetric and bidirectional.
This should stop pc93 conversions which are sent out a) being redisplayed
and b) as SYSOP. It may also stop all these strange chat messages to
unlikely chat group names.
Also rewritten chat import routines for new regime.
Also use a big enough past age limit to cope with inactive nodes
that only output a config record and nowt much else, so that they
don't time out.
Add an 'id too far in the future' compared with current systime
check.