This is meant for MUC presence. Servers don't necessarily track muc joins or other directed presences.
The hint in the xep is meant for clients that might support this (sending directed presence after receiving a pep node update) but servers that don't. So there might be code in the client sending this but it should be wrapped by a check if the server will support it. If that makes sense... On Sat, Sep 1, 2018, 13:36 Philipp Hörist <[email protected]> wrote: > Hi, > > "Services will inject the hash in directed presences automatically but > will not resend the presence if the avatar gets updated. Thus clients MAY > resend directed available presence to all Multi-User Chats after receiving > a 'urn:xmpp:avatar:metadata' update notification. The service will then > inject an updated version of the hash. To avoid sending unnecassary > presence updates, resending should only occur if the service annouces the > 'urn:xmpp:pep-vcard-conversion:0' feature." > > 1. Can we not let the server resend presence after a vcard/0084 update? > > 2. "To avoid sending unnecassary presence updates, resending should only > occur if the service annouces the 'urn:xmpp:pep-vcard-conversion:0' > feature." > > It basically says: Dont do the things that are mentioned in this XEP if > the server doesnt support this XEP. In this case resending presence after a > metadata node update. I think this is implied by any XEP, that if your > counterpart does not have support, things mentioned in this XEP do not apply > > regards > Philipp > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
