XMPP IM Client Design Guidelines
Revision as of 09:24, 13 May 2015 by Flow (talk | contribs) (→Do not to encode any semantic into the resource)
Introduction
Advices
Do not to split up JIDs into multiple input fields
Description
Rationale
Show user's room nickname and allow to change it
Description
Rationale
Use only TLS secured XMPP c2s connections
Description
Rationale
Do not to encode any semantic into the resource and don't specify a resource
Description
Instead of letting the user specify a resource or providing a pre-configured list of possible resource names (e.g. '/home', '/work', '/notebook') let the server generate a resource for your client. You may optionally provide a possibility to configure the resource to the user under a "advanced settings" menu (or similar). But a XMPP user should not need to configure or specify a resource.
Rationale
Resource names should not be guessable to prevent presence leaks.