[Dxspider-support] FTx autogenerated spots

[Kin]

The sysop currently has the possibility to filter this traffic for all its users from the default filter.
You can leave the decision up to the user, but will the user actually know about this option?
If you decide to let the user decide on this kind of traffic, then you would have to normalise it with a set/unset/show, I think.
But if I had to choose, it would be either all FTx or none. Along the lines of being able to separate between human (and pseudo) spots, and rbn.
 
Kin EA3CV
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de g4piq via Dxspider-support
Enviado el: lunes, 17 de marzo de 2025 17:36
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: g4piq <g4piq at btinternet.com>
Asunto: Re: [Dxspider-support] FTx autogenerated spots
 
I generally prefer the principle of dropping spots at the user level rather than on the backbone (unless they are at such a rate as to be dangerous). That way the sysio can configure their node to do what's right fir them and their user base - not what someone else further upstream thinks should be right for them. If we don't apply this principle then the spider ends up becoming closer to a full mesh...
 
73
 
Andy, G4PIQ 
 
Sent from my Galaxy
 
 
-------- Original message --------
From: Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk> 
Date: 17/03/2025 15:14 (GMT+00:00) 
To: Rob Roschewsk via Dxspider-support <dxspider-support at tobit.co.uk> 
Cc: Dirk Koopman <djk at tobit.co.uk> 
Subject: [Dxspider-support] FTx autogenerated spots 
 
In the spirit of discouraging client programs generating spots automatically when they work something, or for other reasons that make life difficult for sysops and users that don't use digital modes, I have introduced the following system variable: $DXProt::remove_auto_ftx which, as default (in the test branch), is currently set to 1. 

DX de WA2JQZ:    28180.0  DL2KBX       FT4 DM78<>JO30                                      14 1415Z  5
DX de G0LZX:     28074.0  W0JJG        FT8 -15dB 1265Hz                                     4 1415Z IO83
DX de CP6UA:     24915.0  CP6UA        FT8 FH82jf -> FH82jf                                10 1414Z 10
DX de G0LZX:     28074.0  N9AKR        FT8 -13dB from EN61 200Hz                            4 1414Z IO83
DX de G0LZX:     28074.0  G0JEI        FT8 -20dB 520Hz                                   IO93 1412Z IO83
DX de WA2JQZ:    28180.0  MW7TTA       FT4 DM78<>IO73                                    IO73 1411Z  5
DX de IZ0FYO:    28180.0  9Z4Y         FT4 JN61og -> FK90                                FK90 1410Z 15
DX de IZ1PLH:    21076.0  BG0HP        FT8 -15 dB from NL59                                23 1410Z JN34
DX de WA2JQZ:    28180.0  OT7X         FT4 DM78<>JO10                                      14 1408Z  5
DX de G0LZX:     28074.0  CE3SOC       FT8 -12dB from FF46 1295Hz                        FF46 1408Z IO83
DX de YC1JEL:    28180.0  RA4M         FT4 -04dB 2426Hz                                  LO44 1441Z 28
DX de GM0LIR:    24919.0  6Y7EI        FT4 +06dB 1585Hz                                     8 1442Z IO85
DX de G0LZX:     28074.0  YC1JEA       FT8 -07dB from OI33 671Hz  

would become:

DX de WA2JQZ:    28180.0  DL2KBX       FT4 DM78<>JO30                                      14 1415Z  5
DX de CP6UA:     24915.0  CP6UA        FT8 FH82jf -> FH82jf                                10 1414Z 10
DX de WA2JQZ:    28180.0  MW7TTA       FT4 DM78<>IO73                                    IO73 1411Z  5
DX de IZ0FYO:    28180.0  9Z4Y         FT4 JN61og -> FK90                                FK90 1410Z 15
DX de WA2JQZ:    28180.0  OT7X         FT4 DM78<>JO10                                      14 1408Z  5

It is, of course, likely that these spots that are left are auto generated too - but at least they provide some useful information. If it is deemed necessary, I can get rid of these as well, together with all the other FTx spots if necessary. 

Some people may think this is overkill, but the spot feed is filling up with more and more useless spots, most of which are machine generated. Someone has to take a stand. Now where did I put that wobbly pedestal I bought from the charity shop the other year? 

You should be made aware, the place that this is currently done, means that these spots are dropped at the PC11/PC61 protocol level - they won't be passed onward to other nodes... You may not like that... It doesn't have to work this way, it could be a user command. Please see the next paragraph. 

Someone was complaining that this list is too quiet. Maybe this will liven it up.

73 Dirk G1TLH

PS I just got a bit sick of the lack of "normal" v "FTx" spots whilst testing the deduping code so I thought "I know, I've meaning to do this for ages and it's only an extra 8 lines of code and a few comments".


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250317/5cae7d88/attachment-0001.htm>