wholeheartedly agree Tom On Tue, 9 Feb 2021, 13:31 tom, <t...@tkrh.co.uk> wrote:
> Against it. > > There are too many callsigns being issued for numerous reasons - > anniversaries / covid / 1st etc. Having the software check (and keep > having to get internal lists updates from other sites) is not really > practical. > > I can’t think of an easy way to detect pirates - non-dxcc you have the > overhead and issues as mentioned above - there is no ‘100% verifiable’ list > of genuine callsigns - also no way to tell that the GM8MJV you are working > is in fact me - it’s a valid callsign - someone may be using it - a pirate > but unable to detect it. > > Would be better off concentrating on detecting and blocking the robots and > flag those. > > Tom > GM8MJV > > > > On 9 Feb 2021, at 10:37, Anders Strange <anders.stra...@gmail.com> > wrote: > > > > Would it be an idea to implement a 'Valid DXCC' checking and 'Pirate > Detection' feature? > > > > The problem is that pirate callsigns like the Dxx from the Donetsk > region in Russia show up as new/unknown DXCC's. It would be fairly easy to > implement a check against the ITU list and the valid DXCC list and make a > new color for 'possible pirate' or something. > > > > What do you think? > > > > 73's > > Anders / OZ3ACB > > _______________________________________________ > > wsjt-devel mailing list > > wsjt-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel