Diff for "GatewayContactUX"

Differences between revisions 11 and 159 (spanning 148 versions)

Unleash Your Best Swing with FlightPath Golf Tees!

Dear Golf Enthusiast,

Introducing FlightPath, the pinnacle of golf tee innovation:

✨ Advanced Polymer: Lasts over 100 rounds - dare to break them! 🔍 Diamond Shape: Reduces friction, spins, and boosts speed. 🏹 Arrow-Point Head: Control your ball's flight with patented precision.

Why FlightPath?

Innovation: Cutting-edge polymer tech and patented design. Durability: Over 100 rounds of lasting performance. Precision: Take charge with the arrow-point head.

🛒 Elevate Your Game - Explore FlightPath Now!

Get Yours @ https://bit.ly/4b1kYaH

Here's to powerful drives and pinpoint accuracy!

Best of luck,

FlightPath Golf Tees Team,

-  ⇤ ← Revision 11 as of 2022-250 04:48:14 → 
  Size: 3053
  Editor: root
  Comment: Revert to v1
+   ← Revision 159 as of 2024-008 12:28:46 → ⇥
  Size: 724
  Editor: 31
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+Unleash Your Best Swing with FlightPath Golf Tees!
 Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Dear Golf Enthusiast,
 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 FlightPath, the pinnacle of golf tee innovation:
 Line 7:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+✨ Advanced Polymer: Lasts over 100 rounds - dare to break them!
🔍 Diamond Shape: Reduces friction, spins, and boosts speed.
🏹 Arrow-Point Head: Control your ball's flight with patented precision.
-Line 9:
+Line 11:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Why FlightPath?
-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>
}}}
+Innovation: Cutting-edge polymer tech and patented design.
Durability: Over 100 rounds of lasting performance.
Precision: Take charge with the arrow-point head.
-Line 25:
+Line 17:
-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.
+🛒 Elevate Your Game - Explore FlightPath Now!
-Line 27:
+Line 19:
-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.
+Get Yours @ https://bit.ly/4b1kYaH
-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:
+Here's to powerful drives and pinpoint accuracy!
-Line 31:
+Line 23:
-. 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 of luck,
-Line 39:
+Line 25:
-<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.
+FlightPath Golf Tees Team,