Differences between revisions 11 and 55 (spanning 44 versions)
Revision 11 as of 2022-250 04:48:14
Size: 3053
Editor: root
Comment: Revert to v1
Revision 55 as of 2023-063 19:28:33
Size: 985
Editor: 104
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format wiki Hi there,
Line 3: Line 3:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. We're writing to ask if you accept Guest Posts on wiki.soprani.ca?
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)". If you do, we can bring more people to your site, who wish to order Guest Posts / Backlinks from you.
Line 7: Line 7:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: This is how it works:
Line 9: Line 9:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
1. We add your site to our free download list, which is marketed to over 47 million potential customers.
2. People download the list for free, browse through the categories and metrics before contacting you.
3. You tell them your price and terms and agree the deal with them.
4. They send you the money.
5. It benefits you greatly because it means more orders.
Line 14: Line 15:
<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>
}}}
As we're doing the promotion, people come to you. You just carry on the conversation and seal the deal.
Line 25: Line 17:
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. A lot of people/agencies take a commission, but our model is different.
Line 27: Line 19:
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 you do accept guest posts and you're open to more business, you get back to me or you can find more information here and contact us through the site: http://bit.ly/3SNm2pA
Line 29: Line 21:
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.
Kind Regards,
Sam
----
CategoryCategory

Hi there,

We're writing to ask if you accept Guest Posts on wiki.soprani.ca?

If you do, we can bring more people to your site, who wish to order Guest Posts / Backlinks from you.

This is how it works:

1. We add your site to our free download list, which is marketed to over 47 million potential customers. 2. People download the list for free, browse through the categories and metrics before contacting you. 3. You tell them your price and terms and agree the deal with them. 4. They send you the money. 5. It benefits you greatly because it means more orders.

As we're doing the promotion, people come to you. You just carry on the conversation and seal the deal.

A lot of people/agencies take a commission, but our model is different.

If you do accept guest posts and you're open to more business, you get back to me or you can find more information here and contact us through the site: http://bit.ly/3SNm2pA

Kind Regards, Sam


CategoryCategory

GatewayContactUX (last edited 2024-266 21:54:24 by ip231)