On Thu Oct 15, 2026 at 8:35 PM CEST, Thilo Molitor wrote:
The privacy aspects are discussed here: https://xmpp.org/extensions/xep-0353.html#security
Because exchanging messages with other entities is effectively a presence leak, an XMPP client that implements the receiving side of this specification MUST disable sending of accept messages by default and MUST enable the feature only as a result of explicit user confirmation. Such confirmation can be provided per request, by automatically allowing requests received from Jingle initiators in the responder's contact list, or through some other suitable means as long as sending accept messages does not occur by default.
But granted this is not ideal for several reasons: 1. the <accept/> element was a :1 namespace one, but we rolled that back to the :0 namespace where the same functionality is called <proceed/>. Also <ringing/> should be added in that section of the XEP as well.
Indeed, I read that section as being about <proceed/> -- indicating that a device is ringing can hardly be called "sending [an] accept message".
Regarding Dino never sending <ringing/>: older versions of that XEP didn't include a ringing indication, maybe Dino simply implements an earlier version of XEP-0353?
Yes, I already said that in the thread you quote:
On 10/14/26 6:59 AM, onf wrote:
I just checked and version 0.3.1 of the XEP that Dino claims to implement doesn't seem to contain any description of <ringing/>, which explains it. Its messages related to this XEP likewise don't include <store/> hints because that's not specified in that version either.
~ onf