[Dxspider-support] Dedup error?

[Dirk Koopman]

If you remove the delay, then that MAJOR vector of flood attacks opens up again. I cannot stress enough how effective this part of the filtering process is. 

So, what perhaps we should consider is whether to change the default delay or educate the user about how the filter works and encourage him to modify his spotting behaviour. 

There HAS to be a delay. 

Perhaps someone could do some analysis after the contest at the end of the month to determine what an optimum value might be? I am not going to be near a suitable computer. 

It is tunable from the console. 

I understand the concern about corrections but is that more important than flood protection?

73 Dirk

> On 19 May 2025, at 09:50, g4piq via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> 
> I have seen the same thing. Changing frequency does not seem to defeat the dupe spot timer - which I think it should. I know there was a parameter for a minimum frequency shift to count as a new spot which I think got moved down (quite correctly)  from 25 kHz to 1 kHz.
> 
> This also impacts the ability of a user ti correct a spot accidently sent on the wrong frequency before the 5 min timer expires.
> 
> 73
> 
> Andy, G4PIQ 
> 
> 
> 
> Sent from my Galaxy
> 
> 
> -------- Original message --------
> From: Simon Ravnič via Dxspider-support <dxspider-support at tobit.co.uk>
> Date: 19/05/2025 09:22 (GMT+00:00)
> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
> Cc: Simon Ravnič <s53zo at t-2.net>
> Subject: [Dxspider-support] Dedup error?
> 
> Hello,
> 
> my user, S51ZO is often spotting beacons and complained to me that he gets wrong duplicate warnings.
> 
> This is what I found out:
> 2025-05-10 16:03:08 GMT  1296090 S55ZMS/B   -> FORWARD
> 2025-05-10 16:04:30 GMT  1296938 HG3BUB/B   -> FORWARD
> 2025-05-10 16:04:46 GMT  2320090 S55ZMS/B   -> DUPLICATE
> 2025-05-10 16:06:10 GMT  3400090 S55ZMS/B   -> DUPLICATE
> 2025-05-10 16:06:53 GMT  5760885 HG3BSA/B   -> FORWARD
> 2025-05-10 16:07:18 GMT 10368070 S55ZMS/B   -> DUPLICATE
> 2025-05-10 16:09:23 GMT 10368930 HG3BS/B    -> FORWARD
> 2025-05-10 16:09:50 GMT 10368975 HG1BSB/    -> FORWARD
> 2025-05-10 16:14:16 GMT  1296878 9A0BLP/B   -> FORWARD
> 2025-05-10 16:25:33 GMT 10368050 S55ZRS/B   -> FORWARD
> 2025-05-10 16:25:48 GMT  5760045 S55ZRS/B   -> DUPLICATE
> 2025-05-10 16:27:36 GMT 10368018 OE8XXQ/B   -> FORWARD
> 2025-05-10 16:41:14 GMT  3400090 S55ZMS/B   -> FORWARD
> 2025-05-10 16:41:33 GMT  5760045 S55ZRS/B   -> FORWARD
> 2025-05-15 18:15:46 GMT  2320890 HG3BUC/B   -> FORWARD
> 2025-05-15 18:16:35 GMT  5760885 HG3BSA/B   -> FORWARD
> 2025-05-15 18:18:58 GMT 10368930 HG3BSB/B   -> FORWARD
> 2025-05-15 18:20:00 GMT  1296938 HG3BUB/B   -> FORWARD
> 2025-05-15 18:20:59 GMT  1296975 HG1BUB/B   -> FORWARD
> 2025-05-15 18:21:47 GMT  2320975 HG1BUB/B   -> DUPLICATE
> 2025-05-15 18:22:51 GMT  2320975 HG1BUB/B   -> DUPLICATE
> 2025-05-15 18:23:25 GMT 10368975 HG1SB/B    -> FORWARD
> 2025-05-15 18:26:17 GMT  1296090 S55ZMS/B   -> FORWARD
> 2025-05-15 18:26:31 GMT  2320090 S55ZMS/B   -> DUPLICATE
> 2025-05-15 18:26:45 GMT  3400090 S55ZMS/B   -> DUPLICATE
> 2025-05-15 18:27:07 GMT 10368070 S55ZMS/B   -> DUPLICATE
> 
> So it appears that any two spots with the same callsign get compared, regardless of frequency. How long is deduping timer? 
> 
> Is this a bug or a feature? 
> 
> 73
> Simon, S53ZO
> S50DXS sysop
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250520/1354f6c9/attachment-0001.htm>