(no subject)

[randomness]

One small irritation of having AIM forward to my phone is having the message buffer fill up and then get some IM with breathless news that I definitely want to reply to, only to find that she's long since logged off AIM, which I can't tell until my reply bounces. The message buffer fills up fast, because people using IM often send multiple messages to the phone in a single thought--that's just the way people talk on IM--and each gets forwarded as a single SMS.

At this point, AIM, Twitter, LJ, GrandCentral, among other services, all point at my phone. The lag is often noticeable, depending on the service.

As I said, it's a small irritation, directed at the technology, not at all at those trying to reach me.

("PREGNANT", huh? I'll give you a call, hon.)

Comments

[r-ness.livejournal.com]

She is! It's very exciting.

(But for the reasons mentioned above, I have no details.)

[chain saw with a magician (from livejournal.com)]

I wouldn't say that's what people do on *all* IM. On AIM, the default clients send (or at least used to) when you press enter, so partial-sentence messages are common, much less partial-thought messages. With protocols where the default clients required a period on an otherwise empty line, or control-D, people tend to compose longer messages.

[r-ness.livejournal.com]

Sure, sure.

Imagine I typoed and said AIM instead of IM. I've used other instant messaging systems in my time, too.

[chain saw with a magician (from livejournal.com)]

Damn AOL for their UI choices.

Awhile ago I thought about something which would aggregate messages based on a timeout, but I never got around to writing it.

[sarabellum.livejournal.com]

uh, what's your twitter handle? I'd like to add you!

[r-ness.livejournal.com]

Yay!

I'm http://twitter.com/Randomness! What's yours?

[sarabellum.livejournal.com]

http://twitter.com/Saramin!

It wasn't me

[maggiebex.livejournal.com]

In case anyone's wondering, that's not me he's referring to....

(anotherjen, that is an EXCELLENT icon!)