|
Size: 3053
Comment: Describe gateway JID resolution and UX considerations
|
Size: 1082
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | Stranded in Desireville? How to Stop Scrolling and Start Doing |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | |
| Line 5: | Line 4: |
| In every place where the UI would ask for a Jabber ID (most notably contact add, but possibly also invite to chatroom, create chatroom from 1:1 conversation, start voice/video call to non-contact, search view where a Jabber ID can be used, etc) it should scan the user's roster for JIDs which have `disco#info > identity[category=gateway]` and show some way of choosing to enter an identifier for that gateway instead of a Jabber ID. The simplest example might be a drop-down with `disco#info > identity[type]` and optional disambiguating `disco#info > idenity[name]` such as "sms (Cheogram)". | The problem? We get caught up in the comfort of the planning stage. We convince ourselves that meticulous research is the key and that the perfect strategy will unlock the door to our dreams. |
| Line 7: | Line 6: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | But what if the secret isn’t in the perfect plan but in the imperfect action? |
| Line 9: | Line 8: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Take action today. Grab Desire to Action and turn your desires and those of your customers (and potential customers) into reality. |
| Line 14: | Line 10: |
| <iq type='result' from='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'> <desc> Please enter the Whatever of the person you would like to contact. </desc> <prompt>Whatever</prompt> </query> </iq> }}} |
Remember, the only way out is through. Are you ready to take that first step? |
| Line 25: | Line 12: |
| This text may then be used as part of the UX as makes sense to help the user feel comfortable. Getting a success here and not an error also means that `jabber:iq:gateway` can be used in the next step. | |
| Line 27: | Line 13: |
| NOTE: it is also acceptable (and in some UX may be preferred or even necessary) to pre-emptively ask all gateways for the prompt, instead of only once one is selected. | |
| Line 29: | Line 14: |
| If an identifier is (or might be, depending on UX) one for a particular gateway, use the following procedure to map it to a Jabber ID and then perform the in-context relevant action on that Jabber ID as though it had been entered directly: | https://bit.ly/motivationalcontent |
| Line 31: | Line 16: |
| 1. If a prompt was got for `jabber:iq:gateway` above then use that protocol to finish resolution: {{{ <iq type='set' to='gateway.tld' id='gate2'> <query xmlns='jabber:iq:gateway'> <prompt>(555) 123-4567</prompt> </query> </iq> |
Beverly |
| Line 39: | Line 18: |
| <iq type='result' from='gateway.tld' id='gate2'> <query xmlns='jabber:iq:gateway'> <jid>+15551234567@gateway.tld</jid> </query> </iq> }}} 2. If an error is received in response to `jabber:iq:gateway` protocol, print the error message to the user and allow them to try again. This allows the gateway to provide useful feedback about format errors to the user. 3. If an error was received in response to fetching the `jabber:iq:gateway` prompt, then the gateway does not support this protocol. Look for a `disco#info > feature[var="jid\20escaping"]` and if found construct a JID using XEP-0106 escaping on the user input concatenated with `@gateway.tld` 4. If `jabber:iq:gateway` and `jid\20escaping` are both unsupported, replace any `@` in the user input with `%` and concatenate `@gateway.tld` |
|
| Line 49: | Line 19: |
| NOTE: If the result of this procedure is a string that is not a valid Jabber ID, it should be rejected just as if a user manually keyed in an invalid Jabber ID. | 1750 Powder Springs Rd 190-133 This opportunity is designed to empower your business growth, but we understand the importance of choice. If you prefer not to receive further information about expanding your business reach efficiently, include unsubscribe in the subject line of your response. soprani.ca Take the next step towards amplifying your business success—explore our offer now and see the difference it makes for yourself. ---- CategoryCategory |
Stranded in Desireville? How to Stop Scrolling and Start Doing
The problem? We get caught up in the comfort of the planning stage. We convince ourselves that meticulous research is the key and that the perfect strategy will unlock the door to our dreams.
But what if the secret isn’t in the perfect plan but in the imperfect action?
Take action today. Grab Desire to Action and turn your desires and those of your customers (and potential customers) into reality.
Remember, the only way out is through. Are you ready to take that first step?
https://bit.ly/motivationalcontent
Beverly
1750 Powder Springs Rd 190-133 This opportunity is designed to empower your business growth, but we understand the importance of choice. If you prefer not to receive further information about expanding your business reach efficiently, include unsubscribe in the subject line of your response. soprani.ca
Take the next step towards amplifying your business success—explore our offer now and see the difference it makes for yourself.