# 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:** 7

<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 11, 2023, 5:39pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/121 "2023-10-11T17:39:01Z")

</div>

If the standard for posting in particular forums here is going to be set at the same level as University term papers, the PTB need to say _that_.

So that I can avoid them, and stick to ones that are treated like the informal social media spaces they actually are.

---

<div class="post-metadata">

**Author:** ![Left\_Hand\_of\_Dorkness](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/left_hand_of_dorkness/32/7156_2.png) [@Left\_Hand\_of\_Dorkness](https://boards.straightdope.com/u/Left_Hand_of_Dorkness)\
**Post date:** [October 11, 2023, 5:39pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/122 "2023-10-11T17:39:30Z")

</div>

> [@Jasmine](#):
>
> When I had English literature, the rule given to us was that, upon the first use of an acronym, the full name was given in parenthesis. After that, the acronym could be use freely throughout the rest of the composition. Example: “Today, NASA (National Aeronautics and Space Administration) announced a new initiative aimed at getting a manned exploration mission to the outer planets.”

When I had English literature, the rule given to us was that any fact beyond the universally known should be cited using MLA format. I don’t think the syllabus spelled out what MLA stood for, though.

Point being, there are plenty of rules from college courses that don’t apply to a messageboard, and we should be leery of thinking they’re universal rules.

---

<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 11, 2023, 5:40pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/123 "2023-10-11T17:40:51Z")

</div>

> [@Jasmine](#):
>
> When I had English literature, the rule given to us was that, upon the first use of an acronym, the full name was given in parenthesis. After that, the acronym could be use freely throughout the rest of the composition.

To claim that this is an absolute rule is just not helpful. Obviously we are not spelling out what USA or SDMB mean. We all agree that there are some acronyms that don’t need to be explained, we’re just haggling over where the line is.

---

<div class="post-metadata">

**Author:** ![Jasmine](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jasmine/32/2964_2.png) [@Jasmine](https://boards.straightdope.com/u/Jasmine)\
**Post date:** [October 11, 2023, 5:50pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/124 "2023-10-11T17:50:16Z")

</div>

> [@Left\_Hand\_of\_Dorkness](#):
>
> Point being, there are plenty of rules from college courses that don’t apply to a messageboard, and we should be leery of thinking they’re universal rules.

> [@Riemann](#):
>
> To claim that this as an absolute rule is just not helpful.

I reread my post, and I didn’t see anything that indicated that I think it is supposed to be some kind of established rule. I just cited it as an example of how indicating the meaning of an acronym in written text is considered important. I just googled this, and the recommendation was the opposite; write the full name and put the acronym in parenthesis. Henceforth, use the acronym only. It also said it wasn’t necessary if the acronyms in question “are familiar to most people”. They gave two acronyms as examples of acronyms being “familiar to most people”, and I didn’t recognize either one of them. LOL

---

<div class="post-metadata">

**Author:** ![Left\_Hand\_of\_Dorkness](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/left_hand_of_dorkness/32/7156_2.png) [@Left\_Hand\_of\_Dorkness](https://boards.straightdope.com/u/Left_Hand_of_Dorkness)\
**Post date:** [October 11, 2023, 5:55pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/125 "2023-10-11T17:55:03Z")

</div>

> [@Jasmine](#):
>
> I just cited it as an example of how indicating the meaning of an acronym in written text is considered important.

_in the context of academic papers_. There are plenty of rules in academic papers (e.g., don’t use contractions) that aren’t true elsewhere.

Imagine that I text my wife:

> By the way (BTW), I’m stopping at the store on my way home. Need anything?

> For what it’s worth (FWIW), I already got everything on our list.

> You’re the best (YTB)! I love you (ILY)!

That would follow the rules from my English Lit class, but would be really fucking weird for the context of a text thread.

It’s not that I think you were proposing a universal rule; it’s that I think the rules from English Lit classes aren’t especially relevant for this conversation.

---

<div class="post-metadata">

**Author:** ![DSeid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dseid/32/20194_2.png) [@DSeid](https://boards.straightdope.com/u/DSeid)\
**Post date:** [October 11, 2023, 7:12pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/126 "2023-10-11T19:12:34Z")

</div>

The obligation goes both ways. As the speaker/writer I should try to use words that my audience understands, or define them as I use them. As the listener/reader I learn by being exposed to unfamiliar words and abbreviations and shouldn’t get upset for not having things made simple enough for me to understand with no work required.

I am just honesty surprised that FIOA is in the frequently not already understood group for the crowd interested in politics.

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [October 11, 2023, 7:14pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/127 "2023-10-11T19:14:53Z")

</div>

> [@DSeid](#):
>
> I am just honesty surprised that FIOA is in the frequently not already understood group for the crowd interested in politics.

I honestly don’t know what FIOA means.

Googling, it means “file input/output area”.

---

<div class="post-metadata">

**Author:** ![Johnny\_Bravo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/johnny_bravo/32/493_2.png) [@Johnny\_Bravo](https://boards.straightdope.com/u/Johnny_Bravo)\
**Post date:** [October 11, 2023, 7:16pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/128 "2023-10-11T19:16:04Z")

</div>

Ah, guadere’s law in action, or at least a corrolary.

It’s FOIA, freedom of information act.

---

<div class="post-metadata">

**Author:** ![DrDeth](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@DrDeth](https://boards.straightdope.com/u/DrDeth)\
**Post date:** [October 11, 2023, 7:49pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/129 "2023-10-11T19:49:53Z")

</div>

> [@What\_Exit](#):
>
> BFF was an odd usage in that thread. I think most regular Message Board, Chat or Social Media users know BFF = Best Friends Forever, but you don’t think it was rather odd in context of talking about a sitting Governor?

Yes, I did.

> [@What\_Exit](#):
>
> I and others don’t know MSM without looking it up.

In context MSM was obvious to me, but MSM has several meanings.

> [@Johnny\_Bravo](#):
>
> If the convention is “don’t overdo abbreviations in serious OPs because it impedes understanding,” that’s all that needs to be said.
> 
> Justifying whether any given abbreviation is or isn’t “common” is injecting way too much subjectivity into the moderation, which is a wholly subjective process to begin with.

Very good post, I concur.

> [@Johnny\_Bravo](#):
>
> It’s FOIA, freedom of information act.

One of the acronyms that needs context.

---

<div class="post-metadata">

**Author:** ![DSeid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dseid/32/20194_2.png) [@DSeid](https://boards.straightdope.com/u/DSeid)\
**Post date:** [October 11, 2023, 8:36pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/130 "2023-10-11T20:36:19Z")

</div>

Okay. Embarrassing typo in context. My bad.

Freedom of Information Act (FOIA) requests are fairly frequently referenced in political discussions in general.

In the context of a scandal discussion in which information not publicly shared is a subject I imagined that the meaning of “FOIA” was understood by most and easily figured out by the few who did not. I would have had no pause in using it as a common knowledge word. Again, I seem to have been mistaken.

---

<div class="post-metadata">

**Author:** ![Atamasama](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/atamasama/32/12961_2.png) [@Atamasama](https://boards.straightdope.com/u/Atamasama)\
**Post date:** [October 11, 2023, 8:37pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/131 "2023-10-11T20:37:30Z")

</div>

> [@DSeid](#):
>
> Okay. Embarrassing typo in context. My bad.

Yup, I was just giving you crap. 😆

I thought it was ironic.

But yes, I got what FOIA was in context when I first read the original thread too.

---

<div class="post-metadata">

**Author:** ![I\_Love\_Me\_Vol.I](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/i_love_me_vol.i/32/521_2.png) [@I\_Love\_Me\_Vol.I](https://boards.straightdope.com/u/I_Love_Me_Vol.I)\
**Post date:** [October 11, 2023, 9:47pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/132 "2023-10-11T21:47:03Z")

</div>

> [@LSLGuy](#):
>
> The former approach is “Here’s a TLA. For you who don’t know it, just go fight your own ignorance: I’ll be here pointing out how ignorant you are.”
> 
> The latter approach is “Here’s a TLA. For you who don’t know it, I’ll help alleviate some of that right here right now.”
> 
> One fights ignorance, the other insults it.

Yes.

What I’ve seen on the SDMB is posters dismissively telling people “just Google it!” when asked to clarify an acronym. They don’t seem to realize that you’re asking for clarification because not just you, but many other Dopers are also having to Google the term when it easily could have been spelled out by the poster.

If, hypothetically, I write a post that has a paragraph in French and people ask me to explain what it means or otherwise take me to task should I just respond “Google it and learn something, you lazy ass” ?

---

<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 11, 2023, 9:53pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/133 "2023-10-11T21:53:15Z")

</div>

> [@I\_Love\_Me\_Vol.I](#):
>
> If hypothetically, I write a post that has a paragraph in French and people ask me to explain what it means or otherwise take me to task should I just respond “Google it and learn something, you lazy ass” ?

Unless it were a French-speaking forum. Context is everything.

I really don’t see the point in chipping in with examples where an explanation would obviously be necessary. It’s just as easy to cite examples (USA, SDMB) where an explanation every time would be silly.

We all ultimately agree that there’s a line _somewhere_ dividing abbreviations that should be explained from those that should not, and where that line is will always be a judgment call based on the context of the conversation and common sense.

---

<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 11, 2023, 9:56pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/134 "2023-10-11T21:56:12Z")

</div>

> [@DSeid](#):
>
> Freedom of Information Act (FOIA) requests are fairly frequently referenced in political discussions in general.
> 
> In the context of a scandal discussion in which information not publicly shared is a subject I imagined that the meaning of “FOIA” was understood by most and easily figured out by the few who did not. I would have had no pause in using it as a common knowledge word. Again, I seem to have been mistaken.

Why do you think you were mistaken? “FOIA” is **very** commonly used in journalism, and especially in political discussions. It should not need explanation in a P&E thread, **especially** when in a context like “reporter files FOIA request for expense reports” where its exact meaning doesn’t even matter to understanding the sentence.

Again, I think the awkward and off-putting sentence about “BFF of SHS” is likely what triggered all this.

Examples of use of “FOIA” in the media without expanding the acronym:

[![](https://i.imgur.com/2zjzaj0.jpg) ](https://i.imgur.com/2zjzaj0.jpg)

---

<div class="post-metadata">

**Author:** ![I\_Love\_Me\_Vol.I](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/i_love_me_vol.i/32/521_2.png) [@I\_Love\_Me\_Vol.I](https://boards.straightdope.com/u/I_Love_Me_Vol.I)\
**Post date:** [October 11, 2023, 9:57pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/135 "2023-10-11T21:57:13Z")

</div>

> [@Riemann](#):
>
> We all ultimately agree that there’s a line _somewhere_ dividing abbreviations that should be explained from those that should not, and where that line is will always be a judgment call based on the context of the conversation and common sense.

That is true. It’s the dividing line that is most contentious.

---

<div class="post-metadata">

**Author:** ![Munch](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/munch/32/5281_2.png) [@Munch](https://boards.straightdope.com/u/Munch)\
**Post date:** [October 11, 2023, 9:59pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/136 "2023-10-11T21:59:45Z")

</div>

> [@I\_Love\_Me\_Vol.I](#):
>
> What I’ve seen on the SDMB is posters dismissively telling people “just Google it!” when asked to clarify an acronym.

No you haven’t. You might have seen “that was easy to Google” or “that’s a pretty common word that Google would have solved for you”. But I haven’t EVER seen someone be as dismissive as “just Google it”.

---

<div class="post-metadata">

**Author:** ![Shalmanese](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@Shalmanese](https://boards.straightdope.com/u/Shalmanese)\
**Post date:** [October 11, 2023, 10:00pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/137 "2023-10-11T22:00:06Z")

</div>

> [@What\_Exit](#):
>
> BFF = Best Friends Forever, but you don’t think it was rather odd in context of talking about a sitting Governor?

The oddness was kind of the point, to emphasize how strange the entire story was. BFF is an acronym that has entirely eclipsed it’s original expansion and now means something totally specific and unique. It can’t be replaced with another word in any way that doesn’t significantly compromise the intent of the writing.

> [@What\_Exit](#):
>
> SHS was far less clear than just typing Sanders. The standard of first time typing Sarah Huckabee Sanders (SHS) is a good one.

Her name isn’t Sanders. Referring to her as that would be as strange as referring to AOC as Cortez. Either you write out Huckabee Sanders every time or you call her Sarah or you use SHS.

> [@What\_Exit](#):
>
> **FOIA** is pretty rare though, maybe 55 times ever in P&E. So it is not commonly used.

A search for “Freedom of Information” returns 39 results and “Freedom of Information Act” returns 34. The concept itself is fairly niche, regardless of how you refer to it. Expanding it from the initialism to the entire phrase isn’t likely to improve comprehension substantially because either you know what it’s referring to or you have to google it anyway. I’ve seen it both ways but I wager I’ve seen it referred to as FOIA _more_ than I’ve seen the full phrase.

---

<div class="post-metadata">

**Author:** ![DSeid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dseid/32/20194_2.png) [@DSeid](https://boards.straightdope.com/u/DSeid)\
**Post date:** [October 11, 2023, 10:09pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/138 "2023-10-11T22:09:22Z")

</div>

> [@wolfpup](#):
>
> Why do you think you were mistaken?

Because a reasonable number of posters are claiming they are previously unfamiliar with it.

> [@Shalmanese](#):
>
> or you call her Sarah

Personally I detest referring to politicians by their first names, and the tendency to more frequently do so with women politicians. This particular politician’s proper name is honestly long enough to type out that after first use initials makes sense.

---

<div class="post-metadata">

**Author:** ![Dr.Strangelove](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dr.strangelove/32/6613_2.png) [@Dr.Strangelove](https://boards.straightdope.com/u/Dr.Strangelove)\
**Post date:** [October 11, 2023, 10:19pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/139 "2023-10-11T22:19:53Z")

</div>

> [@Shalmanese](#):
>
> BFF is an acronym that has entirely eclipsed it’s original expansion and now means something totally specific and unique.

If that’s the case, it’s even more important not to use it if clear communication is the goal.

---

<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 11, 2023, 10:22pm UTC](https://boards.straightdope.com/t/contextual-acronyms-should-be-fine/991272/140 "2023-10-11T22:22:46Z")

</div>

> [@Shalmanese](#):
>
> Her name isn’t Sanders. Referring to her as that would be as strange as referring to AOC as Cortez.

“As strange as” seems an odd thing to say when she isn’t Hispanic.

Of course, the only courteous thing is to address people the way they prefer, but do you have a cite that she doesn’t like being referred to by her last name? She is called “Sanders” throughout her Wikipedia article, I’d have thought she would have asked for it to be changed if she didn’t like it. She’s called “Ms.Sanders” throughout this NY Times article, and they are careful about stuff like this.

> **[In Arkansas, a $19,000 Lectern for the Governor Draws Scrutiny](https://www.nytimes.com/2023/10/10/us/sarah-huckabee-sanders-arkansas-lectern.html)**
>
> Gov. Sarah Huckabee Sanders is facing criticism over the expense, and a whistle-blower’s accusation that her office altered records to cover up how it was paid for.

Also called “Sanders” by the _The New Yorker_, which is even more obsessive about getting things like this correct.

> **[Sarah Huckabee Sanders Lends Her Impeccable Reputation for Honesty and...](https://www.newyorker.com/humor/borowitz-report/sarah-huckabee-sanders-lends-her-impeccable-reputation-for-honesty-and-credibility-to-defending-trump)**
>
> “If the comments attributed to the President have alarmed voters, Sarah’s vouching for him should put an end to that,” an aide said.

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

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