<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/03/2025 15:59, Lorenzo IU1NSA via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9bd09cb9843b899543a84e36d8ab1b3b@haminnovation.com"><br>
To fix this, we corrected the typo in the code by replacing:
<br>
<br>
$<a class="moz-txt-link-freetext" href="DXProt::pc92_ad_enable"
moz-do-not-send="true">DXProt::pc92_ad_enable</a>
<br>
<br>
with:
<br>
<br>
$<a class="moz-txt-link-freetext" href="DXProt::pc92_ad_enabled"
moz-do-not-send="true">DXProt::pc92_ad_enabled</a>
<br>
<br>
Alternatively, we also tested disabling the slugging feature
entirely by setting:
<br>
<br>
$<a class="moz-txt-link-freetext" href="DXProt::pc92_slug_changes"
moz-do-not-send="true">DXProt::pc92_slug_changes</a> = 0;
<br>
</blockquote>
<br>
<font size="4">Thank you for reporting this. It has been corrected
and is available in the release candidate in the test branch. <br>
<br>
As for $<a class="moz-txt-link-freetext"
href="DXProt::pc92_slug_changes">DXProt::pc92_slug_changes</a> =
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. <br>
<br>
73 Dirk G1TLH</font><br>
</body>
</html>