|
Size: 3053
Comment: Revert to v1
|
Size: 1338
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | Safeguard Your Office Valuables: A Hidden Safe Wall Clock That Works! |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | As someone who understands the importance of securing essential items in the workplace, I couldn’t wait to share this gem with you. Our Hidden Safe Large Wall Clock isn’t just another decor piece; it's an ingenious way to keep your office valuables safe and accessible. I've installed one in my own workspace, and it's been a game-changer. |
| Line 5: | 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)". | Here's why it's a must-have: Discreet Protection: This clock is more than meets the eye. Behind its classic design lies a hidden safe, perfect for storing sensitive documents, spare keys, or valuable items discreetly. Seamless Integration: It seamlessly blends into any office setting, adding a touch of sophistication while keeping your important items secure. Effortless Setup: Installation is a breeze—no complicated processes or tools required. |
| Line 7: | Line 12: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | Join me in experiencing the peace of mind that comes with knowing your valuables are safe, right within arm's reach. |
| Line 9: | Line 14: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Ready to enhance your office security effortlessly? Click Here>>>>> https://tinyurl.com/2y4zxmk7 |
| Line 14: | Line 17: |
| <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> }}} |
Invest in the safety of your office essentials with the Hidden Safe Large Wall Clock. Trust me, it’s a decision you won’t regret. Order Now >>> https://tinyurl.com/2y4zxmk7 |
| Line 25: | Line 21: |
| 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. |
Best regards, The MALYS Team ---- CategoryHomepage |
Safeguard Your Office Valuables: A Hidden Safe Wall Clock That Works!
As someone who understands the importance of securing essential items in the workplace, I couldn’t wait to share this gem with you. Our Hidden Safe Large Wall Clock isn’t just another decor piece; it's an ingenious way to keep your office valuables safe and accessible. I've installed one in my own workspace, and it's been a game-changer.
Here's why it's a must-have: Discreet Protection: This clock is more than meets the eye. Behind its classic design lies a hidden safe, perfect for storing sensitive documents, spare keys, or valuable items discreetly. Seamless Integration: It seamlessly blends into any office setting, adding a touch of sophistication while keeping your important items secure. Effortless Setup: Installation is a breeze—no complicated processes or tools required.
Join me in experiencing the peace of mind that comes with knowing your valuables are safe, right within arm's reach.
Ready to enhance your office security effortlessly? Click Here>>>>> https://tinyurl.com/2y4zxmk7
Invest in the safety of your office essentials with the Hidden Safe Large Wall Clock. Trust me, it’s a decision you won’t regret. Order Now >>> https://tinyurl.com/2y4zxmk7
Best regards, The MALYS Team