6255
Comment: revert spam
|
1616
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
---- /!\ '''Edit conflict - other version:''' ---- #format wiki |
Transform Yourself in Just 8 Weeks with BIGGER BOLDER STRONGER! |
Line 4: | Line 3: |
This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | Hello , |
Line 6: | 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)". | Are you ready to embark on a transformative journey and sculpt the body you've always dreamed of? Introducing BIGGER BOLDER STRONGER you in 2024, an 8-week bodybuilding program designed to turn you into a modern-day Gym God. |
Line 8: | Line 8: |
If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | 🏋️♂️ Program Highlights: |
Line 10: | Line 10: |
{{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
Build muscle, lose fat, and get stronger simultaneously. Suitable for all fitness levels: Beginner, Intermediate, Advanced. Comprehensive guidance on workouts, diet, and supplements. Guaranteed to stimulate new lean muscle growth. Get Yours: https://bit.ly/3TPVEht |
Line 15: | Line 16: |
<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> }}} |
🌟 Why Choose BIGGER BOLDER STRONGER? |
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. | Get Yours: https://bit.ly/3TPVEht |
Line 28: | Line 20: |
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. | This program is not just a workout routine; it's a lifestyle change. We provide you with two 4-week cycles, strategically designed to challenge your muscles and ensure continuous growth. With workouts 5 days a week, tailored to your experience level, you'll witness remarkable results in just 8 weeks. |
Line 30: | Line 24: |
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: | 📋 Program Details: |
Line 32: | Line 26: |
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> |
Length: 8 Weeks Workouts per Week: 5 Experience Level: Beginner, Intermediate, Advanced Ready to transform into an impressive, stage-ready Bodybuilding Muscle God? All you have to do is invest in the program, follow the guidelines, and put in the work. Your journey to becoming bigger, leaner, and stronger starts now! |
Line 40: | Line 33: |
<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` |
🚀 Get Yours Today: |
Line 50: | Line 35: |
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. | https://bit.ly/3TPVEht |
Line 52: | Line 37: |
---- /!\ '''Edit conflict - your version:''' ---- #format wiki |
Don't miss this opportunity to redefine your physique and boost your confidence. Let's start building those monster muscles together! |
Line 55: | Line 39: |
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: 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''' ---- |
Best regards, BIGGER BOLDER STRONGER team, ---- CategoryHomepage |
Transform Yourself in Just 8 Weeks with BIGGER BOLDER STRONGER!
Hello ,
Are you ready to embark on a transformative journey and sculpt the body you've always dreamed of? Introducing BIGGER BOLDER STRONGER you in 2024, an 8-week bodybuilding program designed to turn you into a modern-day Gym God.
🏋️♂️ Program Highlights:
Build muscle, lose fat, and get stronger simultaneously. Suitable for all fitness levels: Beginner, Intermediate, Advanced. Comprehensive guidance on workouts, diet, and supplements. Guaranteed to stimulate new lean muscle growth. Get Yours: https://bit.ly/3TPVEht
🌟 Why Choose BIGGER BOLDER STRONGER?
Get Yours: https://bit.ly/3TPVEht
This program is not just a workout routine; it's a lifestyle change. We provide you with two 4-week cycles, strategically designed to challenge your muscles and ensure continuous growth. With workouts 5 days a week, tailored to your experience level, you'll witness remarkable results in just 8 weeks.
📋 Program Details:
Length: 8 Weeks Workouts per Week: 5 Experience Level: Beginner, Intermediate, Advanced Ready to transform into an impressive, stage-ready Bodybuilding Muscle God? All you have to do is invest in the program, follow the guidelines, and put in the work. Your journey to becoming bigger, leaner, and stronger starts now!
🚀 Get Yours Today:
Don't miss this opportunity to redefine your physique and boost your confidence. Let's start building those monster muscles together!
Best regards, BIGGER BOLDER STRONGER team,