On Tuesday 10 June 2008 14:36:24 Rachel Blackman wrote: > > On 06/10/2008 2:51 PM, Tomasz Sterna wrote: > >> Dnia 2008-06-09, pon o godzinie 22:32 -0500, XMPP Extensions Editor > >> > >> pisze: > >>> The XMPP Extensions Editor has received a proposal for a new XEP. > >>> > >>> Title: The /me Command > >>> > >>> Abstract: This specification defines recommended handling of the /me > >>> command in XMPP instant messaging clients. > >> > >> -1 > >> > >> This is a crude hack and I'm against encouraging it. > > > > This is historical documentation of something every jabber client > > under > > the sun has been doing since 1999. > > This is moreover something that just about every IM client -- > including iChat -- now supports in normal chat across AIM, MSN, Yahoo > and so on. You can change it, sure, so that things have to be a > specific 'action' style, but I guarantee you a lot of clients won't > bother to change.
I remember seeing a multi-IM client that would only do the "/me" emote rendering when using Jabber. This emphasizes the fact that /me is a Jabber protocol nuance, worth documenting. > I mean, I don't much care either way, but I think there are probably > better places to focus the energy of forcing adoption. (Like a > standardized file transfer that works between all the clients, instead > of Google Talk off in their own little world, and many servers not > supporting s5b proxies, and a Jingle file transfer spec that isn't > widely adopted yet.) :) This is getting tiring. :) The Google Talk desktop client isn't even maintained, afaik. I'll give you that the lack of S5B proxies is a mystery though. -Justin
