User name:
Password:

Forgot password? - Sign up

chromedome CpDong EA1IRO EA7GZQ gattociao GM0JDB happi59 iadd IU2PES IU5SGV IW2NNQ jh9xgr jk1lwp KA5WAD KF0GHC M6MTN mcnugget91 ofe PhilipHash PU4UAI scotch5 SP2SJ SP9XI Sq6kw test vu2yyf W5JCS

Please have a look at my experimental cw to twitter gateway: https://twitter.com/#!/search/cw2tweet
Connect to Echolink node 521344 (OE6XCG-R) with your vhf/uhf transceiver and use a key and a tone generator (800...1200 Hz)for sending your tweet. It is essential that your message starts with -.-.- and ends with .-.-.
Of course, don't forget your callsign!
This is a receive-only setup, so just look at twitter for verifying if your tweet was received. I use fldigi for decoding. If you don't see anything, you might have to improve your cw ;-) Or simply use the text to cw feature of lcwo (don't forget to set the pitch to approx. 900 Hz). Type for start and for end into the text entry window. Have fun!

Two special characters disappeared in my previous posting: If you use lcwo, type:
(left-angle bracket)ka(right-angle bracket)
for start and
(left-angle bracket)ar(right-angle bracket)
for end of message.

My python script had some problems when receiving empty strings / only spaces: Sending those strings caused tweepy module to crash. Modified script should be getting around this problem now.