While I do agree, there aren't too many clues for the operator who
is listening apart of not trusting any rare DX.
I saw that NK call yesterday in 10m mixed with the Aruba one. I
answered to both, once or twice. Both looked like legit grids and
feasible callsigns.
In the last weeks I'm getting far more false decodes than it used
to be in a whole year. Many R in the messages and grids that
doesn't match the callsign or places where is unlikely to find
anyone far from everything or maritime routes. Not saying that
it's related or it's due a bug, just making an observation about
it.
On Tuesday, February 27 2024, 08:33:05, Joe Taylor via wsjt-devel
wrote:
[1. text/plain]
Hi Jon,
On 2/26/2024 7:50 PM, Jon Anhold KM8V via wsjt-devel wrote:
231900 16 0.4 909 ~ BG2AUE <P4/WE9V> -25 Aruba
232530 5 0.4 909 ~ JR3UIC RR73; JA7WND <P97USI/P> +06 DPR of
Korea
Maybe some logic that checks "am I *really* North Korea?" would
be
good :)
That logic is you, the operator. WSJT-X has many operator aids.
It
is not an operator replacement.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Happiness isn't something you experience; it's something you
remember.
--- Oscar Levant
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
