On 16 June 2010 21:55, Lee Sawkins <span dir="ltr"><<a href="mailto:ve7cc@shaw.ca">ve7cc@shaw.ca</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Is it better to stop some of the abusers or to not do anything and let them all get away with it? My system isn't perfect, but it does catch many bad spots.<br></blockquote><div><br>As do others<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<br>
<br>
My software automatically adds IPs to the bad list. There is a time to live for these addresses. After a while they expire. Every few days I go through the list and look at the spots that have been dropped. Even if a few spots are dropped in error, there are so many duplicate spots it really doesn't make much difference. How many 3C0 spots have you seen? Do you really need the one that makes obscene comments about the operators, even if it gives the correct frequency and call. Do you need spots that call others Nazis or killers or terrorists? Some sysops apparently think these spots are ok as long as they aren't entered on their cluster.<br>
</blockquote><div><br>The way forward is registration. You will not see anything like that from my clusters. Do I think they are OK posted on other clusters? No! However, using IP addresses to stop the problem is a complete waste of time and will cause more problems with disgruntled users than it solves. What we actually need are sysops who check their systems regularly and don't expect the software to do it all for them.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Some abusers have fixed IPs and have been putting out bogus spots for years. These spots may not be obscene, but they are dropped. Some of these are users are putting out self-spots using hundreds of different calls. Every day with different calls. If the system is full of bogus spots like this, how can you trust any of them to be valid. A spot for a UA0 from Florida on a dead band is very misleading.<br>
</blockquote><div><br>So what are the callsigns involved? Tell us and we can deal with it very easily. It takes seconds to do. Trying to regulate the cluster with a stick is not the way forward. What we need is education. I try to help my users and explain to them why correct procedure is important. If I were to spot any wrongdoings from either of my clusters I would take a very dim view indeed of it and would have words with the person involved. I take my responsibilities as a sysop very seriously.<br>
<br>In this day and age, simply trying to catch everything with software is a losing battle. Look at DXSummit as a prime example. At least they now have a login procedure and this has made a huge difference. We have to make the effort to protect the system by ensuring the security of our users as much as possible. While that only works on our nodes, it is all we can do with current protocols. I would go as far as saying that if a user is registered on a cluster node, that information should be shared securely in some way with the network to make sure a malicious user could not use anothers login.<br>
<br>73 Ian<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Lee<div class="im"><br>
<br>
----- Original Message ----- From: "Robert Chalmas" <<a href="mailto:rcbza10@hb9bza.net" target="_blank">rcbza10@hb9bza.net</a>><br></div>
To: "The DXSpider Support list" <<a href="mailto:dxspider-support@dxcluster.org" target="_blank">dxspider-support@dxcluster.org</a>><br>
Sent: Wednesday, June 16, 2010 12:54 PM<div class="im"><br>
Subject: Re: [Dxspider-support] ROS Mode<br>
<br>
<br>
</div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
>It would be much easier to make<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
as list of abuser's IP addresses and drop their spots no matter where<br>
they came from.<br>
</blockquote>
<br>
Well, what do you do with dynamic IP addresses?<br>
<br>
On my side, my IP address on the WAN side is forced to a new value after a maximum of 20 hours and this is the same with all ADSL (and cable? not 100% sure) users in my country (and many others I believe, with just a different time interval), except a few ones who agree to pay an extra fee for a fixed IP address.<br>
<br>
Even worse, if I would misbehave right now and you would put me on your IP addresses blacklist, my current address could be reattributed tomorrow to an honest user who would be blocked without having done anything wrong. And I would be able to continue "cluster spamming" with my new address!<br>
<br>
73's<br>
<br>
Robert - HB9BZA<br>
<br>
-- <br>
Robert CHALMAS, PO Box 1225, CH-1227 Carouge/GE, SWITZERLAND<br>
Free DX-Cluster client RXCLUS: <a href="http://www.hb9bza.net/rxclus" target="_blank">http://www.hb9bza.net/rxclus</a><br>
Unofficial LoTW users list: <a href="http://www.hb9bza.net/lotw" target="_blank">http://www.hb9bza.net/lotw</a><br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a><br>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a> <br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a><br>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</div></div></blockquote></div><br>