Opened 4 years ago

Last modified 3 years ago

#16548 new defect

Pidgin sends chatstates (XEP-0085) when the server didn't advertise it

Reported by: yurivict Owned by: deryni
Milestone: Component: XMPP
Version: 2.10.11 Keywords:
Cc:

Description

disco#info didn't return 'chatstates', yet Pidgin still sends them.

Section 4 in XEP-0085 says: "If an entity supports the Chat State Notifications protocol, it MUST advertise that fact ..." This implies that chatstates support is optional.

pidgin-2.10.11 on FreeBSD 10

Change History (1)

comment:1 Changed 3 years ago by dx

  • Component changed from unclassified to XMPP
  • Owner changed from EionRobb to deryni

Is this breaking some other client?

According to the code this is done for compatibility with earlier libpurple versions.

The spec doesn't say it's wrong to send these anyway. The "Generation of Notifications" section says we SHOULD discover or MAY implicitly discover by sending <active> first to indicate that chatstates are supported. There's no MUST NOT.

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!