Differences between revisions 142 and 143
Revision 142 as of 2023-352 18:55:21
Size: 3061
Comment: Revert spam
Revision 143 as of 2023-354 18:44:28
Size: 961
Editor: 31
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. Transform Your Leadership Journey: 'Empower Her' Course Awaits!
Line 3: Line 3:
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)". Dear Empowered Woman,
Line 5: Line 5:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: In the world of business, your journey is a testament to resilience and determination.
 You've faced unique challenges—juggling responsibilities, battling self-doubt, and navigating gender inequality.
 It's time to rise above it all.
Line 7: Line 9:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Introducing 'Empower Her for Unstoppable Success'—a transformative Course designed for women like you.
 Elevate your leadership skills, make decisive choices, build a high-performing team, and leverage technology for growth.
Line 12: 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>
}}}
Craft a purpose-driven business, harmonize your professional and personal life,
and showcase your expertise with our exclusive Course—a badge of your transformation into a confident, empowered leader.
Line 23: 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. Ready to rewrite the narrative? https://www.digistore24.com/redir/520892/mrvytas23/
Line 25: Line 17:
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 your empowerment and success!
Line 27: Line 19:
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.
Best of Luck,
'Empower Her' team,

Transform Your Leadership Journey: 'Empower Her' Course Awaits!

Dear Empowered Woman,

In the world of business, your journey is a testament to resilience and determination. You've faced unique challenges—juggling responsibilities, battling self-doubt, and navigating gender inequality. It's time to rise above it all.

Introducing 'Empower Her for Unstoppable Success'—a transformative Course designed for women like you. Elevate your leadership skills, make decisive choices, build a high-performing team, and leverage technology for growth.

Craft a purpose-driven business, harmonize your professional and personal life, and showcase your expertise with our exclusive Course—a badge of your transformation into a confident, empowered leader.

Ready to rewrite the narrative? https://www.digistore24.com/redir/520892/mrvytas23/

Here's to your empowerment and success!

Best of Luck, 'Empower Her' team,


CategoryHomepage

GatewayContactUX (last edited 2024-130 12:13:55 by 196)