|
Size: 3053
Comment: Describe gateway JID resolution and UX considerations
|
← Revision 539 as of 2026-149 19:09:55 ⇥
Size: 1009
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | Hi there, |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | The static website era is ending |
| Line 5: | Line 5: |
| 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)". | Most businesses still think their website is a digital brochure. |
| Line 7: | Line 7: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | Visitors do not behave that way anymore. |
| Line 9: | Line 9: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Customers increasingly expect websites to behave like conversations. They show up with intent, specific questions, and very little patience. And when they don't get answers instantly, they leave. |
| Line 14: | Line 13: |
| <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> }}} |
No follow-up. No second attempt. No loyalty. |
| Line 25: | Line 15: |
| 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. | Just revenue that could have been captured but was not. |
| Line 27: | Line 17: |
| 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. | The uncomfortable reality is this: |
| Line 29: | Line 19: |
| 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: | Very soon, websites that cannot talk back will feel old in the same way non-mobile websites felt old. |
| Line 31: | Line 21: |
| 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> |
That shift is already underway. |
| Line 39: | Line 23: |
| <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` |
Modern websites respond. Static ones lose attention. |
| Line 49: | Line 25: |
| 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. | See it in action: https://theollehai.com Regards, Trevor Kobayashi OllehAI If at any point you prefer not to get any more communications from me, kindly fill the form at brnd .li/delist url with your domain address (URL). Vestapad 82, Croton-on-Hudson, CA, USA, 92693 ---- CategoryCategory |
Hi there,
The static website era is ending
Most businesses still think their website is a digital brochure.
Visitors do not behave that way anymore.
Customers increasingly expect websites to behave like conversations. They show up with intent, specific questions, and very little patience. And when they don't get answers instantly, they leave.
No follow-up. No second attempt. No loyalty.
Just revenue that could have been captured but was not.
The uncomfortable reality is this:
Very soon, websites that cannot talk back will feel old in the same way non-mobile websites felt old.
That shift is already underway.
Modern websites respond. Static ones lose attention.
See it in action: https://theollehai.com
Regards, Trevor Kobayashi OllehAI
If at any point you prefer not to get any more communications from me, kindly fill the form at brnd .li/delist url with your domain address (URL). Vestapad 82, Croton-on-Hudson, CA, USA, 92693