|
Size: 6255
Comment: revert spam
|
Size: 1347
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ---- /!\ '''Edit conflict - other version:''' ---- #format wiki |
... ... Hello... |
| Line 4: | Line 5: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | We hope you find this message quite useful ... |
| Line 6: | Line 7: |
| 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)". | This message is informative ... and aims to inform you about a very Beautiful and Luxurious Apartment for sale in Thessaloniki Greece. |
| Line 8: | Line 9: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | At the same time, this message comes to inform you about some new sites that we have created and that we will often add properties, which are for sale and which of course are located in Greece. |
| Line 10: | Line 11: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Most properties have direct contact with the owners and a few properties may be mediated by Greek brokers. |
| Line 15: | 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> }}} |
Do not forget talking about Greece, in fact we are talking about a country that has almost 10 months of the year summer and sun ... |
| Line 26: | 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. | If you want to keep the address of the site that serves you best and often watch for new listings of real estate ... surely you can take advantage of these properties by finding interested buyers and make enough money in every case of sale ... |
| Line 28: | 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. | |
| Line 30: | Line 18: |
| 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: | English: https://shorturl.at/imI46 German: https://shorturl.at/nDQY6 Russia: https://shorturl.at/kouw9 China: https://shorturl.at/koAZ6 Arabic: https://shorturl.at/rGV48 |
| Line 32: | 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> |
|
| Line 40: | Line 25: |
| <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` |
Yours sincerely Alice E-mail.: alicegreece775@gmail.com |
| Line 50: | Line 29: |
| 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. ---- /!\ '''Edit conflict - your version:''' ---- #format wiki This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. 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)". If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: {{{ <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''' ---- |
*** Contact details (phone and email) you can also find it when you click on the link above and going to the site, in the ad ... Thanks for understanding ... Greek - Greece ---- CategoryHomepage |
... ... Hello...
We hope you find this message quite useful ...
This message is informative ... and aims to inform you about a very Beautiful and Luxurious Apartment for sale in Thessaloniki Greece.
At the same time, this message comes to inform you about some new sites that we have created and that we will often add properties, which are for sale and which of course are located in Greece.
Most properties have direct contact with the owners and a few properties may be mediated by Greek brokers.
Do not forget talking about Greece, in fact we are talking about a country that has almost 10 months of the year summer and sun ...
If you want to keep the address of the site that serves you best and often watch for new listings of real estate ... surely you can take advantage of these properties by finding interested buyers and make enough money in every case of sale ...
English: https://shorturl.at/imI46 German: https://shorturl.at/nDQY6 Russia: https://shorturl.at/kouw9 China: https://shorturl.at/koAZ6 Arabic: https://shorturl.at/rGV48
Yours sincerely Alice E-mail.: alicegreece775@gmail.com
* Contact details (phone and email) you can also find it when you click on the link above and going to the site, in the ad ... Thanks for understanding ... Greek - Greece