Diff for "GatewayContactUX"

Differences between revisions 20 and 157 (spanning 137 versions)

Transform Your Body: Watch the Video Now!

Hi Love,

Exciting news! Our latest video reveals a proven method to say goodbye to cellulite and hello to a tighter, smoother you. 🚀Discover the science-backed secrets to reversing muscle-fiber atrophy and shrinkage, making your skin firmer and stronger.

This gentle method targets connective tissue, fascia, ligaments, tendons, and muscles for a lifted and shapely look. 💪

Plus, if excess body fat is a concern, our highlighted moves will help you burn it off, revealing a healthier and more vibrant you. Your unique results may vary based on your body type—Ectomorph, Mesomorph, or Endomorph.

Don't miss the surprising ending! Watch the video now: @ https://bit.ly/48GeqvP

Cheers to unlocking your best self! 🌟

Best Wishes,

Cellulite Removal team,

CategoryHomepage

-  ⇤ ← Revision 20 as of 2022-345 22:59:26 → 
  Size: 3053
  Editor: bras-base-ktnron060cw-grc-05-184-144-81-134
  Comment: revert spam
+   ← Revision 157 as of 2024-006 11:21:24 → ⇥
  Size: 861
  Editor: 139
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+Transform Your Body: Watch the Video Now!
 Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Hi Love,
 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)".
+Exciting news! Our latest video reveals a proven method to say goodbye to cellulite and hello to a tighter, smoother you.
 🚀Discover the science-backed secrets to reversing muscle-fiber atrophy and shrinkage, making your skin firmer and stronger.
-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:
+This gentle method targets connective tissue, fascia, ligaments, tendons, and muscles for a lifted and shapely look. 💪
-Line 9:
+Line 10:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Plus, if excess body fat is a concern, our highlighted moves will help you burn it off, revealing a healthier and more vibrant you.
 Your unique results may vary based on your body type—Ectomorph, Mesomorph, or Endomorph.
-Line 14:
+Line 13:
-<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>
}}}
+Don't miss the surprising ending! Watch the video now: @  https://bit.ly/48GeqvP
-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.
-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.
-Line 29:
+Line 17:
-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:
+Cheers to unlocking your best self! 🌟
-Line 31:
+Line 19:
-. 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>
+Best Wishes,
-Line 39:
+Line 21:
-<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.
+Cellulite Removal team,
----
CategoryHomepage