[everdrive]

> Some cases I've seen lately seem to forgo this not out of ignorance but as a form of elitism/knowledge gate keeping.

It's a natural tendency for ingroups. Nearly any video game forum, or anything else that's full of hobbyists will ultimately contain posts that are absolutely full of acronyms. And they're impenetrable. Bear in mind, I'm not defending this behavior, and certainly not disagreeing with you.

[Avamander]

This is why I like Discourse with it's abbreviation explainer. Musicbrainz's community forums have it and it's incredibly nice.

[yjftsjthsd-h]

I'll defend it. Not the elitism, but using jargon/abbreviations/etc. When you're writing something for a larger audience, you should of course target that audience. But when you're on the "inside" writing for people who already have the background knowledge, it's unnecessary friction to stop and think "what terms would a newbie need defined in this?" It breaks the flow of writing/discourse and is probably mostly not needed, because someone coming in not knowing the terms in play can either go look them up, or just ask in their own post. (Granted, this also depends on that being easy; either a jargon dictionary being available, or the forum members being friendly to newbie questions.) I think it's also understandable to apply a small amount of gatekeeping, insofar as that continual beginner questions in the middle of an advanced discussion are just a distraction. The answer to that should be directing them to a more beginner-friendly subforum, but FWIW I do understand why people sometimes act poorly out of frustration.

[ameister14]

The solution to the "unnecessary friction to stop and think "what terms would a newbie need defined in this?"

If you're writing a paper, define every acronym the first time you use it.

If you're in a forum with a set of acronyms known to all, define them in a sticky or the forum readme.

[alias_neo]

Oh no, I understand your point, no misunderstanding here. It's one of the reasons I keep a technical blog, as an engineer, if I learn the hardest thing I've learned this $timeperiod, I want to share it, as clearly and understandably as I can. I fully support and encourage knowledge sharing, and it hurts just that little bit more when I see it being hoarded.

[yazan94]

Seriously? You want to be able to join a community you might not be familiar with and understand the lingo/jargon off the bat? Of course people will abbreviate things when the word/phrase is sufficiently long, commonly used, and the abbreviation mutually understood (brb, tldr, OOP, etc.). There is no elitism involved, if you don't understand something either Google it or ask. No reason to act snobbish because people cater the the most common denominator in a community rather than the lowest.

[alias_neo]

Not exactly, what I'm arguing against is writing something technical, intended to educate non-experts in the field (the experts don't need your report/paper/thing) and then not providing them with the information they need to background research the things you refer to in abbreviations or acronyms.

And I'm not saying this is _my_ solution, this was literally taught to me in engineering first year.