Differences between revisions 3 and 120 (spanning 117 versions)
Revision 3 as of 2021-285 15:11:07
Size: 3053
Editor: Singpolyma
Comment:
Revision 120 as of 2023-318 03:57:10
Size: 861
Editor: 139
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format wiki Uncover Winter's Hidden Risks - Watch Now!
Line 3: Line 3:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. Protect Your Business Journey: Winter Travel Health Insights!
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)". As a business owner, your time is invaluable. Before embarking on your winter travel adventures, ensure a safe and healthy journey for you and your loved ones. Check out my latest YouTube video: "Dreadful Destinations: Winter Travel's 15 Most Dangerous Diseases!"
https://youtu.be/MaspujyL7j8
Line 7: Line 8:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: ❄️ Uncover the health risks that lurk in winter destinations and gain essential insights to safeguard your well-being. Whether it's a business trip or a family getaway, preparation is key.
Line 9: Line 10:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
📹 Watch the video now: https://youtu.be/MaspujyL7j8
Line 14: Line 12:
<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>
}}}
Subscribe for exclusive travel health tips to keep both your business and loved ones thriving.
Line 25: Line 14:
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. Watch at https://youtu.be/MaspujyL7j8
Line 27: Line 16:
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. Safe travels,
Line 29: Line 18:
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:

 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>

<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`

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.
TravelShieldGuide
----
CategoryHomepage

Uncover Winter's Hidden Risks - Watch Now!

Protect Your Business Journey: Winter Travel Health Insights!

As a business owner, your time is invaluable. Before embarking on your winter travel adventures, ensure a safe and healthy journey for you and your loved ones. Check out my latest YouTube video: "Dreadful Destinations: Winter Travel's 15 Most Dangerous Diseases!" https://youtu.be/MaspujyL7j8

❄️ Uncover the health risks that lurk in winter destinations and gain essential insights to safeguard your well-being. Whether it's a business trip or a family getaway, preparation is key.

📹 Watch the video now: https://youtu.be/MaspujyL7j8

Subscribe for exclusive travel health tips to keep both your business and loved ones thriving.

Watch at https://youtu.be/MaspujyL7j8

Safe travels,

TravelShieldGuide


CategoryHomepage

GatewayContactUX (last edited 2024-277 17:38:04 by gnafuthegreat)