The Wiley Role of RTTY in the WQ6X World

It is no secret that I prefer Cw contests over Ssb; because we use Q-Codes, there really is
no language barrier.  With Cw, there are no "accents" to contend with; atmospheric noise has
a less-debilitating effect, compared to Ssb.  In the last dozen years (thanks largely to N6GEO),
I've been exposed to the Wiley world of RTTY.  

Of course, a fond RTTY memory is the DX-pedition with N6GEO to St. Croix, where
we took 1st-place (for DX) in the 2014 ARRL RTTY RU contest.  Back in January 2020
I wrote a Blast-from-the-Past Blog about the RTTY Roundup (RU) event. 
[CLICK HERE] to read that Blog.

RTTY requires a more complex hardware arrangement than Cw or Ssb, which is probably
off-putting to some would-be upcoming RTTY operators.  However, once a proper hardware configuration is established, RTTY operations actually prove to be far more effective as a communication mode than even Cw.

N6CY + N6ERD + WQ6X (running remote) in 2020 RTTY RU

When running remote operations, internet disruptions or poor latency can easily sideline a Cw
or Ssb contest operation.  However, because the RTTY signals are decoded at the remote site,
when the internet connection settles back down, the QSO information is still there in the RTTY decoder window on the remote computer screen.  With Ssb and Cw, when a signal is lost, it is
LOST - requiring a repeat transmission of the previously sent information.

Bottom line - RTTY has become an important part of my operating world.
JT-65, FT4 and FT-8 do nothing for me.  Outside of RTTY contests, I like the idea that I can
enjoy a LENGTHY typed-in QSO with another station, even tho some of the usual information
(Name, QTH, radio, etc.) is often sent using macro buttons defined on the decoder screen.

If YOU run RTTY, like I run RTTY, then WE can RTTY along.