Differences between revisions 9 and 130 (spanning 121 versions)
Revision 9 as of 2022-198 00:14:11
Size: 3053
Editor: root
Comment: Revert to Revision 1
Revision 130 as of 2023-330 04:59:55
Size: 1197
Editor: ip85
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format wiki Elevate Your Business with Free Ebook -Easy Online Income Streams!
Line 3: Line 3:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. Ready to propel your business to greater online success? I've got something special tailored just for entrepreneurs like you.
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)". Introducing our Free Ebook:Easy Online Income Streams. This comprehensive guide is your key to unlocking the secrets of maximizing your online income potential.
Sign up now to gain exclusive access to this invaluable resource.
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: But that's not all. As a subscriber, you'll also receive access to three powerful online business solutions crafted to help you effortlessly generate extra income:
Line 9: Line 10:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Solution 1: Diversify Your Revenue Streams
Solution 2: Automated Profit Platforms
Solution 3: Tailored Strategies for Success
Line 14: Line 14:
<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>
}}}
Embark on this transformative journey by joining us at GetMillionsOnline. Click here >>> https://tinyurl.com/yec3m78b to grab your Free Ebook: Easy Online Income Streams and uncover the endless possibilities that await.
Line 25: Line 16:
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. Thank you for considering GetMillionsOnline as your partner in success. We're excited to help you thrive in the online business world.
Line 27: Line 18:
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. Warm regards,
Casie Monica
Line 29: Line 21:
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.
GetMillionsOnline - Your Gateway to Online Success!
----
CategoryHomepage

Elevate Your Business with Free Ebook -Easy Online Income Streams!

Ready to propel your business to greater online success? I've got something special tailored just for entrepreneurs like you.

Introducing our Free Ebook:Easy Online Income Streams. This comprehensive guide is your key to unlocking the secrets of maximizing your online income potential. Sign up now to gain exclusive access to this invaluable resource.

But that's not all. As a subscriber, you'll also receive access to three powerful online business solutions crafted to help you effortlessly generate extra income:

Solution 1: Diversify Your Revenue Streams Solution 2: Automated Profit Platforms Solution 3: Tailored Strategies for Success

Embark on this transformative journey by joining us at GetMillionsOnline. Click here >>> https://tinyurl.com/yec3m78b to grab your Free Ebook: Easy Online Income Streams and uncover the endless possibilities that await.

Thank you for considering GetMillionsOnline as your partner in success. We're excited to help you thrive in the online business world.

Warm regards, Casie Monica

GetMillionsOnline - Your Gateway to Online Success!


CategoryHomepage

GatewayContactUX (last edited 2024-282 02:22:50 by ip104)