Good morning Joe,
Thank you for all the great work you have been doing. I am hoping my work
slows down a bit so I can start contributing again.
Two quick observations on MSK144...
I note with SH ON the TX2 message is sent with the calls hashed. Considering
the flow of the contact....
ND0B K1JT
KIJT ND0B EN07 -> (receives ND0B TX1 so has RXed the calls)
(Has not RXed) <- <ND0B K1JT> 00
The hashed version of the calls is not the calls and cannot be reverse decoded
to the calls. It is only a high probability of being unique for those calls,
i.e. you cannot calculate the hash without already knowing the calls which in
this case ND0B only knew because that is who he is working. With K1JT sending
the hashed version ND0B never actually decodes the calls, only the hash.
Question: Should TX2 be sent in the clear rather than hashed to fulfill the
calls both ways part of the minimal QSO requirement???
Second I have started letting people know, it is important to run CW ID when
using SH ON to meet the FCC rules requirements on IDing.
Thanks Joe, and again, thanks for all your (and everyone else's) great work.
73 de Bill ND0B
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
