|
Size: 6255
Comment: revert spam
|
Size: 1305
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ---- /!\ '''Edit conflict - other version:''' ---- #format wiki |
If you're looking to start... |
| Line 4: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | Scale or grow... |
| 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)". | A digital business in 2020 and beyond... |
| 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: | Master online marketer, Matt Bacak, just revealed how he built a 7-figure online business using nothing but "ethical email marketing" to drive sales & commissions... |
| Line 10: | Line 9: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Plus, how he did it WITHOUT creating a product, without fulfilling services and without running ads. Ever. |
| 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> }}} |
The best part? |
| 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. | He only works 30 MINUTES PER DAY... |
| 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. | ...AND he generates sales automatically! |
| 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: | Trust me, this is not like ANY email marketing course or method you've ever seen before... |
| Line 32: | Line 19: |
| 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> |
Matt is known for challenging the status quo and testing everything -- even if it means going against the grain... |
| 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` |
In fact, sometimes the best results are gotten when you do the OPPOSITE of what everybody else does... |
| 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. | The Secret Email System is a counterintuitive approach to creating and running an online business, specifically the freedom/lifestyle model, that allows you to build a profitable long term business that gives you the freedom, fun & adventure... |
| Line 52: | Line 25: |
| ---- /!\ '''Edit conflict - your version:''' ---- #format wiki |
Check it out and grab your copy before the price goes up again... |
| Line 55: | Line 27: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | (You'll SAVE $31.40 if you act quickly) |
| Line 57: | Line 29: |
| 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)". | Get instant access and secure your savings here: https://warriorplus.com/o2/a/ktrjgl/0 |
| Line 59: | Line 32: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | To your success, |
| Line 61: | Line 34: |
| {{{ <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''' ---- |
Hugo Karlsson ---- CategoryHomepage |
If you're looking to start...
Scale or grow...
A digital business in 2020 and beyond...
Master online marketer, Matt Bacak, just revealed how he built a 7-figure online business using nothing but "ethical email marketing" to drive sales & commissions...
Plus, how he did it WITHOUT creating a product, without fulfilling services and without running ads. Ever.
The best part?
He only works 30 MINUTES PER DAY...
...AND he generates sales automatically!
Trust me, this is not like ANY email marketing course or method you've ever seen before...
Matt is known for challenging the status quo and testing everything -- even if it means going against the grain...
In fact, sometimes the best results are gotten when you do the OPPOSITE of what everybody else does...
The Secret Email System is a counterintuitive approach to creating and running an online business, specifically the freedom/lifestyle model, that allows you to build a profitable long term business that gives you the freedom, fun & adventure...
Check it out and grab your copy before the price goes up again...
(You'll SAVE $31.40 if you act quickly)
Get instant access and secure your savings here: https://warriorplus.com/o2/a/ktrjgl/0
To your success,
Hugo Karlsson