# Contextual acronyms should be fine

**URL:** <https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272>\
**Category:** About This Message Board\
**Created:** [October 8, 2023, 2:54pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272 "2023-10-08T14:54:52Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 8, 2023, 3:41pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/21 "2023-10-08T15:41:18Z")

</div>

P&E and GD for sure. I’m not going to modnote 1 or 2 acronyms, but 6 I will for sure. In between lies the grey area.

> [@MrDibble](#):
>
> I am _very much_ a casual reader when it comes to obscure US state politics threads.

But you are not the standard. You are just you.

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 3:42pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/22 "2023-10-08T15:42:34Z")

</div>

> [@What\_Exit](#):
>
> **Actually, that standard does not matter.**  
> **It needs to be common knowledge, not just for P&E.**

Is this a new rule? Because I see nothing about acronyms in the new draft rules.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 3:44pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/23 "2023-10-08T15:44:07Z")

</div>

> [@MrDibble](#):
>
> It’s not just about you, though - WE? has indicated their personal standard of obscurity is going to be the yardstick going forward, I assume in all forums they moderate, and while I don’t care about P&E so much, I’d hate for that to be the standard in their forums I do hang out more in.

If you want the forums to be a welcoming place and not give off a vibe of “only the cool kids are allowed” then there should be _more_ clarity regarding acronyms. Few things put people off more than exclusionary language.

It only requires you to perhaps use three extra words in the totality of the thread, not really a huge imposition,

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 3:44pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/24 "2023-10-08T15:44:52Z")

</div>

> [@What\_Exit](#):
>
> But you are not the standard. You are just you.

We are all “just yous”. But I still strongly disagree that MSM or FOIA are obscure in either P&E _or_ GD.

---

<div class="post-metadata">

**Author:** ![Procrustus](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/procrustus/32/2994_2.png) [@Procrustus](https://boards.straightdope.com/u/Procrustus)\
**Post date:** [October 8, 2023, 3:45pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/25 "2023-10-08T15:45:32Z")

</div>

> [@MrDibble](#):
>
> Is this a new rule? Because I see nothing about acronyms in the new draft rules.

It doesn’t have to be a “rule” to be best practice. No one got a warning for a rule violation. As I see it, we are just being asked to be self-aware about such things. Makes sense to me. No harm can come of it.

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 3:46pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/26 "2023-10-08T15:46:15Z")

</div>

> [@Novelty\_Bobble](#):
>
> If you want the forums to be a welcoming place and not give off a vibe of “only the cool kids are allowed” then there should be _more_ clarity regarding acronyms.

The vibe spelling them all out like that gives isn’t “Warm and welcoming”, it’s “old fuddy-duddies”.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 3:46pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/27 "2023-10-08T15:46:50Z")

</div>

> [@Procrustus](#):
>
> It doesn’t have to be a “rule” to be best practice. No one got a warning for a rule violation. As I see it, we are just being asked to be self-aware about such things. Makes sense to me. No harm can come of it.

exactly, sensible modding as far as I’m concerned.

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 3:47pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/28 "2023-10-08T15:47:47Z")

</div>

> [@Procrustus](#):
>
> As I see it, we are just being asked to be self-aware about such things.

That goes both ways. Just because a person doesn’t know an acronym, doesn’t mean it _is_ obscure. As a search of past posts of the acronyms in question in P&E or GD would show.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 3:48pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/29 "2023-10-08T15:48:10Z")

</div>

> [@MrDibble](#):
>
> The vibe spelling them all out like that gives isn’t “Warm and welcoming”, it’s “old fuddy-duddies”.

That attitude sort of makes the point for me.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 3:49pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/30 "2023-10-08T15:49:55Z")

</div>

> [@MrDibble](#):
>
> That goes both ways. Just because a person doesn’t know an acronym, doesn’t mean it _is_ obscure. As a search of past posts of the acronyms in question in P&E or GD would show.

So we have the imposition on multiple posters to go away and do multiple searches, or the imposition on the poster to use a few extra words, once.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 8, 2023, 3:51pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/31 "2023-10-08T15:51:00Z")

</div>

Correct, better for one poster to do a little extra work, than many posters.

---

<div class="post-metadata">

**Author:** ![Riemann](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/riemann/32/3133_2.png) [@Riemann](https://boards.straightdope.com/u/Riemann)\
**Post date:** [October 8, 2023, 3:51pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/32 "2023-10-08T15:51:07Z")

</div>

> [@MrDibble](#):
>
> We are all “just yous”.

So if you thought WE was off base with the moderation, really the correct way to approach it would be to ask other readers of P&E if the great majority of them, like you, had no difficulty with any of the acronyms.

---

<div class="post-metadata">

**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\
**Post date:** [October 8, 2023, 3:55pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/33 "2023-10-08T15:55:22Z")

</div>

I don’t think it’s really about acronyms per se. If I’m unfamiliar with TPM, and ask what it is, and am told that it stands for “Talking Points Memo”, then in all likelihood I still don’t know what it means. I only know that “Talking Points Memo” is a news commentary website from seeing it in context, and I see “TPM” in that same context just as often. Likewise “FOIA”: If I didn’t know what the “Freedom of Information Act” was, then expanding the acronym would be meaningless. What I really need to know is that “FOIA” or “Freedom of Information Act” is a law that allows citizens to demand access to government documents.

The expansion of an acronym is not its meaning, merely its etymology. And most of the words we use, we use blissfully ignorant of their etymology.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 4:03pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/34 "2023-10-08T16:03:16Z")

</div>

> [@Chronos](#):
>
> The expansion of an acronym is not its meaning, merely its etymology. And most of the words we use, we use blissfully ignorant of their etymology.

it is one step closer to meaning though, and a reasonable step to do on behalf of the potentially uninformed reader.

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 4:09pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/35 "2023-10-08T16:09:33Z")

</div>

> [@Riemann](#):
>
> really the correct way to approach it would be to ask other readers of P&E if the great majority of them, like you, had no difficulty with any of the acronyms.

Or I could do a straw poll - by, for example, searching and seeing how common the usage already was…

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [October 8, 2023, 4:11pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/36 "2023-10-08T16:11:42Z")

</div>

> [@Procrustus](#):
>
> As I see it, we are just being asked to be self-aware about such things.

Agreed. The question at hand is whether that post was an example of excessive use of initialisms.

> [@Shoeless](#):
>
> Just for the record, as the OP (original poster) of the thread in question, I have no problem with the moderation. As I admitted in a later post, I _did_ overdo it with the TLAs (three letter acronyms).

A casual glance makes it look that way, but in my view there were only two instances of what I’d call bad practice. “SHS” would read with more clarity if you’d just said “Sanders”, and something like “friend” or “associate” instead of BFF. To me, all the other initialisms were clear. “TPM” was obviously not clear to some, but in context it’s only important to know that it’s some site that’s being used as a source.

> [@What\_Exit](#):
>
> FOIA & MSM are far from common.

Sometimes these judgments are subjective, but respectfully, the term “FOIA” – whose common usage is reflected in 577 million Google hits – has been in common use in the media for nearly 50 years, and although it’s not the formal name of the pertinent legislation, the law itself goes back to 1965.

“MSM” is pretty colloquial and less defensible, and its use is probably less common outside political contexts. But it’s certainly been used frequently on this board.

---

<div class="post-metadata">

**Author:** ![Riemann](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/riemann/32/3133_2.png) [@Riemann](https://boards.straightdope.com/u/Riemann)\
**Post date:** [October 8, 2023, 4:18pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/37 "2023-10-08T16:18:18Z")

</div>

> [@MrDibble](#):
>
> Or I could do a straw poll - by, for example, searching and seeing how common the usage already was…

The only quantitative information I get from that search (or from any other search I’ve tried) is “more than 50” posts in P&E containing TPM. I don’t have good intuition for whether \>50 means that it’s widely known.

---

<div class="post-metadata">

**Author:** ![MrDibble](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mrdibble/32/114_2.png) [@MrDibble](https://boards.straightdope.com/u/MrDibble)\
**Post date:** [October 8, 2023, 4:21pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/38 "2023-10-08T16:21:41Z")

</div>

\>50 posts and how many of them are complaints about obscure usage?

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [October 8, 2023, 4:32pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/39 "2023-10-08T16:32:37Z")

</div>

I’d never heard of TPM. I’d never heard of SHS. Neither the person by name, nor certainly her as someone so highly well-known that her very name had been reduced to an acronym.

“SHS” may in fact be utterly standard slang for the AR governor. When used in Arkansas by people from Arkansas. Much like everybody in the USA knew who GWB was while he was President. The whole rest of the country, much less the world, has pretty much no idea who the hell that person is.

I’d never use BFF in a political context, so that too was unfamiliar until I read it 3 times and realized “best friend” was the intended meaning. Jarring.

The overall tone of the writing was breezy insider talking to other breezy insiders. Lots of leaps of logic and the unfamiliar acronyms did not help. Not at all. I’m reminded of the old articles in IIRC Variety, the showbiz industry mag, full of cutesy breezy jargon. Or of diner slang.

If the goal is to be approachable, not off-putting to the interested generally, but not necessarily specifically informed reader, beware of how many total acronyms you’re throwing around. That post almost rose to the point of self-parody.

Another point: A post that is incomprehensible without reading the cite is not a good post. Or at least is not an audience-welcoming post.

---

<div class="post-metadata">

**Author:** ![Novelty\_Bobble](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@Novelty\_Bobble](https://boards.straightdope.com/u/Novelty_Bobble)\
**Post date:** [October 8, 2023, 4:33pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/40 "2023-10-08T16:33:03Z")

</div>

A quick skim down the first posts in that particular forum, perhaps the first 20 threads, gives the following insight into the amount of acronyms used within each first post. (and I am including such “proper” acronyms as the FBI and state acronymns)

The sequence goes something like this…

1,1,2,1,1,2,_ **7** _,1,1,1,0,0,0,2,2,1,1,1…etc

I lost the impetus to go further but who would like to guess what the outlier was?

[Previous page](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272.md?page=1)

[Next page](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272.md?page=3)
