Diff for "GatewayContactUX"

Differences between revisions 168 and 328 (spanning 160 versions)

Unlock the full potential of your business with Fiverr's Pro.

Our top-tier professionals don't just fix your broken website—they enhance your SEO

Boost your social media presence, and transform your site into a powerful tool that attracts more customers

And drives your business to NEW HEIGHTS.

Invest in the Expertise that makes a Huge difference.

Choose Fiverr Pro today and watch your business grow.

Simply visit us @ https://go.fiverr.com/visit/?bta=935157&brand=fp

Explore the difference and power of Fiverr Pro!!!

-  ⇤ ← Revision 168 as of 2024-014 23:41:02 → 
  Size: 3061
  Editor: gnafuthegreat
  Comment: Revert spam
+   ← Revision 328 as of 2024-183 10:15:00 → ⇥
  Size: 547
  Editor: ip7
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Unlock the full potential of your business with Fiverr's Pro.
 Line 3:
-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)".
+Our top-tier professionals don't just fix your broken website—they enhance your SEO
 Line 5:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+ Boost your social media presence, and transform your site into a powerful tool that attracts more customers
 Line 7:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+ And drives your business to NEW HEIGHTS.
-Line 12:
+Line 9:
-<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>
}}}
+ Invest in the Expertise that makes a Huge difference.
-Line 23:
+Line 11:
-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.
+Choose Fiverr Pro today and watch your business grow.
-Line 25:
+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.
+Simply visit us @ https://go.fiverr.com/visit/?bta=935157&brand=fp
-Line 27:
+Line 15:
-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.

----
CategoryHomepage
+Explore the difference and power of Fiverr Pro!!!