168
edits
Difference between revisions of "XMPP IM Client Design Guidelines"
Jump to navigation
Jump to search
XMPP IM Client Design Guidelines (view source)
Revision as of 06:20, 2 October 2015
, 06:20, 2 October 2015→Do not to split up JIDs into multiple input fields, require only the user's JID and password
| Line 14: | Line 14: | ||
Splitting the JID into multiple input fields makes it impossible for the user to simply copy&paste his JID into the field. Asking the user for more then his bare JID and password increases the UI elements and reduces the usability. | Splitting the JID into multiple input fields makes it impossible for the user to simply copy&paste his JID into the field. Asking the user for more then his bare JID and password increases the UI elements and reduces the usability. | ||
== Provide an advanced option allowing the user to specify the host and port to connect to == | |||
=== Description === | |||
Users should be able to specify the host and port to which the client tries to establish the connection to. If this is specified the usual and recommend way to determine the host/port via DNS SRV resource records is not used. | |||
=== Rationale === | |||
Some servers don't have proper DNS SRV resource records configured. | |||
== Provide an advanced option allowing the user to specify the SASL authentication identity (authcid) == | |||
=== Description === | |||
Users should be able to specify thea uthentication identity the client uses when performing SASL authentication. If this is specified the usual and recommend way of using the locapart of the users JID is not used. | |||
=== Rationale === | |||
Nothing in the XMPP specification requires the SASL authentication identity to be the localpart of the users JID. While this is true for most XMPP services, there are services which need the SASL authentication identity to be something else. | |||
== Show user's room nickname and allow to change it == | == Show user's room nickname and allow to change it == | ||