Diff for "GatewayContactUX"

Differences between revisions 11 and 163 (spanning 152 versions)

✨ Transform Your Craft with 16,000 Exclusive Woodworking Plans! 🛠️

Dear Friend,

Discover the extraordinary - 16,000 exclusive woodworking projects, meticulously crafted by passionate students and me over 25 years. Each comes with "done-for-you" plans, including step-by-step instructions and detailed blueprints.

Unlock your woodworking potential effortlessly, with stunning, professional results. Whether you're a seasoned craftsman or just starting, these plans make creating your dream projects quick and hassle-free.

Ready to embark on this exciting woodworking adventure?

Explore the plans now: 🔗 https://bit.ly/3TGIovE

Here's to turning your visions into reality!

Best of luck,

Woodworking Plans team,

CategoryCategory

-  ⇤ ← Revision 11 as of 2022-250 04:48:14 → 
  Size: 3053
  Editor: root
  Comment: Revert to v1
+   ← Revision 163 as of 2024-011 18:21:04 → ⇥
  Size: 773
  Editor: 139
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+✨ Transform Your Craft with 16,000 Exclusive Woodworking Plans! 🛠️
 Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Dear Friend,
 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)".
+Discover the extraordinary - 16,000 exclusive woodworking projects, meticulously crafted by passionate students and me over 25 years.
 Each comes with "done-for-you" plans, including step-by-step instructions and detailed blueprints.
-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:
 Line 9:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Unlock your woodworking potential effortlessly, with stunning, professional results.
 Whether you're a seasoned craftsman or just starting, these plans make creating your dream projects quick and hassle-free.
-Line 14:
+Line 12:
-<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>
}}}
+Ready to embark on this exciting woodworking adventure?
-Line 25:
+Line 14:
-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.
+Explore the plans now: 🔗 https://bit.ly/3TGIovE
-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.
+Here's to turning your visions into reality!
-Line 29:
+Line 18:
-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:
+Best of luck,
-Line 31:
+Line 20:
-. 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.
+Woodworking Plans team,
----
CategoryCategory