One would think that it would be reasonable to at least skim the very ample 
instructions that have been put out. But no, it is not about to happen.

Nope, and there is little you can do to change it.  As a person who spends a 
fraction of his time writing documentation, I can tell you from personal 
experience, you can write documents till you’re blue in the face, and they 
won’t read them.  They’ll dive in feet first, make a mess, then jump online and 
complain at you for creating something they can’t figure out how to use.  
Assuming users will read and following instructions is foolish.  If you want 
more order in the FT8/DXpedition world, it will have to be enforced.

Dave / NX6D


________________________________
From: Gary Kohtala - K7EK via wsjt-devel <wsjt-devel@lists.sourceforge.net>
Sent: Saturday, June 30, 2018 11:25:32 AM
To: 'WSJT software development'; John Zantek; Black Michael
Cc: Gary Kohtala - K7EK
Subject: Re: [wsjt-devel] Observation on Expedition Mode

The Baker Island DXpedition has brought out the very worst:  Stations calling 
blind for hours when KH7Z is not even on FT8, incessant calling below 1000 hz, 
calling the wrong call sign (KH7V), calling in the wrong time slot, etc. One 
would think that it would be reasonable to at least skim the very ample 
instructions that have been put out. But no, it is not about to happen. I came 
close to completing for an ATNO on 30m but sadly, I never got his RR73 and did 
not go into their log. So, I continue to fight the
uninformed and apparently clueless hoards that have descended upon the bands. 
And of course throw in bad propagation, low power,
and a less than ideal antenna system and the odds of making the Q are even 
lower. Oh well. There is still time. I'd love to get
KH1 for that ATNO on any mode, any band.

Best regards,

Gary, K7EK

Radcliff, KY (EM77at)

------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to