search

Crazy-Marvin / Morse

Translator for converting text into morse code and vice-versa
https://crazymarvin.com/morse/
Apache License 2.0
159 stars 31 forks source link

Confusing paragraph in readme #23

Open ghost opened 4 years ago

ghost commented 4 years ago

This passage in your readme is totally incorrect:

Since people rarely communicate via telegraph, nowadays there are very few people who can memorize Morse codes. Instead, it has become a way to encode something or special characters for special purposes. Of course, these special characters are still widely used in many situations, you don’t know when you are going to really need it. 

Excuse me? Where is this known? Cite your source. As an amateur radio operator (my call sign is my username), I find that the developer is either totally ignorant of CW (NOT the broadcast TV network) and its current use today, or 2, not a licensed ham.

I am concerned regarding this as a licensed ham, where ham radio is a dying art... but we need to keep the hobby alive. What would happen if the cell towers went down? Hams provide help. Please, I extend a plea to find a ham radio club and get your license. You can start with http://www.arrl.org/find-an-amateur-radio-license-exam-session and it's $15. Morse code is not required for any test now, but still is alive and well. Morse code is still used on QRP (low power) HF communication.

CW (Morse code) is not cryptography! FCC Part 97 prohibits any cipher or other obfuscation to hide the meaning of your transmission.

Please fix your README.MD. The information is totally wrong regarding Morse code.

73, W9JYD

CrazyMarvin commented 4 years ago

Hi, thanks for opening the issue. I am glad to have an expert on that point now. I ordered that text on Fiverr as I am not a good writer. It would be really awesome if you could open a PR with a fixed description. Thank you so much for the rectification and your help.

janheinrichmerker commented 4 years ago

@W9JYD You're right about Morse not being cryptographic. Though I am confused about your tone. Are you experiencing issues caused by the incorrect information in the readme? We would highly appreciate, if you'd take the time to propose a change of that passage, highlighting the current use cases. We could also add a disclaimer for recommending to not use Morse for cryptography.