Differences between revisions 263 and 290 (spanning 27 versions)
Revision 263 as of 2024-084 17:55:40
Size: 3061
Comment: Revert spam
Revision 290 as of 2024-164 00:19:12
Size: 1324
Editor: 38
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. Dear Business Owner,
Are you struggling to boost your office productivity due to the high costs of new laptops, notebooks, and desktops? Do you need to equip your staff for remote work or expand your team to increase efficiency but find the budget constraints daunting?
Line 3: Line 4:
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)".
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: Visit https://beverlyfrazierllc.com today! Discover how our tailored solutions can meet your unique needs and requirements. By partnering with Beverly Frazier LLC, you can equip your staff with high-quality, affordable technology, enabling you to increase
 productivity and efficiency without breaking the bank. Don't miss out on this opportunity to transform your workspace – check out our offerings now!
Line 7: Line 8:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Line 12: Line 9:
<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>
}}}
https://beverlyfrazierllc.com
beverly@beverlyfrazierllc.com
Line 23: Line 12:
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.
Line 25: Line 13:
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.
Line 27: Line 14:
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: 1750 Powder Springs Rd
190-133
Marietta GA 30064
Line 29: Line 18:
 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.
"We're committed to providing you with the latest technology information designed to help you improve and grow your business. If you feel that our updates are no longer beneficial to you, you can reply to this email with 'Remove' in the subject line.
However, by unsubscribing, you will miss out on exclusive tips and strategies for potential productivity-boosting, time-saving devices." include unsubscribehttps://wiki.soprani.ca/GatewayContactUX in the subject line of your response.

Dear Business Owner, Are you struggling to boost your office productivity due to the high costs of new laptops, notebooks, and desktops? Do you need to equip your staff for remote work or expand your team to increase efficiency but find the budget constraints daunting?

Visit https://beverlyfrazierllc.com today! Discover how our tailored solutions can meet your unique needs and requirements. By partnering with Beverly Frazier LLC, you can equip your staff with high-quality, affordable technology, enabling you to increase productivity and efficiency without breaking the bank. Don't miss out on this opportunity to transform your workspace – check out our offerings now!

https://beverlyfrazierllc.com beverly@beverlyfrazierllc.com

1750 Powder Springs Rd 190-133 Marietta GA 30064

"We're committed to providing you with the latest technology information designed to help you improve and grow your business. If you feel that our updates are no longer beneficial to you, you can reply to this email with 'Remove' in the subject line. However, by unsubscribing, you will miss out on exclusive tips and strategies for potential productivity-boosting, time-saving devices." include unsubscribehttps://wiki.soprani.ca/GatewayContactUX in the subject line of your response.


CategoryHomepage

GatewayContactUX (last edited 2024-263 23:31:40 by ip51)