Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XEP-0045: Remove conflicting keyword in §7.2.2 #1342

Merged
merged 1 commit into from
May 8, 2024
+7 −1
Merged

XEP-0045: Remove conflicting keyword in §7.2.2 #1342

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion xep-0045.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,12 @@
</schemaloc>
<registry/>
&stpeter;
<revision>
<version>1.34.6</version>
<date>2024-05-01</date>
<initials>pep</initials>
<remark><p>Remove contradicting keyword on sending subject in §7.2.2.</p></remark>
</revision>
<revision>
<version>1.34.5</version>
<date>2022-12-01</date>
Expand Down Expand Up @@ -1543,7 +1549,7 @@
</presence>
]]></example>
<p>Note: The order of the presence stanzas sent to the new occupant is important. The service MUST first send the complete list of the existing occupants to the new occupant and only then send the new occupant's own presence to the new occupant. This helps the client know when it has received the complete "room roster". For tracking purposes, the room might also reflect the original 'id' value if provided in the presence stanza sent by the user.</p>
<p>After sending the presence broadcast (and only after doing so), the service MAY then send discussion history, the room subject, live messages, presence updates, and other in-room traffic.</p>
<p>After sending the presence broadcast (and only after doing so), the service can then send discussion history, the room subject, live messages, presence updates, and other in-room traffic.</p>
</section3>

<section3 topic='Non-Anonymous Rooms' anchor='enter-nonanon'>
Expand Down