From 90cfc9182986090d184b1d87fa7c18afd7186b07 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Tue, 1 Nov 2016 20:52:57 -0500 Subject: [PATCH] Accept new "spoilers" protoxep --- inbox/spoiler.xml | 185 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 185 insertions(+) create mode 100644 inbox/spoiler.xml diff --git a/inbox/spoiler.xml b/inbox/spoiler.xml new file mode 100644 index 00000000..5c796751 --- /dev/null +++ b/inbox/spoiler.xml @@ -0,0 +1,185 @@ + + +%ents; +]> + + +
+ Spoiler messages + + This specification defines an XMPP protocol extension that provides a + method for indicating a message is a spoiler and should be displayed as + such. + + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + + + + NOT_YET_ASSIGNED + + Severino + Ferrer de la Peñita + soul@blastersklan.com + soul@blastersklan.com + + + Xavier + Ferrer de la Peñita + vaulor@openmailbox.org + vaulor@blastersklan.com + + + 0.0.1 + 2016-10-31 + ??? +

First draft.

 + +
+ +

+ 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 an + <spoiler> element qualified by the 'urn:xmpp:spoiler:0' namespace + and optionally, <spoiler> elements may possess a 'hint' attribute + that warns about the topic of the spoiler message. +

+ + This is a very long message so I'm going to hide inside a spoiler [...] + + +]]> + + And at the end of the story, both of them die! It is so tragic! + + +]]> + + +

+ It MUST be clear a message is in fact a spoiler and its content MUST only + be displayed upon user's request. +

+

+ 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). +

+

+ Clients SHOULD display spoiler's hint, if any, before showing message's + content. +

+

+ Clients MAY display spoiler's hint even after showing message's content + (e.g. as a header or title of the message). +

+

+ Users SHOULD be able to 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;.

+ + + +

This specification defines the following XML namespace:

+
    +
  • 'urn:xmpp:spoiler:0'
    • +
+

+ Upon advancement of this specification to draft status, the ®ISTRAR; + shall include the foregoing namespaces in its registry of protocol + namespaces &NAMESPACES; and in its disco features registry + &DISCOFEATURES; as defined in &xep0030;. +

+ + urn:xmpp:spoiler:0 + Indicates that a message should be hidden by default. + xxxx + +]]> + + + + + + + + + + + + + + + + + + + +]]> + +