[Dxspider-support] Startup script

[Kin]

There are two perspectives on this issue:
*	Those who support allowing all information to flow through the network, leaving it to sysops or users to filter it.
*	And those who prefer filtering at the source to avoid propagating everything.
 
However, there is always a middle ground. I believe that if the information is accurate, it should be propagated, but with tools that allow certain types of information to be filtered.
In the case of autospots, a command or filter similar to “rej/spot when (by eq call)” would be useful. This would allow sysops to apply it in node_default or let users do so themselves.
 
I am not particularly in favour of autospots, but in some cases, they may be justified or permitted by specific contests.
 
Kin EA3CV
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Danilo Brelih via Dxspider-support
Enviado el: viernes, 14 de febrero de 2025 12:41
Para: Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk>
CC: Danilo Brelih <s50u at s50e.si>
Asunto: Re: [Dxspider-support] Startup script
 
Keith, G6NHU via Dxspider-support je 14.2.2025 ob 12:24 napisal:
t should be set to 0 by default and then individual sysops can opt out if they want.
Or selfspotting can be turned per Node default to OFF and turned on by each individual user with the command (un)SET/SELFSPOTING as example. In our experience only a few users per Node will show interest for the selfspotting option to be on, believe me. 🙂
GL ARRL CW de Dan S50U
-- 
S50CLX DX Cluster <https://s50clx.infrax.si> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250214/2f8b435a/attachment-0001.htm>