<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EstiloCorreo17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=ES-UY link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I
want understanding, negotiations, solutions, not fights.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>For
my part, congratulations, dear Keith.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Best
73, Jose<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=ES style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></b><span
lang=ES style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Dxspider-support
[mailto:dxspider-support-bounces@tobit.co.uk] <b>En nombre de </b>Keith, G6NHU
via Dxspider-support<br>
<b>Enviado el:</b> martes, 18 de marzo de 2025 10:48<br>
<b>Para:</b> The DXSpider Support list<br>
<b>CC:</b> Keith, G6NHU<br>
<b>Asunto:</b> [Dxspider-support] An update about HamAward.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div name=messageBodySection>
<div>
<p class=MsoNormal>All,<br>
<br>
A couple of weeks ago, I decided to approach the HamAward people independently
to see if we could come to some solution for the current problem, much the same
way I did with the HamClock developer about 18 months ago.<br>
<br>
Once I'd made contact with them, I was introduced to one of their developers
and we've been talking. Knowing how we handled the initial spots earlier this
year and the actions they took was quite eye opening. Part of their process was
to check that each spot appeared on the network in various places after it was
submitted and if it didn't show, an automatic process would be taken to re-push
the spot through. This was a big part of the problem.<br>
<br>
We talked at length, I proposed a solution and it's been implemented and
running for a week or so now. The process I described above regarding
re-pushing a spot has been removed completely.<br>
<br>
They've set up a new node using the current build of dxspider with the callsign
IW1FRU-74 and at the moment, it has just one connection into the network, to my
G6NHU-2 node.<br>
<br>
When their activators hit the ‘submit spot' button on their custom software, a
number of checks are made to ensure the validity of the sender and when they
last submitted a spot. This duplication time has been increased to to 15
minutes so the most any activator will be able to spot themselves is four times
an hour. Providing these checks are passed, a telnet session is created into
their node and the spot is sent. <br>
<br>
This has been running for nearly a week and in all the time I've been keeping
an eye on it, I've not seen one bad spot come through, everything appears to be
working perfectly well. You can do an rcmd command to IW1FRU-74 and check to
see who's logged on and active at any time, and you can enter 'sh/dx origin
iw1fru-74' on your own node to see the spots that have been submitted from
them.<br>
<br>
I know some sysops won't be happy that I've been talking to an organisation
that's been considered the enemy for a few months but my logic is simple. I
want good, reliable and accurate spots on my cluster, and I want to know these
spots are genuine. I think that this is a good solution for all sides.<br>
<br>
73 Keith.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>