<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div>
<div dir="ltr">Hi All,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I think leaving the User to decide what they see or don’t see is personal preference.</div>
<div dir="ltr">If we give them the tools to filter out what they want…. </div>
<div dir="ltr">Maybe,, if people want to see RBN then there should be a few nodes with it enabled, the rest have it disabled..</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Just my pennys worth..</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Brian GB7VAX</div>
</div>
<div id="ms-outlook-mobile-body-separator-line" dir="auto"><br>
</div>
<div id="ms-outlook-mobile-signature">Sent from <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of dxspider-support-request@tobit.co.uk <dxspider-support-request@tobit.co.uk><br>
<b>Sent:</b> Monday, March 17, 2025 5:24:48 PM<br>
<b>To:</b> dxspider-support@tobit.co.uk <dxspider-support@tobit.co.uk><br>
<b>Subject:</b> Dxspider-support Digest, Vol 266, Issue 81</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send Dxspider-support mailing list submissions to<br>
dxspider-support@tobit.co.uk<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
or, via email, send a message with subject or body 'help' to<br>
dxspider-support-request@tobit.co.uk<br>
<br>
You can reach the person managing the list at<br>
dxspider-support-owner@tobit.co.uk<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Dxspider-support digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: FTx autogenerated spots (Keith)<br>
2. Re: FTx autogenerated spots (Kin)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 17 Mar 2025 17:11:02 +0000<br>
From: Keith, G6NHU <g6nhu@me.com><br>
To: The DXSpider Support list <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] FTx autogenerated spots<br>
Message-ID: <5cf3717c-9e49-42f2-8cbe-28d0021435b1@Spark><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I?m with Andy on this, I think it should be something for users to decide whether they show them or not.? ?I want to give my users the choice what they see and not dictate to them.<br>
<br>
With one caveat - Node advertising spam announcements which I filter out by having this line in my startup file.??If I could stop forwarding these on, I?d happily do so.<br>
<br>
rej/ann node_default input info telnet,cluster,7000,7300,7373,8000,8888,9000,17300,port<br>
<br>
<br>
73 Keith<br>
On 17 Mar 2025 at 16:44 +0000, g4piq via Dxspider-support <dxspider-support@tobit.co.uk>, wrote:<br>
> 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...<br>
><br>
> 73<br>
><br>
> Andy, G4PIQ<br>
><br>
> Sent from my Galaxy<br>
><br>
><br>
> -------- Original message --------<br>
> From: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
> Date: 17/03/2025 15:14 (GMT+00:00)<br>
> To: Rob Roschewsk via Dxspider-support <dxspider-support@tobit.co.uk><br>
> Cc: Dirk Koopman <djk@tobit.co.uk><br>
> Subject: [Dxspider-support] FTx autogenerated spots<br>
><br>
> 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.<br>
><br>
> DX de WA2JQZ:??? 28180.0? DL2KBX?????? FT4 DM78<>JO30????????????????????????????????????? 14 1415Z? 5<br>
> DX de G0LZX:???? 28074.0? W0JJG??????? FT8 -15dB 1265Hz???????????????????????????????????? 4 1415Z IO83<br>
> DX de CP6UA:???? 24915.0? CP6UA??????? FT8 FH82jf -> FH82jf??????????????????????????????? 10 1414Z 10<br>
> DX de G0LZX:???? 28074.0? N9AKR??????? FT8 -13dB from EN61 200Hz??????????????????????????? 4 1414Z IO83<br>
> DX de G0LZX:???? 28074.0? G0JEI??????? FT8 -20dB 520Hz?????????????????????????????????? IO93 1412Z IO83<br>
> DX de WA2JQZ:??? 28180.0? MW7TTA?????? FT4 DM78<>IO73??????????????????????????????????? IO73 1411Z? 5<br>
> DX de IZ0FYO:??? 28180.0? 9Z4Y???????? FT4 JN61og -> FK90??????????????????????????????? FK90 1410Z 15<br>
> DX de IZ1PLH:??? 21076.0? BG0HP??????? FT8 -15 dB from NL59??????????????????????????????? 23 1410Z JN34<br>
> DX de WA2JQZ:??? 28180.0? OT7X???????? FT4 DM78<>JO10????????????????????????????????????? 14 1408Z? 5<br>
> DX de G0LZX:???? 28074.0? CE3SOC?????? FT8 -12dB from FF46 1295Hz??????????????????????? FF46 1408Z IO83<br>
> DX de YC1JEL:??? 28180.0? RA4M???????? FT4 -04dB 2426Hz????????????????????????????????? LO44 1441Z 28<br>
> DX de GM0LIR:??? 24919.0? 6Y7EI??????? FT4 +06dB 1585Hz???????????????????????????????????? 8 1442Z IO85<br>
> DX de G0LZX:???? 28074.0? YC1JEA?????? FT8 -07dB from OI33 671Hz<br>
><br>
> would become:<br>
><br>
> DX de WA2JQZ:??? 28180.0? DL2KBX?????? FT4 DM78<>JO30????????????????????????????????????? 14 1415Z? 5<br>
> DX de CP6UA:???? 24915.0? CP6UA??????? FT8 FH82jf -> FH82jf??????????????????????????????? 10 1414Z 10<br>
> DX de WA2JQZ:??? 28180.0? MW7TTA?????? FT4 DM78<>IO73??????????????????????????????????? IO73 1411Z? 5<br>
> DX de IZ0FYO:??? 28180.0? 9Z4Y???????? FT4 JN61og -> FK90??????????????????????????????? FK90 1410Z 15<br>
> DX de WA2JQZ:??? 28180.0? OT7X???????? FT4 DM78<>JO10????????????????????????????????????? 14 1408Z? 5<br>
><br>
> 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.<br>
><br>
> 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?<br>
><br>
> 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.<br>
><br>
> Someone was complaining that this list is too quiet. Maybe this will liven it up.<br>
><br>
> 73 Dirk G1TLH<br>
><br>
> 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".<br>
><br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250317/487d8783/attachment-0001.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250317/487d8783/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 17 Mar 2025 18:24:37 +0100<br>
From: "Kin" <ea3cv@cronux.net><br>
To: "'The DXSpider Support list'" <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] FTx autogenerated spots<br>
Message-ID: <02c101db9761$771fdb80$655f9280$@cronux.net><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I don't understand Keith, why you leave the user free for the spots, but not for the ann, which represent a very small amount compared to the spots.<br>
<br>
Kin EA3CV <br>
<br>
De: Dxspider-support <dxspider-support-bounces@tobit.co.uk> En nombre de Keith, G6NHU via Dxspider-support<br>
Enviado el: lunes, 17 de marzo de 2025 18:11<br>
Para: The DXSpider Support list <dxspider-support@tobit.co.uk><br>
CC: Keith, G6NHU <g6nhu@me.com><br>
Asunto: Re: [Dxspider-support] FTx autogenerated spots<br>
<br>
I?m with Andy on this, I think it should be something for users to decide whether they show them or not. I want to give my users the choice what they see and not dictate to them.<br>
<br>
With one caveat - Node advertising spam announcements which I filter out by having this line in my startup file. If I could stop forwarding these on, I?d happily do so.<br>
<br>
rej/ann node_default input info telnet,cluster,7000,7300,7373,8000,8888,9000,17300,port<br>
<br>
<br>
73 Keith<br>
On 17 Mar 2025 at 16:44 +0000, g4piq via Dxspider-support <dxspider-support@tobit.co.uk>, wrote:<br>
<br>
<br>
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...<br>
<br>
73<br>
<br>
Andy, G4PIQ <br>
<br>
Sent from my Galaxy<br>
<br>
<br>
-------- Original message --------<br>
From: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
Date: 17/03/2025 15:14 (GMT+00:00)<br>
To: Rob Roschewsk via Dxspider-support <dxspider-support@tobit.co.uk><br>
Cc: Dirk Koopman <djk@tobit.co.uk><br>
Subject: [Dxspider-support] FTx autogenerated spots<br>
<br>
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.<br>
<br>
DX de WA2JQZ: 28180.0 DL2KBX FT4 DM78<>JO30 14 1415Z 5<br>
DX de G0LZX: 28074.0 W0JJG FT8 -15dB 1265Hz 4 1415Z IO83<br>
DX de CP6UA: 24915.0 CP6UA FT8 FH82jf -> FH82jf 10 1414Z 10<br>
DX de G0LZX: 28074.0 N9AKR FT8 -13dB from EN61 200Hz 4 1414Z IO83<br>
DX de G0LZX: 28074.0 G0JEI FT8 -20dB 520Hz IO93 1412Z IO83<br>
DX de WA2JQZ: 28180.0 MW7TTA FT4 DM78<>IO73 IO73 1411Z 5<br>
DX de IZ0FYO: 28180.0 9Z4Y FT4 JN61og -> FK90 FK90 1410Z 15<br>
DX de IZ1PLH: 21076.0 BG0HP FT8 -15 dB from NL59 23 1410Z JN34<br>
DX de WA2JQZ: 28180.0 OT7X FT4 DM78<>JO10 14 1408Z 5<br>
DX de G0LZX: 28074.0 CE3SOC FT8 -12dB from FF46 1295Hz FF46 1408Z IO83<br>
DX de YC1JEL: 28180.0 RA4M FT4 -04dB 2426Hz LO44 1441Z 28<br>
DX de GM0LIR: 24919.0 6Y7EI FT4 +06dB 1585Hz 8 1442Z IO85<br>
DX de G0LZX: 28074.0 YC1JEA FT8 -07dB from OI33 671Hz <br>
<br>
would become:<br>
<br>
DX de WA2JQZ: 28180.0 DL2KBX FT4 DM78<>JO30 14 1415Z 5<br>
DX de CP6UA: 24915.0 CP6UA FT8 FH82jf -> FH82jf 10 1414Z 10<br>
DX de WA2JQZ: 28180.0 MW7TTA FT4 DM78<>IO73 IO73 1411Z 5<br>
DX de IZ0FYO: 28180.0 9Z4Y FT4 JN61og -> FK90 FK90 1410Z 15<br>
DX de WA2JQZ: 28180.0 OT7X FT4 DM78<>JO10 14 1408Z 5<br>
<br>
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.<br>
<br>
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?<br>
<br>
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.<br>
<br>
Someone was complaining that this list is too quiet. Maybe this will liven it up.<br>
<br>
73 Dirk G1TLH<br>
<br>
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".<br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250317/e5b28cf6/attachment.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250317/e5b28cf6/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Dxspider-support Digest, Vol 266, Issue 81<br>
*************************************************<br>
</div>
</span></font></div>
</body>
</html>