Opened 4 years ago

Last modified 13 months ago

#16649 new defect

Cannot Send message beginning with / in XMPP

Reported by: HeXetic Owned by: deryni
Milestone: Component: XMPP
Version: 2.10.10 Keywords:
Cc:

Description

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

Change History (1)

comment:1 Changed 13 months ago by FeepingCreature

This also breaks /code for sending code to Hipchat users.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!