[Pidgin] #16649: Cannot Send message beginning with / in XMPP

Pidgin trac at pidgin.im
Thu Apr 30 14:49:12 EDT 2015

#16649: Cannot Send message beginning with / in XMPP
 Reporter:  HeXetic  |      Owner:  deryni
     Type:  defect   |     Status:  new
Milestone:           |  Component:  XMPP
  Version:  2.10.10  |   Keywords:
 (See bugs #10114 and #15406 for previous issues related to chat messages
 beginning with slash)

 Pidgin denies sending XMPP messages beginning with / (forward-slash) that
 do not have a second / before any whitespace.

 This behaviour is inconsistent, and furthermore there is no way to
 "escape" the slash; instead, the IRC command "/say /something" must be
 used, which is incongruous for something that is not IRC.

 Currently, to send the text "/say", a sender using Pidgin will have to
 type "/say /say".

 As far as I can tell, the only valid "slash command" for XMPP chat is
 "/me", but XMPP spec XEP-0245
 ([https://xmpp.org/extensions/xep-0245.html]) for this feature explicitly
 says that sending clients must transmit /me "commands" verbatim, and it is
 up to the receiving chat client to display the line differently, if they
 choose. Therefore, there is no reason for Pidgin to enforce "valid slash
 commands" on the sender when communicating over XMPP. XMPP sender-side
 parsing of these commands should be removed, as should the special
 behaviour of "/say".

Ticket URL: <https://developer.pidgin.im/ticket/16649>
Pidgin <https://pidgin.im>

More information about the Tracker mailing list