mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-21 23:28:51 -05:00
Allow server to limit retract timeframe
This commit is contained in:
parent
56255283cf
commit
d0f3a49b08
@ -47,6 +47,7 @@
|
||||
Joining Channel Clarification,
|
||||
Coming online clarification,
|
||||
Going offline JID error,
|
||||
Allow servers to limit retract time frame,
|
||||
|
||||
</p></remark>
|
||||
</revision> <revision>
|
||||
@ -1745,7 +1746,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
|
||||
|
||||
<section3 topic="Retracting a Message" anchor="usecase-retract">
|
||||
<p>
|
||||
A MIX channel MAY support message retraction, where the sender of a messages or an authorized administrator deletes a message. If this is done the original message MAY be replaced by a tombstone. The protocol to request retraction does this by adding to the message a <retract> element qualified by the 'urn:xmpp:mix:1' namespace. The <retract> element MUST include an <id> attribute that holds the id of the original message. A message and it's retraction shown in the following example.
|
||||
A MIX channel MAY support message retraction, where the sender of a messages or an authorized administrator deletes a message. A MIX channel MAY limit the time frame in which a message is allowed to be retracted, for example to prevent retraction of very old messages. If this is done the original message MAY be replaced by a tombstone. The protocol to request retraction does this by adding to the message a <retract> element qualified by the 'urn:xmpp:mix:1' namespace. The <retract> element MUST include an <id> attribute that holds the id of the original message. A message and it's retraction shown in the following example.
|
||||
</p>
|
||||
<example caption="User Retracts a Message"><![CDATA[
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user