Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Very Short Reply Expected

blog.vrypan.net

Post reply on HN
Print view View original

51–60 of 232 posts

Re: Very Short Reply Expected

#51

Post by lenazegher »

danbruc wrote: post #17
thatthatis wrote: post #9

Earlier quoted context omitted.

Interesting point. Is VSRE something that empowers the respondent to choose: A "social out from a full polite response"? Or is it a "social obligation to provide a short response?"

Make it explicit - VSR A vs VSR E , acceptable vs expected. But this makes the whole thing unnecessarily complex and I would prefer VSRA - I am fine with getting a very short reply. If it is not possible a, long reply is also fine but try to keep it as short as possible. Different suggestions from the comments. CURT - condensed unfussy reply tolerable CURT - CURT unfussy reply tolerable NLRN - no long reply needed TC…

How about CURT - condensed unfussy reply tolerable

Re: Very Short Reply Expected

#52

Post by bluehex »

read wrote: post #30
endgame wrote: post #10

Earlier quoted context omitted.

You could probably call it a meat-level communication hack or something. I like it, but I'd probably use it in the subject line. Similar to how some people use to signal that an email has no body. Now let's see if it gains traction.

The trouble with EOM is that you still need to click on the email you received to un-bold it. EOM or not, you are still opening it.

If you read your email on a desktop, or from the the gmail website I would definitely recommend learning the keyboard shortcuts so you don't have to click. In just a few seconds I can star all the ones in my inbox that I plan to read, and archive the rest including the EOM short mails. I do end up archiving a lot of unread mail this way but that rarely bothers me when searching for old mail.

Re: Very Short Reply Expected

#53

Post by Wintamute »

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 ...

Re: Very Short Reply Expected

#54

Post by reinhardt »

lwat wrote: post #50
TeMPOraL wrote: post #43

Earlier quoted context omitted.

This is not social awkwardness. This is social efficiency.

You say efficient, we say awkward.

Awkward would be to just go ahead and start replying in one word without trying to establish a netiquette protocol.

Re: Very Short Reply Expected

#55

Post by TylerE »

Wintamute wrote: post #53

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 ...

I fail to see how "vis-ree" is any harder to pronounce thatn "roff-ull", "af-ack", or "em-ho"

Re: Very Short Reply Expected

#56

Post by fudged71 »

TazeTSchnitzel wrote: post #49
fudged71 wrote: post #48

Earlier quoted context omitted.

It gets suspicious if you write this and you don't have an iPhone ;)

"Sent from my Samsung" "Sent from my Windows Phone" "Sent from my $OEM" They all follow the same pattern these days.

Hotmail syndrome. I'm going to change mine to say "Sent from Google Glass" just for kicks. "This message transcribed from an awkwardly public soundbite"

Re: Very Short Reply Expected

#58

Post by andrewvc »

TeMPOraL wrote: post #43
andrewvc wrote: post #40

Annnnnnd this is why geeks have a reputation for social awkwardness.

This is not social awkwardness. This is social efficiency.

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 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.

Re: Very Short Reply Expected

#59

Post by reinhardt »

TazeTSchnitzel wrote: post #49
fudged71 wrote: post #48

Earlier quoted context omitted.

It gets suspicious if you write this and you don't have an iPhone ;)

"Sent from my Samsung" "Sent from my Windows Phone" "Sent from my $OEM" They all follow the same pattern these days.

I prefer "Sent from my rotary phone". No need for free advertisement or misplaced smugness about a disposable gizmo.

Re: Very Short Reply Expected

#60

Post by danbruc »

lenazegher wrote: post #51
danbruc wrote: post #17

Earlier quoted context omitted.

Make it explicit - VSR A vs VSR E , acceptable vs expected. But this makes the whole thing unnecessarily complex and I would prefer VSRA - I am fine with getting a very short reply. If it is not possible a, long reply is also fine but try to keep it as short as possible. Different suggestions from the comments. CURT - condensed unfussy reply tolerable CURT - CURT unfussy reply tolerable NLRN - no long reply needed TC…

How about CURT - condensed unfussy reply tolerable

Than let's make it recursive.

  CURT - CURT unfussy reply tolerable
Post reply on HN