Sometimes, people have the need to send large texts related to the current topic but because of their length, make it hard to follow the conversation (specially on mobile devices). On other occasions, people may want to discuss or just make a little quick comment related to a film or a book in a conversation with multiple people that may or may not know the plot. Also, every now and then, people may want to send a private message (in the sense that people near the receiver must not be able to read) or inline images to someone is known is in a public enviroment like libraries, coffehouses, bars, etc.

This specification defines a way to indicate message's content does not have to be displayed until receiver requests to do so.

If a client implements spoiler messages, it MUST specify the 'urn:xmpp:spoiler:0' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.

Messages user wants to be sent as spoilers, MUST contain a <spoiler> element qualified by the 'urn:xmpp:spoiler:0' namespace and optionally, <spoiler> elements may contain character data as a hint that warns about the topic of the spoiler message. They may also possess the 'xml:lang' attribute.

1. It MUST be clear that a message is in fact a spoiler and its content MUST only be displayed upon user's request.
2. Clients MAY provide a way to display spoilers always uncovered, without the need of interaction by the user (e.g. in the client's settings).
3. Clients SHOULD display spoiler's hint, if any, before showing message's content.
4. Clients MAY display spoiler's hint even after showing message's content (e.g. as a header or title of the message).
5. Users SHOULD uncover or hide a spoiler message at will, anytime.

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.

This document requires no interaction with &IANA;.