Add <no-copy/> hint.
+Some clients might want to avoid Carbons on a single message, while still keeping all of the other semantics of Carbon support. This might be useful for clients sending end-to-end encrypted messages, for example. To exclude a &MESSAGE; from being forwarded to other Carbons-enabled resources, the sending client must add a <private/> element qualified by the namespace "urn:xmpp:carbons:2" and a <no-copy/> hint according to &xep0334; as child content elements to the &MESSAGE; stanza.
++ Some clients might want to avoid Carbons on a single message, while still + keeping all of the other semantics of Carbon support. + This might be useful for clients sending end-to-end encrypted messages, for + example. + The sending client MAY exclude a &MESSAGE; from being forwarded to other + Carbons-enabled resources, by adding a <private/> element qualified by + the namespace "urn:xmpp:carbons:2" and a <no-copy/> hint as described + in &xep0334; as child elements of the &MESSAGE; stanza. +
-Note: use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.
+Note: use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.