[Dxspider-support] New mojo version

[Dirk Koopman]

There is a new mojo version which has been under test by a few brave 
sysops and they have determined that it is stable. Please look at the 
Changes file for the list of issues dealt with.

One of the issues that has become apparent is the random lock status 
(historically) granted to new nodes that appear on the network. For some 
reason they defaulting to "unlocked". I don't understand why this has 
suddenly become a problem AGAIN, but it does seem to affect longer 
running nodes more than newer ones.

This release is an attempt to fix this. It will lock all nodes that are 
not specifically unlocked via explicit unset/lock or set/spider type 
commands. Unfortunately, previous attempts to deal with this may have 
got this all confused and it *MAY* (and I stress this) mean that a 
(very) few of your older node partners *MIGHT* get locked out. If this 
happens then simply unset/lock or set/spider any of these nodes manually.

There is new spot deduping code which seems to reduce the number of 
dupes, but since I have not been able to reproduce this further than 
making sure that nodes that issue multiple dupe spots with the same 
sequence number don't cause dupes.

73 Dirk G1TLH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240919/aa9c34c8/attachment.htm>