[Dxspider-support] An update about HamAward.
Dirk Koopman
djk at tobit.co.uk
Wed Mar 19 16:22:35 GMT 2025
On 19/03/2025 15:59, Lorenzo IU1NSA via Dxspider-support wrote:
>
> To fix this, we corrected the typo in the code by replacing:
>
> $DXProt::pc92_ad_enable
>
> with:
>
> $DXProt::pc92_ad_enabled
>
> Alternatively, we also tested disabling the slugging feature entirely
> by setting:
>
> $DXProt::pc92_slug_changes = 0;
Thank you for reporting this. It has been corrected and is available in
the release candidate in the test branch.
As for $DXProt::pc92_slug_changes = 0, where you are in control of the
connections from your web system, this probably makes no real
difference. This is there to discourage the annoying habit of certain
user program "sniping" a spot into the system. When it was written
senderverify wasn't a usable thing - which now, likely, has the same
effect, but puts the onus on one's node partners to deal with the spot.
"PC92_slug_changes" puts a delay in such that the PC92 A can go out
before the spot. This was because certain actors thought it a jolly jape
to send any old spot out - scot free and unaccountably. Personally, I
would leave a small value in there to make sure that the PC92 A still
goes out before the spot.
73 Dirk G1TLH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250319/c2b77dc8/attachment.htm>
More information about the Dxspider-support
mailing list