Diff for "GatewayContactUX"

Differences between revisions 22 and 48 (spanning 26 versions)

It is said by yahoo finance that by 2030 90 percent of content on the web will be created by Ai, the other 10 percent will agmented content with Ai there is a new Ai tool called Jasper that helps create content for you with a click of a button for your blog or business

Click the Link here to start your free trial -> https://tinyurl.com/Jasper-Free-Trial-Ai-Writer

From Bernardo Palos

If you dont want to hear about jasper anymore from me fill out this form correctly: https://tinyurl.com/Jasper-Contact-Removal

CategoryCategory

-  ⇤ ← Revision 22 as of 2022-345 23:01:05 → 
  Size: 3053
  Editor: bras-base-ktnron060cw-grc-05-184-144-81-134
  Comment: fix
+   ← Revision 48 as of 2023-022 22:22:39 → ⇥
  Size: 549
  Editor: stonen
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+It is said by yahoo finance that by 2030 90 percent of content on the web will be created by Ai, the other 10 percent will agmented content with Ai
there is a new Ai tool called Jasper that helps create content for you with a click of a button for your blog or business
-Line 3:
+Line 4:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Click the Link here to start your free trial -> https://tinyurl.com/Jasper-Free-Trial-Ai-Writer
-Line 5:
+Line 6:
-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)".
+From
Bernardo Palos
-Line 7:
+Line 9:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:

{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>

<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>
}}}

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.

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.

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.
+If you dont want to hear about jasper anymore from me fill out this form correctly: https://tinyurl.com/Jasper-Contact-Removal
----
CategoryCategory