Skip to content

New MUC: Fix typo in Bassanio #1531

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

Open
Fishbowler wants to merge 1 commit into
base: master
Choose a base branch
from
Open

New MUC: Fix typo in Bassanio #1531

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
10 changes: 5 additions & 5 deletions inbox/new-muc.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,10 @@
<p>A client joining via MUC1's presence-based joins will not see these addresses, but instead sees the nickname-based addressing.</p>
<p>MUC2 rooms MUST include the nickname within presence as a nickname element qualified by the urn:xmpp:muc:0 namespace within the usual &X;.</p>
<example><![CDATA[
<presence to='bastanio@shakespeare.example/wimsy-192837' from='court@venice.example/-deadbeefcafe'>
<presence to='bassanio@shakespeare.example/wimsy-192837' from='court@venice.example/-deadbeefcafe'>
<x xmlns='http://jabber.org/protocol/muc#user'>
<item affiliation='admin' role='moderator'/>
<nickname xmlns='urn:xmpp:muc:0'>Bastanio</nickname>
<nickname xmlns='urn:xmpp:muc:0'>Bassanio</nickname>
</x>
</presence>
]]></example>
Expand All @@ -71,10 +71,10 @@
<p>Joining a MUC1 room can be done with (relatively) simple presence. MUC2, as well, can be done this way, though this will not automatically create a bare JID occupancy session. To do so, the same joining presence stanza is used, but the &X; element includes a muc2 element qualified by the &NSMUC2; namespace, and the presence is sent to the bare JID. This will indicate to the room that MUC2 is expected, and will cause the occupancy session to be a MUC2 session.</p>
<p>While rooms can be configured as "anonymous", "semi-anonymous", and so on, users MAY express their preference as well via the &lt;visibility/> element. If a user requests anonymity, the room MUST either honour that request or reject the join. Note that if the user has an existing occupancy session joined non-anonymously, this conflict MUST also reject the join. Typically, rooms will accept a non-anonymous join to a room that defaults to anonymous, but they MAY reject that.</p>
<example><![CDATA[
<presence from='bastanio@shakespeare.example/wimsy-192837' to='court@venice.example'>
<presence from='bassanio@shakespeare.example/wimsy-192837' to='court@venice.example'>
<x xmlns='http://jabber.org/protocol/muc'>
<muc2 xmlns='urn:xmpp:muc:0'/>
<nickname>Bastanio</nickname>
<nickname>Bassanio</nickname>
<presence level='full'/>
<visibility type='anonymous'/>
</muc2>
Expand Down Expand Up @@ -113,4 +113,4 @@
</section3>
</section2>
</section1>
</xep>
</xep>
Loading