Hey #hamradio folks. I know we use the acronym CW to mean morse code (via “continuous wave.”) I also know we are encouraged to use hashtags to make our content more easily searchable. I agree with all this.

But be aware that #cw typically refers to Content Warnings. And that convention has existed on the Fediverse/Mastodon for a very long time.

I suggest we use #morse instead. It’ll prevent confusion, and your posts are less likely to be filtered out.

Please Boost for visibility.

@smitty I have been using #cwops too, either is fine I guess
@W9SSN ooo, that’s good too.
@smitty I like this, but I think it would be better to use #MorseCode as it would be more meaningful to a screen reader. We don’t have to work very hard to send messages here 🤗
@tiesa @smitty genuine question, why would a screen reader have a problem with #morse?
AIUI they don't like multiple words without spaces, I imagine #cwops would be a problem bit #morse is just one word and is much easier to introduce than a two word tag with camelcase so has multiple opportunities for error
@M0TDN @smitty they wouldn’t have a problem with #morse but it would just be read as morse where #MorseCode will be read as Morse Code. If you capitalize the first letter of each word in a multi word hashtag a screen reader will treat it as two words.

@tiesa @M0TDN does the first word need to be capitolized too? I thought “morseCode” would still be read as two words.

Technical detail question, not at all a disagreement with your post.

@M0TDN @tiesa #morse should be fine. If you are going to do “morse code,” do it in camel case: #MorseCode or #morseCode. The Capitol letters in the middle of the word tell screen readers to read it as a separate word.

And, you’re right, “CW Ops” isn’t great in that regard.

@M0TDN @smitty guess I just normalize on capitalizing the first letter because that’s what a lot of screen reader users have advocated in requests.
@tiesa @M0TDN sounds good. I’ll do so going forward. The most recent shop coding style I used was camelDrinkingCase not CamelStandingCase (I just made those terms up) so it might take me a bit to adjust.

@smitty .
#MorseCode is probably better as it is what non-hams are more likely to look for. #CW is less commonly known outside of Amateur Radio circles and as you correctly point out can be confused with other things.

#AmateurRadio #HamRadio

@PikesPeakARES
Almost all abbreviations of length 1 or 2 and most of length 3 are being used for different purposes by different communities. To avoid confusion, it is wise to prefer longer terms.

We in the CW part of the #hamradio community use a transport that is quite slow. So we found it wise to use lots of short abbreviations.

There is an inherent conflict here.

When transmitting to the Fediverse, I intend to use the longer #MorseCode.

@smitty

@smitty I too feel like the #cw debate will be going on in perpetuity
@M0TDN yeah, I understand that. But at least now it’s started.
@smitty now I am thinking about updating my profile.
@sergio_101 I won’t speak for you, but “content warning” may still be appropriate for some people. *points at self*
@smitty I don’t know that I understand the nuances of content warnings yet.
@smitty @sergio_101 there is a lot of discussion about content warnings and their potential for being oppressive, especially to non-white people. If you search on the hashtag #ContentWarning a few good discussions pop up.
Personally I feel that content warnings should be imposed by the OP and if someone has an issue with seeing what they post there are tools available to moderated what you see on your own timeline without imposing censorship on others.
@tiesa @sergio_101 the tricky bit comes when the reader want a warning about something that the writer doesn’t think needs a warning, or even realize might need a warning. I’m usually the writer in this example.
@smitty @sergio_101 it is something we all are learning and I’m for it to make our world more inclusive 🤗
@smitty @tiesa right. No one has contacted me about any infractions I have made, but most all of my posting has been prior to the twitter influx. Plus, I really only post super tame stuff.

@sergio_101 @tiesa yeah. I don’t have a list either, except my judgement. And if there’s one thing I’ve learned over the last 10 or 20 years, it’s that my privileged ass doesn’t get to make the judgement calls that matter. So I try to listen to others’ opinions and learn where I can.

Sorry I don’t have a better/more precise answer for you.

@smitty @tiesa I figure that with the influx, we’ll definitely be put on notice if we post anything that someone doesn’t like.
@sergio_101 @tiesa I figure, use your best judgement, then adjust your judgement over time as education happens. I think you’ll be alright.

@sergio_101 let’s use an extreme example: a gory picture of a car crash. As a news post, it might be relevant to post. But obviously, many readers won’t want to see it without warning, or at all. So “before you proceed, be aware these pictures contain graphic content. Viewer discretion is advised.” Then the viewer/reader decides whether to expand that image.

Some people have issues with “simple” things like eye contact, or politics, etc. They appreciate content warnings.

@smitty right. I just don’t know what the list of triggers is. I see people posting content warning for foo, vehicles, faces, something called “adjacent”, gender, weather, etc. I just don’t know all the things we need to cover.
@smitty then there still the #PBS #MasterpieceMystery character Endeavor Morse.
@KeithHiggs how many people are hash tagging Endeavor Morse? 😂
@smitty exactly where I was going. However, it's a very well done program so if you like those BBC mysteries I recommend it.
@smitty cwOps is a Morse code academy. #MorseCode is unambiguous and screenreader friendly
@smitty
Only you would know that and thank you
Makes perfect sense
@N9VDQ some might say my entire feed deserves a content warning. ;-)
@smitty
Or perhaps #MorseCode
@W8HF yep. Several have suggested that too. Clear, and screen reader friendly.
@smitty
Plus to a non ham Morse is vague. #MorseCode they will know plus may inspire someone to do some digging and discover that it is very much alive and well!
@smitty I also like #MorseCode as it includes using the code by other methods such as, modulated carrier, flashing light, and sound instead of just continuous wave carrier.
@N1ZZZ YES! I decided not to attack this hill in that post, but the term “continuous wave” only differentiates that mode from SPARK GAP. Every other mode we use today, with the arguable exception of voice over SSB, is a continuous wave!
@N1ZZZ @smitty to be fair, though, my Morse code probably requires a content warning given how atrocious it is. Perhaps #CW would be appropriate for me still 
@smitty is #-.- taken?
@kc5kct Ha! Unfortunately, doesn't look like that worked. Darn.
@smitty Good point, I'm going to change my profile.
@KN4YRM replies to this have made good arguments for #MorseCode (complete with capitols) instead. Better for screen readers. But otherwise, thank you. :-)
@smitty how about #a1a
@LittlejohnsCarl oh, heh. Is that the ITAR designator? :-) I like it, but probably a little too subtle.
@smitty Noted! Now to remember this. :)

@smitty
I need to move away from the "CW" hashtag. The recent discussion has convinced me if that.

But isn't #MorseCode a better choice? The plain #Morse you suggest refers to a person, not the code. And I find #MorseCode more naturally integrates into the sentences I typically write.
@qrper