From 8eff2467b0234a9dc7a2b1ae06b14df6c8cc9f02 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Jaussoin?= Date: Tue, 3 Dec 2024 19:03:25 +0100 Subject: [PATCH] New ProtoXEP: Pubsub Stories --- inbox/stories.xml | 125 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) create mode 100644 inbox/stories.xml diff --git a/inbox/stories.xml b/inbox/stories.xml new file mode 100644 index 00000000..e4a66059 --- /dev/null +++ b/inbox/stories.xml @@ -0,0 +1,125 @@ + + + %ents; +]> + + +
+ Pubsub Stories + This specification defines a way of publishing Stories over XMPP. + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + XMPP IM + XEP-0060 + XEP-0163 + XEP-0472 + RFC 4287 + + + + ps + + Timothée + Jaussoin + edhelas@movim.eu + edhelas@movim.eu + https://edhelas.movim.eu + + + 0.0.1 + 2024-12-03 + tj + Initial version. + +
+ + +
+ +
Story
+
An item stored in a Stories Pubsub node.
+
+
+
+ + +

Introduced by Snapchat in 2012 Stories are a way for users to share content that can be viewed for a specific amount of time in chronological order.

+ +

&xep0472; already defines a generic way of publishing social content on XMPP. This extension defines a way to publish Stories content on a user &xep0163; node.

+ +

This extension extends &xep0472; by defining a new Profile (see Profiles) called Pubsub Stories.

+
+ + +

If an entity implements Pubsub Stories, it MUST specify the 'urn:xmpp:pubsub-social-feed:1' and 'urn:xmpp:pubsub-social-feed:stories:0' features in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.

+ +

If an entity wish to receive notifications from a contact when a Story is published it should also declares it in its service discovery followed by "+notify"

+ + + + ... + + + + ... + + + ]]> +
+ + + +

This profile is defined by the Pubsub type "urn:xmpp:pubsub-social-feed:stories:0" and is hosted on a "urn:xmpp:pubsub-social-feed:stories:0" &xep0163; node.

+ +

All the items published in a Pubsub Stories node MUST have only one attached media. This media MUST be of type "enclosure" as specified in &rfc4287;.

+ +]]> + + +

Stories node MUST base their default configuration on the Base Profile and:

+
    +
  1. The "pubsub#type" MUST be set to "urn:xmpp:pubsub-social-feed:stories:0"
  2. +
  3. The "pubsub#access_model" SHOULD be set to "presence".
  4. +
+
+
+
+ + +

Subscribers clients SHOULD hide the items after a specific amount of time, usually 24 hours.

+

Publishers clients SHOULD retract the items after a specific amount of time, usually 24 hours.

+
+ + +

There are no security features or concerns related to this proposal.

+
+ + +

This document requires no interaction with &IANA;.

+
+ + +

The ®ISTRAR; is requested to issue an initial namespace of "urn:xmpp:pubsub-social-feed:stories:0".

+
+ + +

+ This specification re-uses the schema for the Atom content format, i.e., the 'http://www.w3.org/2005/Atom' namespace (see + &rfc4287; + ). +

+
+ +
\ No newline at end of file