1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Commit Graph

129 Commits

Author SHA1 Message Date
Licaon_Kter
aff15f996e
Move none to note 2021-06-24 15:11:05 +00:00
Licaon_Kter
20ce66154a
XEP-0045 - Fix typo missed in rev. 1.25
Ping @stpeter
2021-05-15 21:27:34 +00:00
Matthew Wild
373b9de7b6 Multiple XEPs: Cross-document editorial adjustments for inclusive language.
Further reading and some rationale for these changes can be found at:
https://tools.ietf.org/html/draft-knodel-terminology-04

All changes are intended to be editorial in nature, not break existing
wire protocols, and not alter the meanings of any text.
2021-03-04 17:59:37 +01:00
Jonas Schäfer
e2031ae53f XEP-0045: specify use of <delay/> in subject message 2020-10-28 17:25:19 +01:00
Matthew Wild
64ae7088d6 XEP-0045: Clarify that the 307 status code should not be used alongside 333 for user disconnects
Includes a change of 'not recommended' to 'not advisable' per Council feedback.
2020-08-11 21:56:19 +02:00
Jonas Schäfer
e61d13f60a XEP-0045: add revision block 2019-05-15 17:34:20 +02:00
Georg Lukas
049f186631 XEP-0045: add 333 status to gc1-kick, thx Kev 2019-04-18 12:25:02 +02:00
Georg Lukas
84674a9221 XEP-0045: restrict gc1 kick to non-occupant full-JIDs, thx jonas’ 2019-04-18 09:26:22 +02:00
Georg Lukas
5282243d5d XEP-0045: do not claim compatibility with GC1.0 2019-04-18 00:41:10 +02:00
Georg Lukas
2408ea0373 XEP-0045: respond to GC1.0 join with kick, thx Kev 2019-04-18 00:37:29 +02:00
Georg Lukas
45e050c9c6 XEP-0045: fix wording in GC1.0 join 2019-04-18 00:29:49 +02:00
Kim Alvefur
4a71e3b82b XEP-0045: Move section about GC 1.0 further down
It's weird that the first thing you see under "Entering a room" is how
to do it in the old way, instead of the new way, which might mislead
implementers and make them miss the new way entirely.
2019-04-18 00:24:24 +02:00
Georg Lukas
11bf5c82fb XEP-0045: first and early attempt at removing GC1.0 2019-02-11 10:59:40 +01:00
Jonas Wielicki
4be4a8554b XEP-0045: Add implementation note about {jabberconference}x payload 2018-07-31 17:04:04 +02:00
Kevin Smith
1f4d98f66a Fix which witch is which 2018-03-12 11:03:14 +00:00
Georg Lukas
b017284eea XEP-0045: change feature according to Council feedback 2018-03-08 10:39:50 +01:00
Georg Lukas
7123a7a4ed XEP-0045: Implement stable IDs on Reflection
This updates the example and the wording to make stable IDs mandatory.
It also introduces the 'muc_stable_id' feature flag fig leaf to test
servers.

Per http://logs.xmpp.org/council/2018-02-28/#16:27:29

Discussion:

* https://mail.jabber.org/pipermail/standards/2010-November/023928.html
* https://mail.jabber.org/pipermail/standards/2014-July/028988.html
2018-03-06 14:50:52 +01:00
Jonas Wielicki
0b4754f43d XEP-0045: fix version block with actual publishing date 2018-02-23 08:13:22 +01:00
Jonas Wielicki
22dbb78a40 XEP-0045: Specify 333 status code 2018-01-16 10:50:05 +01:00
Jonas Wielicki
867616ab0b XEP-0045: add revision block 2017-09-01 16:42:57 +02:00
Jonas Wielicki
32bda0a904 Merge branch 'xep0045mucrejoin' of https://github.com/ge0rg/xeps into feature/xep-0045 2017-09-01 16:41:13 +02:00
Georg Lukas
d960697c73 XEP-0045: improve wording of client re-sync 2017-08-31 10:20:08 +02:00
Georg Lukas
8f684ace2b XEP-0045: Clarify wording for a client re-syncing to a MUC
TL;DR: whenever a client (re)sends a join, the MUC service should return
everything a newly joining client needs to know.

