mirror of
https://github.com/moparisthebest/xeps
synced 2025-03-03 01:51:49 -05:00
64f87e1d2a
The requirement to strip `<private/>` by the sending server was in the XEP from day 1. It was later changed from "MUST" to "SHOULD" and from "sending server" to "receiving server", so that the latter could also prevent normal message routing. As this behavior only ever affected the `<private/>` element and not the `<no-copy/>` hint (introduced in 2017), which should be treated in a similar but not equal way, and there is a security benefit in letting the receiving client know that message routing was manipulated, it makes sense to remove this requirement. As there is no negative effect of keeping another element in delivered messages, nobody complained about `<no-copy/>` not being stripped, and bumping Carbons today would be rather unfortunate, this is done without a namespace bump, despite "breaking" the specification.
XMPP Extension Protocols (XEPs)
About
This repository is used to manage work on XMPP Extension Protocols (XEPs), which are the specifications produced by the XMPP Standards Foundation (XSF). See http://xmpp.org/ for details. The rendered documents can be found here:
Contribution
Please use this repository to raise issues and submit pull requests:
https://github.com/xsf/xeps/issues https://github.com/xsf/xeps/pulls
For in-depth technical discussion, please post to the standards@xmpp.org email list:
https://mail.jabber.org/mailman/listinfo/standards
To submit a new proposal for consideration as a XEP, please read this page:
https://xmpp.org/about/standards-process.html#submitting-a-xep
XEP-0001: XMPP Extension Protocols defines the standards process followed by the XMPP Standards Foundation.
Editor
Documentation for Editors is in the docs folder.