[Pidgin] #16833: Attention (XEP-0224) isn't sent even though the other client supports it.

Pidgin trac at pidgin.im
Tue Dec 29 16:37:47 EST 2015

#16833: Attention (XEP-0224) isn't sent even though the other client supports it.
 Reporter:  Arancaytar  |      Owner:  deryni
     Type:  defect      |     Status:  new
Milestone:              |  Component:  XMPP
  Version:  2.10.11     |   Keywords:
 It's quite possible that I'm doing something wrong, but here's what

 1. Pidgin is connected with XMPP account A.
 2. My client (using Strophe.js) connects with XMPP account B on another
 server and sends an undirected <presence>. Because A and B are mutually
 subscribed, both Pidgin and my client get each others' presences.
 3. A and B can message each other with no problem.
 4. B can request disco#info on A, and the response contains `<feature
 var="urn:xmpp:attention:0"/>` as expected, since Pidgin implements it.
   (If Pidgin did a disco#info on B, it would see the same thing, since my
 client also advertises that feature.)

 B can send a message with `<attention xmlns="urn:xmpp:attention:0"/>` in
 it, and Pidgin will handle it correctly.

 But I can't get Pidgin to even try to buzz me back. It will report "Unable
 to buzz, because [B] does not support it or does not wish to receive
 buzzes now." It doesn't seem to make any attempt at service discovery
 before assuming this.

 Did I miss some kind of negotiation or handshake that would get Pidgin to
 do service discovery, or is it simply using a hardcoded list of clients
 that support this feature?

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

More information about the Tracker mailing list