<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Please upgrade to the latest version in
git. If you are not running a version derived from the git
repository then please carry out the actions under the heading
"Git" on this page: <a class="moz-txt-link-freetext" href="http://www.dxcluster.org/download/">http://www.dxcluster.org/download/</a><br>
<br>
Just to to repeat myself, but in other words (I do that), do a
'git pull' before you start. The instructions are located in the
file /spider/UPGRADE.mojo.<br>
<br>
For those wandering whether to "jump", the instructions are
attached.<br>
<br>
Dirk G1TLH<br>
<br>
On 15/06/18 22:15, Ron Gibson via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8a7b3ed2-1007-fb80-b9d5-d830e97a018e@sympatico.ca">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Hi Dirk,<br>
Can we have a reminder as to how to switch to the mojo branch?<br>
Ron<br>
VE3CGR<br>
<br>
<div class="moz-cite-prefix">On 6/12/2018 6:31 PM, djk via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:095f2a01-e399-867d-7a5e-f224f4b44e48@tobit.co.uk">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p>The program rbn.pl is just a simple test program that does
some deduping and a certain amount of checking. There room for
improvement, most of which could be made easier by
incorporating it into the main DXSpider code. Work which I
have started doing but, owing to personal circumstances, has
had to take a back seat until (probably) beginning of July. I
have started to put some stubs in already, but there are a
number of issues that I would like to get some guidance on -
here are my current views :</p>
<ul>
<li>RBN spots should always be local - meaning that they are
not distributed on the cluster - this implies that each node
(that wants to handle them) will need to make a connection
to the RBN. Note: any spots ending in -# will be dropped by
existing DXSpider nodes so, in fact, it would require a
network wide upgrade to distribute them anyway.</li>
<li>When the node has established a connection to the RBN,
users should have actively opt in and have a set of RBN
specific filter rules separate from the spot rules. <br>
</li>
<li>Having access to all this realtime signal strength info
should allow some enhanced propagation prediction. Is anyone
interested in this sort of thing and, if so (given that the
prediction is regarded as good) how is to be used by (or
communicated to) users?</li>
<li>Some time ago one of my sysops wrote a program to provide
himself with SMS notifications of spots or conditions that
he was interested in using the filtered output from a
connection to a node. Given that there other means, these
days, of informing users on mobile phones that might be
cheaper - should be looking this? Twitter, Signal or some
other mechanism?<br>
</li>
<li>The mojo branch can be considered mature, if not
"finished". Any new features will appear on this branch
which will appear, somewhen, as DXSpider version 2. <br>
</li>
</ul>
<p>Discuss. <br>
</p>
<p>Open to any reasonable suggestions.</p>
<p>Dirk G1TLH<br>
</p>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>