%ents; ]>
The /me Command This specification defines recommended handling of the /me command in XMPP instant messaging clients. &LEGALNOTICE; 0245 Active Informational Standards Council XMPP Core XMPP IM N/A &stpeter; 1.0 2009-01-21 psa

Per a vote of the XMPP Council, advanced specification to Active and changed type from Historical to Informational.

 0.2 2009-01-08 psa

Clarified handling of XHTML-IM formatting; added security consideration for multi-user chat rooms.

 0.1 2008-06-18 psa

Initial published version.

 0.0.1 2008-06-09 psa

First draft.

Many Jabber/XMPP instant messaging clients provide special processing and presentation of the string "/me " at the beginning of a message body. This specification describes the recommended handling of this "command".

The /me command The string "/me " is usually pronounced "slash-me". is a text string that enables a human user to type an action phrase and have it be presented in a special way within an instant messaging client. The text string is followed by a verb or verb phrase, such as "/me laughs" or "/me is logging off now". This command does not result in the generation of any XMPP protocol. Instead, the command is sent as-is (e.g., <body>/me laughs</body>) and the receiving client performs string-matching on the first four characters of the data included in the &BODY; element to determine if the message begins with the string "/me ". If the client finds a match, the receiving client will show the message with a special presentation. It is RECOMMENDED for the client to show the receiving client's understanding of the sender's user name, nickname, or handle On the difference between user names, nicknames, and handles, see &xep0165; and &xep0172;. followed by the verb phrase in italicized text, prepended by the "*" character.

For example, imagine that the Greek god Atlas is in a chatroom with the other gods and types the following text in his IM client:

That text will be sent to all the occupants in the chatroom as follows:

/me shrugs in disgust ]]>

Each recipient's client would then show the message with a special presentation, such as:

* Atlas shrugs in disgust

If the receiving client does not find a match on the string "/me " in the first four characters of the message body, it SHOULD NOT present the text in a special way. For example, the following message bodies do not match:

/meshrugs in disgust /me's disgusted /me shrugs in disgust "/me shrugs in disgust" * Atlas shrugs in disgust Why did Atlas say "/me shrugs in disgust"? ]]>

&xep0071; describes a method for lightweight formatting of a message body using a subset of XHTML. For example, the stanza shown above might be formatted in the color green, as follows.

/me shrugs in disgust

/me shrugs in disgust

]]>

The XHTML-formatted version of the message MUST NOT modify the "/me " command string (e.g., in this case to something like "* Atlas shrugs in disgust") because the recipient might have a different user name, nickname, or handle on file for the sender.

This specification describes the /me command in terms of visual presentation. A receiving client that presents messages aurally MAY modify its presentation of /me commands and SHOULD at a minimum transform the string "/me " into the user name, nickname, or handle of the sender.

&xep0045; rooms send XMPP presence stanzas when people leave and join the room, and receiving clients typically show these presence changes as the equivalent of in-room messages, such as the following transformation of a presence stanza of type unavailable:

*** Atlas has left the room

A sender could attempt to spoof such a leave message by sending an XMPP groupchat message stanza whose body text is "/me has left the room". Although the presentation of presence joins and leaves is determined by the receiving client and therefore such a notification cannot be universally spoofed for all receivers, a client SHOULD differentiate between presence notifications and /me commands (e.g., with different colors and different prepended characters, such as several asterisks for presence notifications and one asterisk for /me commands).

This document requires no interaction with &IANA;.

This document requires no interaction with the ®ISTRAR;.

Thanks to Dave Cridland, Kevin Smith, and Matthew Wild for their feedback and suggestions.