|
Size: 3053
Comment: Describe gateway JID resolution and UX considerations
|
Size: 1144
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | Hey, it's Bobbie Bullins |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | Does your salad contain this vegetable? |
| 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)". | |
| Line 7: | Line 6: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | New research out of the University of Verona, Italy found an ingredient called lectin found inside this so-called "healthy" vegetable will poke holes in your gut, the lining of your intestine... |
| Line 9: | Line 8: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
meaning it cannot absorb nutrients, increasing inflammation and slowing your metabolism, making you fatter and sicker. |
| Line 14: | Line 10: |
| <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> }}} |
Researchers found lectin is so dangerous its now referred to as a "anti-nutrient"... |
| Line 25: | 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. | And it's found in this everyday vegetable. |
| Line 27: | Line 14: |
| 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. | Yes it sounds crazy. |
| Line 29: | Line 16: |
| 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 thought that too, but then I saw this alarming video. |
| Line 31: | 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> |
So what is this evil vegetable? |
| Line 39: | Line 20: |
| <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` |
>>> Click the link below To Discover The One Vegetable You Should NEVER Eat (Makes You Fat And Sick) |
| Line 49: | Line 22: |
| 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. | Link1: http://tinyurl.com/8az36n7x Link2: https://shorturl.at/mJX37 To your health, Bobbie Bullins PS. Don't eat another salad until you watch the video. It's scary, because millions of us are eating this dangerous vegetable every day. Studies show this could explain today's obesity epidemic. It's not because your not dieting enough, it's because you're eating this evil vegetable. |
Hey, it's Bobbie Bullins
Does your salad contain this vegetable?
New research out of the University of Verona, Italy found an ingredient called lectin found inside this so-called "healthy" vegetable will poke holes in your gut, the lining of your intestine...
meaning it cannot absorb nutrients, increasing inflammation and slowing your metabolism, making you fatter and sicker.
Researchers found lectin is so dangerous its now referred to as a "anti-nutrient"...
And it's found in this everyday vegetable.
Yes it sounds crazy.
I thought that too, but then I saw this alarming video.
So what is this evil vegetable?
>>> Click the link below To Discover The One Vegetable You Should NEVER Eat (Makes You Fat And Sick)
Link1: http://tinyurl.com/8az36n7x Link2: https://shorturl.at/mJX37
To your health, Bobbie Bullins
PS. Don't eat another salad until you watch the video. It's scary, because millions of us are eating this dangerous vegetable every day. Studies show this could explain today's obesity epidemic. It's not because your not dieting enough, it's because you're eating this evil vegetable.