[Dxspider-support] $DXProt::senderverify = '2'

[g4piq at btinternet.com]

Hi Mikel,

 

Sorry - was trying not to create too much reflector traffic - but you ask a direct question - so here are my thoughts.

 

My aim is to have a node which is contest optimised for a multi operator contest environment - I've been running this node to do that for well over 30 years. That means it misses as few spots as sensible, gets them quickly, and allows the mult station radio operator to use their ears / brain to figure out if the spots are good or not. Yes - some of the fake spots are really irritating in contests - and I'd love to see them go - but not at the expense of missing 70% of valid spots. Lots of the spots we are currently not seeing are perfectly valid - and unique. I appreciate that everyone has different use cases for their cluster and that's why I'd prefer the sendverify parameter to affect display rather than backbone forwarding.

 

And I say that because I'm not convinced that Is backbone traffic from unverified spots is really an issue any more. The days of 1200 baud half duplex radio links are long gone. Dirk's code is so lightweight that it ticks along at a few percent CPU on a Raspberry Pi and the bandwidth consumption is tiny. 

 

The flooding at the weekend clearly caused some nodes real problems.  But I think that's a different behaviour to spots being sourced from nodes that for we haven't got up to date user lists for (many reasons for that in this complex heterogeneous network). The flooding at the weekend feels like it could be prevented with a different mechanism - for example an incoming rate limit on spots with the same call or from the same IP.

 

BTW @Dirk - really appreciate all the hard work on this - I'm not having a pop - just sharing some data. 

 

73

 

Andy, G4PIQ

-----Original Message-----
From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> On Behalf Of Mikel EA2CW via Dxspider-support
Sent: 19 February 2025 14:34
To: dxspider-support at tobit.co.uk
Cc: Mikel EA2CW <ea2cw at gautxori.com>
Subject: Re: [Dxspider-support] $DXProt::senderverify = '2'

 

Dear Andy

So d'you mean, "I will not show bad spots to my users, but I will keep spreading what I consider bad spots to the rest of the net", am I right ?

 

I think the solution should not to be "soft" with old or missconfigured servers, but being oriented to the quality of the "product" server to our customers. Then they will decide.

 

 

El 19/2/25 a las 14:49, g4piq--- via Dxspider-support escribió:

> The difficulty is that - as I've read it (and I'd be delighted to be corrected) - with DXProt::senderverify = '2' the node drops the spot and doesn't forward on its neighbours - so that node makes a unilateral decision on whether the spot is good or not for the rest of the network. I'd be much more comfortable with the parameter just impacting what's displayed to the users on the node.

> 

> Apologies if I have mis-understood this.

> 

> 73

> 

> Andy, G4PIQ

> --

73 de Mikel Berrocal EA2CW-AE2CW

Bilbao, Basque Country

 <mailto:ea2cw at gautxori.com> ea2cw at gautxori.com

 <https://www.ea2cw.eus> https://www.ea2cw.eus

 

 

_______________________________________________

Dxspider-support mailing list

 <mailto:Dxspider-support at tobit.co.uk> Dxspider-support at tobit.co.uk

 <https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support> 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/20250219/dee8ec00/attachment-0001.htm>