TZUTC: -0500
MSGID: 1430.fido-englisht@1:3634/12 24a773fa
REPLY: 2:221/6.0 60423532
PID: Synchronet 3.18a-Linux  May 23 2020 GCC 7.5.0
TID: SBBSecho 3.11-Linux r3.173 May 23 2020 GCC 7.5.0
CHRS: ASCII 1
NOTE: FSEditor.js v1.104
  Re: 73! Morse telegraph ;)
  By: Anton Shepelev to mark lewis on Fri Mar 05 2021 15:42:10


note: quote attribution MS manually corrected to ML below...

 AS>>> I did not realise it. I thought that decyphering did
 AS>>> not requier character separators.  See also:

 ML>> how would you decipher this without character
 ML>> separators?

 ML>>   .--...-.-.-...

 AS> I thought Morse code was like variable-width Unicode in this
 AS> regard, where the prefix is sufficent to decide whether a
 AS> character is terminated or another dash or dot is pending.
 AS> Now I see I was wrong.

yeah, there is no prefix in morse... it is too old to have such concepts...

FWIW: the above line i wrote without any silence spacing is ABCD but it could
be decoded as one of several others depending on how one breaks it apart...

  .-  -...  -.-.  -...
  A   B     C     D

speed is another factor with morse code... if you can easily hear 20WPM but
have problems at 30WPM, you might miss some things and get a wrong decode...


)\/(ark
--- SBBSecho 3.11-Linux
 * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
SEEN-BY: 1/19 120 123 16/0 18/0 19/10 90/1 105/81 116/116 120/340
SEEN-BY: 123/0 25 35 40 126 130 131 150 170 180 190 755 129/305 135/300
SEEN-BY: 153/7715 154/10 203/0 221/0 1 6 360 226/30 227/114 702 229/101
SEEN-BY: 229/424 426 664 1016 1017 240/1120 2100 5138 5411 5824 5832
SEEN-BY: 240/5853 249/206 317 261/38 280/5003 282/1038 317/3 320/119
SEEN-BY: 320/219 319 322/0 757 342/200 423/81 460/58 640/1138 1321
SEEN-BY: 640/1384 712/848 2454/119 3634/0 12 15 27 50
PATH: 3634/12 640/1384 221/1 320/219 240/5832 229/426