[Dxspider-support] ARRL contest dumped spots?

[Rudy Bakalov]

There are many ways to skin the cat. One option that has not been discussed is to implement the same approach as the one for RBN spots.

At the skimmer level, spots are not generated unless the software “hears” the same call several times. Calls are also validated again the check partial database that is regularly updated. At the cluster level, the spot is not considered valid unless confirmed by several spotters. The picture becomes even more clear when SSIDs are stripped out and the analysis uses only the base spotter callsign.

This approach is more computationally intensive, but more realistic in real life compared to requiring everyone everywhere to use passwords. It also determines the quality of the spot based on the spot itself rather than origin of the spot.

Rudy N2WQ

Sent using a tiny keyboard.  Please excuse brevity, typos, or inappropriate autocorrect.


> On Mar 1, 2025, at 2:13 AM, Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> 
> If this were Reddit, I’d get downvoted by some people for saying this but I’m going to say it anyway. 
>  
> If VE7CC does not pass his list of connected users as part of the protocol, there is no way to verify the spots are coming from genuine users. 
>  
> Therefore for the security of the network, VE7CC should update his software to something which does provide user verification or enable this option within his own software. 
>  
> Backwards compatibility can only go so far.  I now strongly feel that any node which can’t provide this kind of user verification should be effectively disconnected from the network until they can comply.  We have to be able to verify spots are being submitted genuinely by the callsign attached to them. 
>  
> 73 Keith. 
>> On 1 Mar 2025 at 04:09 +0000, Rene Olsen via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:
>> Hi.
>> 
>> I am not good at all those fance grep lines and what not, but just looking at watchdbg, I can
>> see a LOT of spots being dumped.
>> 
>> 04:02:19 (*) PCPROT: Bad Spot IB9A on 7179.0 by K3CT(216.126.9.169)@NC7J User K3CT
>> not on node NC7J, DUMPED via DO5SSB-2 92 hops
>> 04:02:35 (*) PCPROT: Bad Spot KL5DX on 14326.5 by KI6RRN/KL7(98.97.64.140)@VE7CC-1
>> User KI6RRN/KL7 not on node VE7CC-1, DUMPED via DO5SSB-2 95 hops
>> 04:02:39 (*) PCPROT: Bad Spot ED8W on 7177.1 by WB2WPM(67.247.211.43)@VE7CC-1
>> User WB2WPM not on node VE7CC-1, DUMPED via DO5SSB-2 95 hops
>> 
>> And it just goes on and on.
>> 
>> Also when looking at MRTG normally when a contest starts, there is a huge jump in number of
>> spots.
>> 
>> This time the jump is very minimal.
>> 
>> Could of course be there just isn't as many spots as usual in a contest.
>> 
>> Are we sure that our "map" of who is connected where is 100% correct.
>> 
>> Anyway. I just saw that a lot of spots were dumped, and wondered if it could really be correct.
>> 
>> Vy 73 de Rene / OZ1LQH
>> 
>> 
>> 
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support