[Dxspider-support] Bad spots going through

Dirk Koopman djk at tobit.co.uk
Wed Jul 2 15:49:22 BST 2025


Easy to spot, but difficult to stop because no-one will standardise what 
(limits) a (spotted) callsign can be constrained to be. There are no 
callsign checks, other than things like swearing, badspot etc on the 
spotted callsign field. It gets longer and non-standard more or less at 
a whim.

But one could put F5IN into badspotter - in this case.

Dirk G1TLH
On 02/07/2025 15:00, IZ2LSC via Dxspider-support wrote:
> These spots should not be accepted/forwarded, but they are.
>
>
>   14025.5 QRG/QRL      2-Jul-2025 1350Z                            <F5IN>
>   21019.0 RAC          1-Jul-2025 2012Z        <F5IN>
>   14025.5 QRG/QRL      1-Jul-2025 1746Z TNX QSY        <F5IN>
>   14025.5 RAC          1-Jul-2025 1735Z        <F5IN>
>   21027.0 RAC          1-Jul-2025 1515Z        <F5IN>
>   14025.7 RAC          1-Jul-2025 1456Z        <F5IN>
>   14019.0 RACTEST      1-Jul-2025 0550Z        <F5IN>
>
>
> 73
> Andrea
> iz2lsc
>
> -->
>
> _______________________________________________
> 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/20250702/90e586d9/attachment.htm>


More information about the Dxspider-support mailing list