Discussion in
https://mail.jabber.org/pipermail/standards/2016-June/031180.html
2017-08-23 16:20:37 +02:00
Georg Lukas
2c4f007561 XEP-0045: add revision block 2017-06-17 09:00:44 +02:00
Georg Lukas
f2b9ece717 Changed wording from 'clients' to 'entities' 2017-03-14 09:23:28 +01:00
Georg Lukas
0dd74fde8d XEP-0045: clients MUST NOT rely on <x/> 2017-03-09 17:34:49 +01:00
Georg Lukas
cde2abe151 XEP-0045: Add <x/> tag to MUC-PMs 2017-02-22 18:53:07 +01:00
Emmanuel Gil Peyrot
c6cd7c1181 XEP-0045: Remove trailing whitespace in examples. 2017-01-29 08:29:41 -06:00
Sam Whited
337e41f925 XEP-0045: Typo and whitespace fixes 2016-12-03 10:35:00 -06:00
Sam Whited
8910053e92 XEP-0045: Tweak revision in preparation for 1.27 2016-10-29 16:27:37 -05:00
Christian Schudt
2a968984ad XEP-0045: Fix typo 2016-10-29 14:23:58 -07:00
Christian Schudt
7535f39785 XEP-0045: participant should be member 2016-10-29 14:23:58 -07:00
Sam Whited
f9a9139078 XEP-0045: Bump version to 1.27 2016-10-29 16:21:35 -05:00
Georg Lukas
cee524dbde XEP-0045: Business Rule for client-requested full resync
As discussed on the ML [0]: When a client re-joins a MUC where the MUC
service did not notice the client leaving, the client will end up with
an incomplete list of participants and no room subject.

This patch adds a sentence to the business rules section that explicitly
requires a MUC service to send a full sync whenever it receives a MUC
join presence (as opposed to the old groupchat protocol).

In my eyes, this is only a clarification of the existing standard
definition, so we do not need to bump the version.

Georg

[0] http://mail.jabber.org/pipermail/standards/2016-June/031180.html
2016-10-29 14:14:21 -07:00
Sam Whited
45960060ed XEP-0045: Fix wrong revision date 2016-05-17 09:11:33 -05:00
Sam Whited
f7ffad456d XEP-0045: Version bump for various bug fixes 2016-05-16 15:29:37 -05:00
Christian Schudt
530f271088 Remove status code 174 again 2016-05-16 15:25:46 -05:00
Christian Schudt
33d131a531 XEP-0045: Various bug fixes:
- Example 90 lacks status code 110 (self-presence)
- muc#roomconfig_allowpm is boolean, but should be list-single
- muc#roomconfig_allowinvites is list-single, but should be boolean
- Typo: Publish-Subcribe
- 15.6.2 Initial Submission: Status code 174 is missing.
- muc#role should be list-single
- muc#register_faqentry: mixed occurrences of text-single and text-multi
2016-05-16 15:25:46 -05:00
Peter Saint-Andre
49894184e5 small typos noticed by Nate Leon 2012-08-24 19:47:37 -06:00
stpeter
db8f1249e1 1.25 2012-02-08 10:06:16 -07:00
stpeter
f35e05df01 specified that edits to moderator list are based on nick, not jid 2012-02-01 18:20:12 -07:00
stpeter
04de67d670 fix to data form registration 2012-02-01 14:22:19 -07:00
stpeter
c93e1f0a37 1.25rc12 2012-01-24 14:58:46 -07:00
stpeter
ce9206c397 1.25rc11 2012-01-23 16:48:40 -07:00
stpeter
1b6f49bf6f 1.25rc10 2011-12-20 10:31:59 -07:00
stpeter
2487142e08 1.25rc9 2011-12-16 11:35:53 -07:00
stpeter
6b640d42e1 1.25rc9 2011-12-16 10:01:34 -07:00
stpeter
f4cc8b96a1 1.25rc8 2011-11-08 12:23:01 -07:00
stpeter
8a1d07e9a7 1.25rc7 2011-09-30 21:21:02 -06:00
stpeter
de29f8aad7 1.25rc6 2011-09-19 14:31:49 -06:00