Diff for "GatewayContactUX"

Differences between revisions 81 and 407 (spanning 326 versions)

Real Businesses, Real Results

How Businesses Like Yours Thrive on Fiverr

Hi,

Ever wondered how companies like yours are growing without breaking the bank?

Meet Sarah, a small business owner who needed a social media strategy but didn’t have the budget for an agency. Thanks to Fiverr, she connected with a top-notch social media expert in under 24 hours—at a fraction of the cost.

Her results? 3x engagement in 3 months.

Whether you need marketing, design, or tech support, Fiverr has professionals ready to help you achieve your goals.

Ready to see what Fiverr can do for you?

Start Your Journey → https://go.fiverr.com/visit/?bta=935157&brand=fiverrmarketplace

Cheers, Fiverr Ambassador,

-  ⇤ ← Revision 81 as of 2023-255 02:20:34 → 
  Size: 3037
  Editor: Singpolyma
  Comment: revert spam
+   ← Revision 407 as of 2024-353 10:43:38 → ⇥
  Size: 726
  Editor: ip83
  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.
+Real Businesses, Real Results
 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)".
+How Businesses Like Yours Thrive on Fiverr
 Line 5:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+Hi,
 Line 7:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Ever wondered how companies like yours are growing without breaking the bank?
-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>
}}}
+Meet Sarah, a small business owner who needed a social media strategy but didn’t have the budget for an agency.
Thanks to Fiverr, she connected with a top-notch social media expert in under 24 hours—at a fraction of the cost.
-Line 23:
+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.
+Her results? 3x engagement in 3 months.
-Line 25:
+Line 14:
-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.
+Whether you need marketing, design, or tech support, Fiverr has professionals ready to help you achieve your goals.
-Line 27:
+Line 16:
-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:
+Ready to see what Fiverr can do for you?
-Line 29:
+Line 18:
-. 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>
+Start Your Journey → https://go.fiverr.com/visit/?bta=935157&brand=fiverrmarketplace
-Line 37:
+Line 20:
-<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.
+Cheers,
Fiverr Ambassador,