|
Size: 3053
Comment: Describe gateway JID resolution and UX considerations
|
Size: 1142
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | The Survival Secrets Nobody Tells You |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | Hi Friend, |
| Line 5: | 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)". | Most people don’t realize how close we are to the next major catastrophe — until it’s too late. |
| Line 7: | Line 7: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | **The Situation:** Right now, you might feel uncertain for events like natural disasters, wars, and nuclear threats. |
| Line 9: | Line 10: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
**Problem:** When chaos hits, not knowing the right steps could put you and your loved ones at extreme risk. |
| Line 14: | Line 13: |
| <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> }}} |
**Imagine:** Imagine alarms blaring at midnight… and instead of panicking, you confidently protect your family to safety — because you *already* know exactly what to do. Or saving a life when every second counts. |
| Line 25: | Line 17: |
| 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. | **Need-Payoff:** That's why I’ve created a comprehensive guide — packed with real-world survival skills you won’t find anywhere else. |
| Line 27: | Line 20: |
| 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. | Normally, people pay small fortunes... but I made it accessible to those who are ready — because *everyone deserves a fighting chance.* |
| Line 29: | Line 22: |
| 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: | ⚡ I can’t promise it’ll stay available forever. If the wrong people find out, I may have to remove access permanently. |
| Line 31: | Line 24: |
| 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> |
👉 [Grab your copy here before it’s too late](https://bit.ly/4iM87vB) |
| Line 39: | Line 26: |
| <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. |
Stay safe, ---- CategoryHomepage |
The Survival Secrets Nobody Tells You
Hi Friend,
Most people don’t realize how close we are to the next major catastrophe — until it’s too late.
The Situation: Right now, you might feel uncertain for events like natural disasters, wars, and nuclear threats.
Problem: When chaos hits, not knowing the right steps could put you and your loved ones at extreme risk.
Imagine: Imagine alarms blaring at midnight… and instead of panicking, you confidently protect your family to safety — because you *already* know exactly what to do. Or saving a life when every second counts.
Need-Payoff: That's why I’ve created a comprehensive guide — packed with real-world survival skills you won’t find anywhere else.
Normally, people pay small fortunes... but I made it accessible to those who are ready — because *everyone deserves a fighting chance.*
⚡ I can’t promise it’ll stay available forever. If the wrong people find out, I may have to remove access permanently.
👉 [Grab your copy here before it’s too late](https://bit.ly/4iM87vB)
Stay safe,