Differences between revisions 52 and 371 (spanning 319 versions)
Revision 52 as of 2023-050 17:54:49
Size: 3053
Editor: root
Comment: Spam
Revision 371 as of 2024-299 10:48:06
Size: 880
Editor: ip48
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format wiki Hey you want to Boost Your LinkedIn Advertising
Line 3: Line 3:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. Dear ,
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)". With LinkedIn's vast network of over 1 billion members, success depends on reaching the right decision-makers.
TRADExperts provides high-quality data on global executives and employees, enabling your ads to connect with those ready to act.
Line 7: Line 8:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: Why TRADExperts?
Line 9: Line 10:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Access Quality Leads Instantly:
Reach 12.4 million companies and 380 million active, earning professionals worldwide.
Leverage LinkedIn’s Matched Audiences to target precisely.
Line 14: Line 14:
<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>
}}}
Tailored for Professionals Across Roles: From Marketing Managers to Business Owners and Analysts,
Our data supports a wide range of strategic goals.
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. Get Started Today!
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. Transform your LinkedIn advertising in just a few clicks.
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: For more information visit our website https://www.checkout-ds24.com/redir/552448/mrvytas23/
Line 31: Line 23:
 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,
----
CategoryCategory

Hey you want to Boost Your LinkedIn Advertising

Dear ,

With LinkedIn's vast network of over 1 billion members, success depends on reaching the right decision-makers. TRADExperts provides high-quality data on global executives and employees, enabling your ads to connect with those ready to act.

Why TRADExperts?

Access Quality Leads Instantly: Reach 12.4 million companies and 380 million active, earning professionals worldwide. Leverage LinkedIn’s Matched Audiences to target precisely.

Tailored for Professionals Across Roles: From Marketing Managers to Business Owners and Analysts, Our data supports a wide range of strategic goals.

Get Started Today!

Transform your LinkedIn advertising in just a few clicks.

For more information visit our website https://www.checkout-ds24.com/redir/552448/mrvytas23/

Best regards,


CategoryCategory

GatewayContactUX (last edited 2024-361 15:58:51 by ip83)