[arcfour]

LPE is a very well-known acronym within the security community, it's not purely academic or obscure or anything.

I agree that it would be a good idea to define it explicitly when writing for a broader audience, but I don't think it's particularly egregious that they didn't. It's certainly something I could see myself forgetting.

Then again, the whole writeup appears to be AI-generated, so...

[globular-toast]

Sure, but the target audience of copy.fail is surely not the security community but regular sysadmins who probably don't otherwise follow as closely.

[a96]

I would absolutely expect a sysadmin in particular to know and understand the term and acronym.

[globular-toast]

Well I would expect a sysadmin to have already been following the kernel mailing lists and not even need to look at copy.fail.

In fact, why do people even write stuff down? Everyone should just know everything.

[SoftTalker]

It's still just courteous to define acronyms on first use, it doesn't take any real effort to do that.

[a96]

Very much true, and I would never criticize that. Just that this term would be particularly obscure to a sysadmin which seems completely backwards.

[plg94]

Understanding a term with the help of context is very different from guessing what the letters of an acronym might mean. The latter is more like a crosswords puzzle, and a totally unneccessary task for the reader.

[1970-01-01]

It is nowhere near this. There are very few acronyms in the IT world that are actually well-known outside of it. LPE is less well-known than LVAD or MCU.

https://www.acronymfinder.com/Information-Technology/MCU.htm...

https://www.acronymfinder.com/LVAD.html

https://www.acronymfinder.com/Information-Technology/LPE.htm...

[dataflow]

> LPE is less well-known than LVAD or MCU.

I knew what LPE stands for but not the others. (I've seen MCU mentioned and kinda had a vague feeling for what it is. Never even seen LVAD.)