Differences between revisions 132 and 479 (spanning 347 versions)
Revision 132 as of 2023-334 15:48:09
Size: 3061
Editor: 31
Comment: Revert spam
Revision 479 as of 2025-112 00:59:46
Size: 1121
Editor: vmi2354374
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. Tired of overpriced lead services? At **FastCheapLeads**, we deliver **REAL business leads** starting at just **$0.01 per lead** — no gimmicks.
Line 3: Line 3:
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)". Go to https://bit.ly/fastcheapleads
Line 5: Line 5:
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: ✅ Company Name
✅ Contact Person
✅ Phone Number
✅ Filtered by Any USA City
✅ Custom Orders Available
Line 7: Line 11:
{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
Perfect for:
Line 12: Line 13:
<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>
}}}
- Cold Calling
- Email Marketing
- Local Sales Teams
- Agencies & Freelancers
Line 23: 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. 📦 Fast Delivery – Usually Within 24–72 Hours
💬 Custom Requests Welcome
👉 Visit: **FastCheapLeads.com**
📩 Or message us here for your first list today!
Line 25: Line 23:
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. Let us know if you need leads based on your industry of preference — whether it's real estate, catering, insurance, legal services, event planning, fitness, salons, med spas, construction, digital marketing, auto sales, financial services, credit repair, moving companies, HVAC, home cleaning, pest control, photography, coaching, tutoring, tech support, e-commerce, or any other field — we’ve got you covered. We can get it all! We can also filter by any city in the USA!
Line 27: Line 25:
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.
Go to https://bit.ly/fastcheapleads
Line 50: Line 27:
CategoryHomepage CategoryCategory

Tired of overpriced lead services? At FastCheapLeads, we deliver REAL business leads starting at just $0.01 per lead — no gimmicks.

Go to https://bit.ly/fastcheapleads

✅ Company Name ✅ Contact Person ✅ Phone Number ✅ Filtered by Any USA City ✅ Custom Orders Available

Perfect for:

- Cold Calling - Email Marketing - Local Sales Teams - Agencies & Freelancers

📦 Fast Delivery – Usually Within 24–72 Hours 💬 Custom Requests Welcome 👉 Visit: FastCheapLeads.com 📩 Or message us here for your first list today!

Let us know if you need leads based on your industry of preference — whether it's real estate, catering, insurance, legal services, event planning, fitness, salons, med spas, construction, digital marketing, auto sales, financial services, credit repair, moving companies, HVAC, home cleaning, pest control, photography, coaching, tutoring, tech support, e-commerce, or any other field — we’ve got you covered. We can get it all! We can also filter by any city in the USA!

Go to https://bit.ly/fastcheapleads


CategoryCategory

GatewayContactUX (last edited 2025-112 15:31:32 by vmi2354374)