Diff for "GatewayContactUX"

Differences between revisions 11 and 434 (spanning 423 versions)

Take the Leap: Ready to Elevate Your Business in 2025?

Are You Ready to Elevate? Let’s Do This!

Hi,

The year 2025 holds incredible potential for businesses ready to take the leap. By now, you’ve learned key strategies and insights that can propel your business forward, but the most important step is taking action.

Are you ready to elevate your business? If so, we’re here to support you every step of the way.

We’ve got all the tools, resources, and strategies you need to succeed. All you need to do is make the first move.

Visit us now to take the leap and start your transformation: https://bit.ly/402zBpp

Let’s make 2025 your year of breakthrough success.

Best wishes, Jordan Miller Elevate Business Solutions

-  ⇤ ← Revision 11 as of 2022-250 04:48:14 → 
  Size: 3053
  Editor: root
  Comment: Revert to v1
+   ← Revision 434 as of 2025-007 20:31:00 → ⇥
  Size: 757
  Editor: ip15
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+Take the Leap: Ready to Elevate Your Business in 2025?
 Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Are You Ready to Elevate? Let’s Do This!
 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)".
+Hi,
 Line 7:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+The year 2025 holds incredible potential for businesses ready to take the leap.
By now, you’ve learned key strategies and insights that can propel your business forward, but the most important step is taking action.
-Line 9:
+Line 10:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Are you ready to elevate your business? If so, we’re here to support you every step of the way.
-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>
}}}
+We’ve got all the tools, resources, and strategies you need to succeed.
All you need to do is make the first move.
-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.
+Visit us now to take the leap and start your transformation: https://bit.ly/402zBpp
-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.
-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:
+Let’s make 2025 your year of breakthrough success.
-Line 31:
+Line 20:
-. 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.
+Best wishes,
Jordan Miller
Elevate Business Solutions