Don't try to be funny in your docs. If you want to convey information, make it clean, precise, and to the point. Do not assume and do not distract.

Please.

P.S. Jokes are not totally forbidden, but they should be more subtle and not so intrusive as "You are asking me a question, but here I'll give you a performance instead of an answer".

Yes, the word ‘oof’ denotes a performance. The etymology dates back to early vaudeville days when Barker Malarkey used it to start the Famous Malarkey Family’s drag show…

Except that’s not true. That whole paragraph is a load of malarkey.

It’s a word. You don’t know the person involved and you’re making more awful assumptions based upon three letters.

Now, reverse it backward. Not only I don't know them, but neither they know me. Can you see the issue now?

There is such a thing as technical writing style and it is about the relevance of information pieces and the relations between them.

it's not empathetic, it's an attempt to disarm and minimize, and it's insulting.

There is no person on the other end. There is a program, so definitely a drone, maybe wrote by offshored developers maybe not, definitely overworked or they'll have the time to fix the bug or implement the feature instead of replacing it with a message.

A person doing the export manually would be OK as a workaround and instead all they have is that message. That's not OK.

Consider the platform demographic before responding this way. It can be an advantage and a disadvantage.