[Dxspider-support] build 608 =?utf-8?Q?=3D=3Futf-8=3FQ=3F=3DE2=3D80=3D9CSorry=3D2C=5F=3F=3Dthis_?=is a duplicate”

[Keith, G6NHU]

Can we get an English translation of that please :-)

73 Keith

On 28 Mar 2025 at 19:41 +0000, Christopher Schlegel via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:
> If I'm not mistaken, Dirk put some variables in that can tweak this on a per node basis.
> $Spot::dupecall - check that call is not spotted too often - this the base dedupe interval - set to 0 to disable
> $Spot::dupecallthreashold - This is threshold at which a repeated call's dupe record actually becomes a dupe. So somewhere between 4 slowish and 3 fast spots will cause this indicate a possible flood.
>
> From Dirk when I asked...
> "This is an extract from another email…
> This an attempt to explain how the code for flooding protection for spot call, by call, node and ip addresses (call/ip thing below) works:
> 1. If a call/ip thing dupe does not exist it will create an entry in the dupe store with the current time+initial timeout ( 10 seconds ) and passed onward.
> 2. If the call/ip thing exists in the dupe file but the time stored is less than the threshold then it is incremented by a tick (was 10 seconds but is now 5 seconds) and then passed onward as though there was no dupe.
> 3. If the call/ip thing exists in the dupe file and the time stored is >= threshold then it is declared to be a DUPE.
>
> While all this is going on the Dupe cleaner is ticking along every 5 secs underneath deleting all Dupe records created here that have expired. This is how the whole system is self regulating. By setting the threshold you have decide how call/ip things you want to allow over that many 5 seconds ticks. After that it is declared a dupe until it cleaned or time has marched so that the dupe entry has dropped below threshold. If more come in and the threshold is crossed, then the whole cycle repeats."
>
> I have not had a chance to experiment with this, but maybe it'll help.
> 73, Chris WI3W
>
> > On Fri, Mar 28, 2025, 07:43 Grant via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> > > So the DUPE function in this case is in my view problematic.
> > >
> > > I saw a spot for E51ANQ on 40m reported from the USA – so I go and work him and then try to also spot E51ANQ on the same frequency – except I am in Australia.
> > >
> > > By blocking me submitting the spot people are loosing out on the ability to get timely data on where the bands are open from. A spot from me in VK is equally as valuable as a spot from the US in the same time period.
> > >
> > > Is the duple time window configurable?
> > >
> > > A value more like 120 seconds might be more appropriate
> > >
> > > Regards,
> > > Grant VK5GR
> > >
> > >
> > > From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> On Behalf Of IZ2LSC via Dxspider-support
> > > Sent: Friday, 28 March 2025 4:36 AM
> > > To: The DXSpider Support list <dxspider-support at tobit.co.uk>
> > > Cc: IZ2LSC <iz2lsc.andrea at gmail.com>
> > > Subject: Re: [Dxspider-support] build 608 =?utf-8?Q?=E2=80=9CSorry=2C_?=this is a duplicate”
> > >
> > > YES
> > > timer is 305 sec from the last spot of the same call on the same QRG
> > >
> > >
> > > -->
> > >
> > >
> > > On Thu, Mar 27, 2025 at 6:54 PM Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> > > > quote_type
> > > > Just tried to submit a spot and I got a dupe message.   I manually cleared the dupe file (clear/dupe) and my spot was accepted.
> > > >
> > > > Is this expected behaviour now?
> > > >
> > > > 73 Keith.
> > > >
> > > > G6NHU de G6NHU-2 27-Mar-2025 1739Z dxspider >
> > > > dx d68z 14088 RTTY QSX 14089.1 tnx
> > > > Sorry, this is a duplicate
> > > > G6NHU de G6NHU-2 27-Mar-2025 1747Z dxspider >
> > > > sh/dx d68z
> > > > G6NHU de G6NHU-2 27-Mar-2025 1747Z dxspider >
> > > >   14088.0 D68Z        27-Mar-2025 1746Z QSX 14089                             <OE5RLM>
> > > >   14088.0 D68Z        27-Mar-2025 1737Z rtty tnx 73 up                        <IZ5IOR>
> > > >   14090.0 D68Z        27-Mar-2025 1733Z RTTY IOTA AF007                       <OH6TN>
> > > >   14088.0 D68Z        27-Mar-2025 1726Z QSX 14089.00                          <IK0XBX>
> > > > _______________________________________________
> > > > 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
> _______________________________________________
> 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/20250328/52a3d539/attachment.htm>