Social conventions aren't established by protocol drafts, they're organic.
Also, people write long replies for a reason. Wording indicates emotional state. If you have trouble reading emotional state, you don't care. If, like most people, you do care, then this proposal is ridiculous.
"How about we schedule lunch next week? VSRP"
VSRP: "Can't make it, extremely busy. Maybe next month?"
FULL: "Sorry to say, I can't make it. I'd really like to but we're in a crunch right now, and I've got a booked calendar. Perhaps next month when things have died down? I'd really like to catch up but this month is already overwhelming"
I might take the VSRP as a bit of an affront. The full explanation however is quite understandable.
There's a time and place for long communication and it's in person. Not in an email.
People are more important than "your time", and a failure to realize that is a dehumanization of the other party. The latter response demonstrates emotional sensitivity towards the other person in the conversation. Among most people, that is important. It makes the other party feel good. It reinforces that you do care about the other party enough to ensure that they are not potentially affronted by terse communication. This is why normal people, lacking in the self-absorption your post exudes, do this sort of thing.
And in any case it doesn't take more than a few seconds to write or read; when the hell did four sentences become a "bloody novel"?
Welcome to the generation of twitter. :)
"potentially affronted" is not a thing I particularly care about. If I want to affront you, oh you'll know. Believe me.
More interestingly, the only people I've ever seen write email like in that example are people who send/receive less than about 5 emails a day. The more they have to process daily, the shorter their messages become.
In written contexts, there often isn't. Without what I would call a significant amount of personal history, there isn't enough data and there aren't nonverbal cues to demonstrate terseness versus rudeness. Many people will assume rudeness, because that's what that pattern generally looks like.
Also, there's the nerd stereotype of being a standoffish jerk to consider, which you are doing a bang-up job of reinforcing with crap like this:
> "potentially affronted" is not a thing I particularly care about. If I want to affront you, oh you'll know. Believe me.
This is the sort of thing I would expect a teenager in the throes of self-absorption to say. I say this because I did. Then I grew up.
You're being an asshole. You'll be happier if you stop.
Not at all. I've noticed a general uptick in happiness since I started taking people at face value and stopped worrying about walking on egg shells for no reason whatsoever.
You know what you get by trying too hard to be polite and making absolutely certain no feelings could possibly get hurt? The language bureaucrats use to say "Your tax basis this year is X" on two A4 pages.
I hate it when people beat around the bush. So I avoid doing it.
Perhaps the acronym should've been something like VSRA (Accepted), or SROK (Short Reply OK) instead.
> Social conventions aren't established by protocol drafts, they're organic.
Organic stuff lends itself better to optimization - by constant feedback.
I often have to write FULL responses like the example you provided and find this incredibly annoying. There are many reasons to that. Sometimes, I just don't have time to craft a nice sounding and formatted answer at the moment (if I'm going FULL, I won't tolerate any spelling mistakes, typos, double spaces, etc. If one commits oneself to quality, it should be 100%).
But sometimes, the crafting of the answer FULL requires too much cognitive power. Quite often in situations similar to your example, my real reaction is a linear combination of things like "I'm not sure if I have time", "I wanted to go to a party on friday", "I'm worried what my girlfriend will think of this", "I really need some rest", "I'm worried we won't have much to talk about and it will feel awkward", "I'd really like to save this money for 3D printer electronics", "goddammit, I'll break my ketosis again if I'll eat a normal lunch with you", etc. It takes a bit of effort to craft a message that is a) nice, b) not an outright lie. A bit of effort I don't always want to make at the very moment.
So yes, I'm all-in for any kind of social protocol that would allow me to decline/postpone requests without having to explain myself to other party just for the message to sound polite.
The obvious use case is you are communicating with someone for the first time or for not so long, you are fine with a short reply and you know that recipient would like to write a short reply but will not do so in order not to sound impolite.
"Can't. Next month?"
"No. Next month?"
1) Because it isn't always worth the cost
2) Because we don't always fully understand the systems we are modifying
Which hearkens back to, "Don't fix it if it ain't broke". Inefficient is not automatically broke.
Don't fix it if it ain't broke seems to run counter to innovation. I'd try for improvement on a functional system if there's a positive expected outcome.
Heh. Forget IANAL; we need IANAA.