[Dxspider-support] badword impacts

[g4piq at btinternet.com]

I noted this little interaction between the new badword definitions and
normal cluster behaviour.

 

27May2023 at 19:48:21 G4PIQ swore: 14001.8 K1LZ (with words:K1L)

27May2023 at 19:48:21 G4PIQ|192.168.1.254|dx|14001.8 K1LZ

 

Obviously no spot was actually distributed - except to me.

 

With the current badword settings, any stations with K1L at the start of
their callsign won't get spotted. That may not be the best compromise
between filtering badwords and making the system work for the real users -
there are several regular big contesters with K1L* callsigns - K1LZ (very
big and well known), K1LG, K1LH, K1LK, K1LM, K1LN, K1LO, K1LR, K1LT, K1LX
are all in the SCP database. 

 

Maybe just update KIL to KILL (which reduces but doesn't remove the blast
radius - K1LLU and K1LLR are both in my contest logs) - or remove the I->1
mappings for this word

 

73

 

Andy, G4PIQ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230528/6fc6767b/attachment.htm>