[Standards] Presences of Contacts in Search Result

Cramer, E.R. (Eelco) Eelco.Cramer at tno.nl
Mon Oct 19 10:45:36 UTC 2015

For internal contact only you might want to check out:

http://www.xmpp.org/extensions/xep-0144.html#entities-groupservice <http://www.xmpp.org/extensions/xep-0144.html#entities-groupservice>

If you server administrator allows it and you server supports it.

“A group service enables an administrator to centrally define and administer roster groups so that they can be shared among a user population in an organized fashion.”

"If the user has registered with a group service or been otherwise provisioned to use a group service, the receiving application SHOULD process roster item suggestions received from the service. Such processing MAY occur automatically (i.e., without the user's approval of each roster item or batch of roster items) if and only if the receiving application has explicitly informed the user that it will automatically process roster items from the service. Furthermore, the receiving application SHOULD periodically verify automatic processing with the user (e.g., once per session in which the service sends roster item suggestions to the user).”

Hope this helps.

> On 19 Oct 2015, at 12:28, Dave Cridland <dave at cridland.net> wrote:
> On 19 October 2015 at 00:25, Phuong Vo <phngt2 at gmail.com <mailto:phngt2 at gmail.com>> wrote:
> According to your reply, if I want to see presences of all contacts in search result, I have to add them to roster. That is just fine for single endpoint; however, jabber supports multiple endpoints (the same users can login on multiple devices) if I do this on one endpoint, all other endpoints will see searched contacts in the contact list which is weird behavior. I am not sure XMPP has a workaround for this issue. Thanks for your response Dave.
> You're misunderstanding.
> You can only see presence for those people who have given you permission to do so.
> This is intentional, and a workaround would be a security issue.
> Dave.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20151019/b6ee3425/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.jabber.org/pipermail/standards/attachments/20151019/b6ee3425/attachment.sig>
-------------- next part --------------
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

More information about the Standards mailing list