Live data from Hacker News

Very Short Reply Expected

blog.vrypan.net

121–130 of 232 posts

Re: Very Short Reply Expected

#122

The most viral/popular acronyms are easily pronounceable, I think. Acronyms like lol, rofl, afaik, imho etc. Not that you go around saying them all the time, but you can easily pronounce them in your own head so I think they tend to stick there and flow into your text easily. Maybe something along the lines of "sro" (short reply ok) would be better ...

You pronounce lol, rofl, afaik, imho? Talk about awkward.

Re: Very Short Reply Expected

#123
post #74

If it means "very short reply OK" why isn't it VSRO? "Expected" almost sounds too demanding to me...like you'll actually be disappointed if I write a little more.

"Very short reply Welcome" VSRW was discussed elsewhere to make clear that it is an invitation but not an expectation.

I like this too, I might start using it but with a text expander so others don't reply asking what the hell it means.

Re: Very Short Reply Expected

#124
post #104
post #101

I love this. I'm also extremely fond of EOM (short for End Of Message. An email with a short subject and no body). Often I send EOMs to imply a VSRE. For example, "Grill tonight? Have burgers. Off work @ 6. EOM" Very interested in learning others.

NNTR: 'no need to reply' is another common abbreviation. Pro-tip: Use them as TextExpander snippets to avoid getting another message asking you to clarify what EOM/NNTR means as only a subset of people are familiar with & use these abbreviations.

Until everyone starts communicating this way, and it becomes completely normal.

Remember, a geek invented the smiley ( and I'm sure there are many other examples).

Re: Very Short Reply Expected

#126
post #101

I love this. I'm also extremely fond of EOM (short for End Of Message. An email with a short subject and no body). Often I send EOMs to imply a VSRE. For example, "Grill tonight? Have burgers. Off work @ 6. EOM" Very interested in learning others.

NT: No text

This one is shorter than the rest, and easy to grok. VSRE OR EOM? I'd have to look those up.

Re: Very Short Reply Expected

#127
post #112

Earlier quoted context omitted.

No, you've got it all wrong! Geeks aren't socially awkward, they're socially "efficient" 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. An example: "How about we schedule lunch next…

Personally, I find the latter response just disrespectful of my time. If all you want/need to say is you can't make it, don't write a bloody novel! All I need is an answer. There's a time and place for long communication and it's in person. Not in an email.

This is strange to me. It was just 3 sentences, and you were the one who asked them for a response.

Re: Very Short Reply Expected

#128
post #112

Earlier quoted context omitted.

No, you've got it all wrong! Geeks aren't socially awkward, they're socially "efficient" 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. An example: "How about we schedule lunch next…

Personally, I find the latter response just disrespectful of my time. If all you want/need to say is you can't make it, don't write a bloody novel! All I need is an answer. There's a time and place for long communication and it's in person. Not in an email.

Four sentences constitutes a "novel" now? What is going on in the world that people dont have the time, or worse seem not to care, to communicate in a normal way?

Re: Very Short Reply Expected

#129
post #112

Earlier quoted context omitted.

No, you've got it all wrong! Geeks aren't socially awkward, they're socially "efficient" 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. An example: "How about we schedule lunch next…

Personally, I find the latter response just disrespectful of my time. If all you want/need to say is you can't make it, don't write a bloody novel! All I need is an answer. There's a time and place for long communication and it's in person. Not in an email.

That would be a problem between you and...you.

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"?

Post reply on HN