|
Size: 1640
Comment:
|
Size: 3053
Comment: Spam
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Being a digital marketer today is definitely not easy! Not only do you need high-quality content, you need a lot of it. | #format wiki |
| Line 3: | Line 3: |
| But creating good content is incredibly time consuming. At least that is what I thought until I came across WordAi… | This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. |
| Line 5: | Line 5: |
| In case you have never heard of WordAi, it is a lightning fast content rewriter that uses Artificial Intelligence to automatically create unique variations of any piece of content. The best part is, WordAi creates rewrites that both humans and Google love. | 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 7: |
| I know, that’s a bold claim and I was pretty skeptical myself. So I decided to test their claims with their free trial and can tell you honestly, I opted directly for the yearly subscription after that. | If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: |
| Line 9: | Line 9: |
| I’m not exaggerating when I tell you that WordAi is better than any other tool, service, or method on the market. | {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
| Line 11: | Line 14: |
| I have been using WordAi to fill out my blogs and have already covered the cost of my yearly subscription. It’s crazy but I’m just scratching the surface of how far I can scale my SEO with WordAi! | <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> }}} |
| Line 13: | Line 25: |
| While I am using WordAi to scale my SEO efforts, you can also use WordAi to diversify your copy or even brainstorm to beat writer's block! | 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. |
| Line 15: | Line 27: |
| I could tell you about WordAi all day, but you really just need to try it for yourself. They are so confident in their technology that they offer a completely free 3-day trial AND a 30-day money back guarantee. | 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 17: | Line 29: |
| So what are you waiting for? Click here to get started with WordAi for Free! -> https://tinyurl.com/WordAi1 | 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: |
| Line 19: | Line 31: |
| And make sure to thank me later when this tool has changed the way you create content :) | 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 21: | Line 39: |
| From Alphonse Fuqua ---- CategoryCategory |
<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. |
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:
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>
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.
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
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.