Differences between revisions 21 and 53 (spanning 32 versions)
Revision 21 as of 2022-345 23:00:32
Size: 6255
Editor: bras-base-ktnron060cw-grc-05-184-144-81-134
Comment: revert spam
Revision 53 as of 2023-051 04:37:58
Size: 1533
Editor: 63
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
---- /!\ '''Edit conflict - other version:''' ----
#format wiki
Hey,
What’s the most powerful marketing medium on the internet?
If you didn’t say video…you’re just plain wrong.
Sorry to be so blunt, but…
Line 4: Line 6:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. 70% of marketers are already using YouTube to promote their
products and services.
Line 6: Line 9:
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)". But you can have an unfair advantage over all these marketers…
Click Here To Learn More
→http://bit.ly/3lPZ3hu
Line 8: Line 13:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
Line 10: Line 14:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
A few years ago, Ranking videos on the first page of google
and YouTube was easy as 1-2-3…
Line 15: 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>
}}}
Line 26: Line 18:
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. Nowadays, with fierce competition and every marketer and their mom uploading thousands of videos each day it’s hard to get your video on the first
page of Google or YouTube…
Line 28: Line 21:
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 22:
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: What if I would told you there is a much easier way…
What if I told you that that I found a backdoor strategy
to get instant top video rankings and get
AS MUCH TARGETED FREE TRAFFIC as you want:
Line 32: Line 27:
 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 28:
<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`
x And you​ ​won’t​ ​have​ ​to​ ​learn​ ​a​ ​thing​ ​about​ ​SEO.
Line 50: Line 30:
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.
Line 52: Line 31:
---- /!\ '''Edit conflict - your version:''' ----
#format wiki
x You​ ​don’t​ ​have​ ​to​ ​know​ ​a​ ​damn​ ​thing​ ​about​ ​backlinks…
Line 55: Line 33:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
Line 57: Line 34:
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)". x And​ ​you​ ​don’t​ ​need​ ​a​ ​huge​ ​budget​ ​to​ ​take​ ​advantage​ ​of​ ​this
Line 59: Line 36:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
Line 61: Line 37:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Find out how you can profit from this too and get tons of targeted traffic, starting right now
→ http://bit.ly/3lPZ3hu
Have a great day,
Line 66: Line 41:
<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 77: Line 42:
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''' ----
PS: It’s a simple copy, paste and profit formula only a handful
people are taking advantage of it.
Go see it in action:
>> http://bit.ly/3lPZ3hu
----
CategoryHomepage

Hey, What’s the most powerful marketing medium on the internet? If you didn’t say video…you’re just plain wrong. Sorry to be so blunt, but…

70% of marketers are already using YouTube to promote their products and services.

But you can have an unfair advantage over all these marketers… Click Here To Learn More →http://bit.ly/3lPZ3hu

A few years ago, Ranking videos on the first page of google and YouTube was easy as 1-2-3…

Nowadays, with fierce competition and every marketer and their mom uploading thousands of videos each day it’s hard to get your video on the first page of Google or YouTube

What if I would told you there is a much easier way… What if I told you that that I found a backdoor strategy to get instant top video rankings and get AS MUCH TARGETED FREE TRAFFIC as you want:

x And you​ ​won’t​ ​have​ ​to​ ​learn​ ​a​ ​thing​ ​about​ ​SEO.

x You​ ​don’t​ ​have​ ​to​ ​know​ ​a​ ​damn​ ​thing​ ​about​ ​backlinks…

x And​ ​you​ ​don’t​ ​need​ ​a​ ​huge​ ​budget​ ​to​ ​take​ ​advantage​ ​of​ ​this

Find out how you can profit from this too and get tons of targeted traffic, starting right now → http://bit.ly/3lPZ3hu Have a great day,

PS: It’s a simple copy, paste and profit formula only a handful people are taking advantage of it. Go see it in action: >> http://bit.ly/3lPZ3hu


CategoryHomepage

GatewayContactUX (last edited 2024-322 17:13:29 by ip157)