moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-23 17:52:15 -05:00
Code Issues Releases Wiki Activity

Merge branch 'feature/xep-0379'

Browse Source
This commit is contained in:
Jonas Schäfer 2020-01-14 18:52:40 +01:00
commit eb6d697524
1 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
xep-0379.xml
View File

@ -28,6 +28,12 @@
<email>georg@op-co.de</email>
<jid>georg@yax.im</jid>
</author>
<revision>
<version>0.3.2</version>
<date>2020-01-14</date>
<initials>licaon-kter</initials>
<remark>Fix a bunch of typos.</remark>
</revision>
<revision>
<version>0.3.1</version>
<date>2018-11-03</date>
@ -71,10 +77,10 @@
register with some server. Now, Romeo only needs to create a mutual
presence subscription with her, without yet knowing her JID.</p>
<p>This specification allows Romeo to create an out-of-band link (URI) which,
when opened in Juilet's (or another user's) client, will:</p>
when opened in Juliet's (or another user's) client, will:</p>
<ul>
<li>Add Romeo to Juliet's roster (with a display name optionally specified by Romeo)</li>
<li>Add Juliet to Romeo's roster (without a pre-defined display name)</li>
<li>Add Juliet to Romeo's roster (without a predefined display name)</li>
<li>Establish a mutual presence subscription between Romeo and Juliet</li>
</ul>
<p>The perceivable effect is that with a single click, Romeo and Juliet
@ -93,7 +99,7 @@
<ol>
<li>Generation of invitation link</li>
<li>Out-of-band transmission and presentation of the link</li>
<li>Subcription request to the user by the link receiver (new contact)</li>
<li>Subscription request to the user by the link receiver (new contact)</li>
<li>Approval by the user and mutual subscription request</li>
<li>Approval by the new contact</li>
</ol>
@ -281,7 +287,7 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp;
as if no preauth token was contained.</p>
</section2>
<section2 topic='No Expectaion of Immediate Approval' anchor='rules_expectation'>
<section2 topic='No Expectation of Immediate Approval' anchor='rules_expectation'>
<p>When sending a pre-authenticated subscription request, the contact's
client MUST NOT expect an immediate successful approval. If the user's
issuing client is currently offline, or if the token has expired, a manual
@ -359,8 +365,8 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp;
<section2 topic='Opening the Landing Page in an App' anchor='rules_multiclient'>
<p>Some mobile device platforms allow an app to register itself as a
handler for cetain URIs. This allows an XMPP client to register for <strong>xmpp:</strong>
URIs, but also to redirect handling of cetain HTTP/HTTPS URIs. A mobile
handler for certain URIs. This allows an XMPP client to register for <strong>xmpp:</strong>
URIs, but also to redirect handling of certain HTTP/HTTPS URIs. A mobile
client SHOULD register for the associated landing page URIs and properly
handle the contained invitations. For example, the JuicyXMPP client should
register a handler for <strong>https://juicyxmpp.example/i/*</strong>, and present
@ -375,7 +381,7 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp;
SHOULD be indicated by the client UI to Romeo.</p>
<p>If a client allows customization of the validity time or the number of
uses for a given invitation token, it SHOULD provide clear language
to inidcate that.</p>
to indicate that.</p>
</section2>
<section2 topic='Tagging of Auto-Added Contacts' anchor='rules_group'>
<p>When a new contact is added automatically by the client, it SHOULD