Diff for "GatewayContactUX"

Differences between revisions 21 and 221 (spanning 200 versions)

Elevate Your Video Content with InVideo AI!

Dear,

Are you ready to take your video content to the next level?

Look no further than InVideo AI!

Create captivating videos with ease, no matter the topic.

InVideo AI works tirelessly to craft scripts, design scenes, add voiceovers, and fine-tune your video according to your preferences.

With InVideo AI as your co-pilot, engaging your audience has never been simpler.

Elevate your content creation process today with InVideo AI.

Let's make your vision a reality!

Follow the link @ invideo.sjv.io/1r3qMR

Best regards,

InvideoAi team,

CategoryHomepage

-  ⇤ ← Revision 21 as of 2022-345 23:00:32 → 
  Size: 6255
  Editor: bras-base-ktnron060cw-grc-05-184-144-81-134
  Comment: revert spam
+   ← Revision 221 as of 2024-048 23:21:43 → ⇥
  Size: 640
  Editor: 31
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
----- /!\ '''Edit conflict - other version:''' ----
#format wiki
+Elevate Your Video Content with InVideo AI!
-Line 4:
+Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Dear,
-Line 6:
+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)".
+Are you ready to take your video content to the next level?
-Line 8:
+Line 7:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+ Look no further than InVideo AI!
-Line 10:
+Line 9:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Create captivating videos with ease, no matter the topic.
-Line 15:
+Line 11:
-<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>
}}}
+InVideo AI works tirelessly to craft scripts, design scenes, add voiceovers, and fine-tune your video according to your preferences.
-Line 26:
+Line 13:
-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.
+With InVideo AI as your co-pilot, engaging your audience has never been simpler.
-Line 28:
+Line 15:
-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.
+Elevate your content creation process today with InVideo AI.
-Line 30:
+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:
+Let's make your vision a reality!
-Line 32:
+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>
+Follow the link @ invideo.sjv.io/1r3qMR
-Line 40:
+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`
+Best regards,
-Line 50:
+Line 23:
-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.

---- /!\ '''Edit conflict - your version:''' ----
#format wiki

This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.

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)".

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.

---- /!\ '''End of edit conflict''' ----
+#InvideoAi team,
----
CategoryHomepage