<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The user can't turn off this auto-spot feature. No where in the
documentation (FAQ or User Guide) is the Cluster even mentioned.<br>
<br>
Reviewing the limited options within the program, I could find no
option to turn this on or off. It appears to be enabled by default.<br>
<br>
It looks to me that the ROS author is trying to make the spots appear
to be human generated by using a different comment string (some give a
db report, others tnx, 73, etc) and using different Cluster Nodes. <br>
<br>
It is just spamming the Network and gives the non-ROS user viewing the
Cluster, the impression that it is a popular and widespread mode.<br>
<br>
de Laurie, VK3AMA<br>
<br>
<br>
On 9/07/2010 8:07 PM, Brendan Minish wrote:
<blockquote cite="mid:1278670036.3735.77.camel@localhost.localdomain"
type="cite">
<pre wrap="">Can the user disable this auto-spot feature and is it enabled by
default ?
On Fri, 2010-07-09 at 19:55 +1000, VK3AMA wrote:
</pre>
<blockquote type="cite">
<pre wrap="">This auto-spot (when logging a qso) behaviour was happening today when
I tested ver 4.5.7 & latest ver 4.5.9
The previous flooding of the cluster (few weeks ago) occurred when the
ROS software auto-spotted everything it decoded and used the one
Cluster Node. That is what the deleted thread on the ROS site was
about.
de Laurie, VK3AMA
On 9/07/2010 7:22 PM, Brendan Minish wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Can anyone confirm if the latest version of ROS still auto-spots ?
the author of ROS deleted the thread about abusive cluster behaviour,
when I asked about this I was told 'The thread has been deleted because
the problem is fixed'
On Fri, 2010-07-09 at 10:45 +0200, SM6U, Rickard wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi, thanks for the information. I've been noticing lots of rapid connect and disconnects lately, wich I found strange since our cluster is just a shell for the webcluster.
Is it just me, or are most of the "targeted" clusters thoose who discussed the ROS-problem last time?
Will badword ROS asap and theb set up for registered users only when I return home from the SK9HQ event. Hope to work you during the weekend!
/SM6U, Rick
sector7.nu / sm6.se / sk6aw.net
9 jul 2010 kl. 04:56 skrev VK3AMA <a class="moz-txt-link-rfc2396E"
href="mailto:vk3ama@gmail.com"><vk3ama@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">While researching ROS cluster spots arriving at HamSpots.net via the Cluster, I have discovered how the ROS software is auto-spotting to a list of nodes that may be of concern to the Node Sysops.
The following Spider Node addresses are hard-coded in the software.
dxc.us6iq.com
dxc.ham.hr
9a0dxc.hamradio.hr
remo3.renet.ru
cluster.sk4bw.net
ax25.org
sk3w.se
sector7.nu
sm7gvf.dyndns.org
ROS software establishes a connection at startup using your callsign and varies which node it connects to, not always the same node.
When a qso is logged a spot is auto generated (there is no option in ROS to turn this off that I could find) and the text of the spot is changed based on another hard-coded list of messages. This is obviously done to give the impression that the spot is sent from a human (unlike the past flooding of the network, same text and same node). No where in the ROS FAQ or User Guide is this behaviour documented.
I ran ROS in RX mode today, after a callsign was decoded, I hit the log button and it sent a spot to the cluster without permission with my name and call thanking the other station for the QSO.
A quick review of recent ROS spots shows the same nodes being used and similar style comments.
What other surprises are hidden in this software?
de Laurie, VK3AMA
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>