Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://writing.exchange/users/davepolaschek/statuses/115703670063686467">Dave Polaschek (he/him) (davepolaschek@writing.exchange)'s status on Friday, 12-Dec-2025 09:07:24 JST</a><a href="https://writing.exchange/@davepolaschek" title="davepolaschek@writing.exchange"><img src="https://gnusocial.jp/avatar/245017-48-20250820030327.webp" width="48" height="48" alt="Dave Polaschek (he/him)" style="position: absolute; left: 0; top: 0;">Dave Polaschek (he/him)</a></section><article><p>I’m pretty sure one of my ham followers knows of a Linux Morse trainer that wouldn’t have the latency problems of Android. Perhaps? <a href="https://writing.exchange/tags/AmateurRadio" rel="tag">#AmateurRadio</a> <a href="https://hachyderm.io/@jbcrawford/115702788572739032" rel="nofollow">https://hachyderm.io/@jbcrawford/115702788572739032</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/5945513#notice-11694326">In conversation</a><time datetime="2025-12-12T09:07:24+09:00" title="Friday, 12-Dec-2025 09:07:24 JST">about 8 months ago</time> <span>from <span><a href="https://writing.exchange/@davepolaschek/115703670063686467" rel="external" title="Sent from writing.exchange via ActivityPub">writing.exchange</a></span></span><a href="https://writing.exchange/@davepolaschek/115703670063686467">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://hachyderm.io/@jbcrawford/115702788572739032">J. B. Crawford (@jbcrawford@hachyderm.io)</a></h5><div> from <span>J. B. Crawford</span></div></header><div>I find that if you have middling proficiency in morse code, the Android apps for learning and sending CW are very annoying. I am particularly always stumbling on things like 'H' and '4' and '5' with a lot of repeated dits. I think the problem is quite simply that Android is too slow: the latency from tapping the screen to emitting a beep is longer than a typical dit, so you have to completely ignore the audible feedback or you'll 'lose your place' like you do with your voice played back at you.Funny that the latest communications technology struggles with meeting the latency budget of one of the oldest.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Dave Polaschek (he/him) (davepolaschek@writing.exchange)'s status on Friday, 12-Dec-2025 09:07:24 JST Dave Polaschek (he/him)
I’m pretty sure one of my ham followers knows of a Linux Morse trainer that wouldn’t have the latency problems of Android. Perhaps? #AmateurRadio https://hachyderm.io/@jbcrawford/115702788572739032
In conversationabout 8 months ago from writing.exchangepermalink
Attachments
1. No result found on File_thumbnail lookup.
  J. B. Crawford (@jbcrawford@hachyderm.io)
  from J. B. Crawford
  I find that if you have middling proficiency in morse code, the Android apps for learning and sending CW are very annoying. I am particularly always stumbling on things like 'H' and '4' and '5' with a lot of repeated dits. I think the problem is quite simply that Android is too slow: the latency from tapping the screen to emitting a beep is longer than a typical dit, so you have to completely ignore the audible feedback or you'll 'lose your place' like you do with your voice played back at you. Funny that the latest communications technology struggles with meeting the latency budget of one of the oldest.

Public

Embed Notice

HTML Code

Corresponding Notice