%ents; ]>
PubSub Social Feed This specification defines a way of publishing social content over XMPP. &LEGALNOTICE; xxxx ProtoXEP Standards Track Standards Council XMPP Core XMPP IM XEP-0060 RFC 4287 XEP-0277 psf Timothée Jaussoin edhelas@movim.eu edhelas@movim.eu https://edhelas.movim.eu 0.0.1 2022-09-26 tj Initial version.

Social Networking plaftorms are often built around the concept of feeds. XMPP offers, through &xep0060;, a really generic way of Publishing and Subscribing elements on XMPP nodes. This extension defines a way to publish social content on PubSub nodes using &rfc4287;

Social features in XMPP were historically built on the &xep0277; specifications. However in practice Microblogging was not applicable in more common cases and some related features were not used. The current XEP defines a more generic way of handling Social Feeds on XMPP by keeping the existing Microblogging features as a subset of it.
Profile
Defined by a specific Pubsub type (pubsub#type) a profile is a Pubsub Social Feed with some constraints. See the Profiles section.

A PubSub Social Feed can be located on any PubSub node on the XMPP network. Some specific use cases, such as the personal eventing (PEP) node Microblog is defined in the Profiles section.

The publication of a Post consist of a valid &rfc4287 entry embeded in a &xep0060; item.

The post content itself can be either text (content element without "type" attribute or with "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, his client MUST publish two "content" elements: a text one, and a XHTML one. For XHTML publishing, see &xep0060;.

hanging out at the Café Napolitano tag:montague.lit,2008-05-08:posts-1cb57d9c-1c46-11dd-838c-001143d5d5db 2008-05-08T18:30:02Z 2008-05-08T18:30:02Z ]]>

Note: The "title" element is required to be included in an "atom:entry" element according to &rfc4287;. An implementation MAY provide also "atom:summary" and/or "atom:content" elements too if it needs.

It's possible to insert some rich content in the post or comment. It can be some text formatting, images, etc. Only "xhtml" content type is supported for the moment by this document but possibly it will be extended later. Also, it is RECOMMENDED for the client to restrict XHTML content to the XHTML-IM subset (&xep0071;).

<div xmlns="http://www.w3.org/1999/xhtml"> <p>hanging out at the <strong>Caf&#233; Napolitano</strong></p> </div> tag:montague.lit,2008-05-08:posts-1cb57d9c-1c46-11dd-838c-001143d5d5db 2008-05-08T18:30:02Z 2008-05-08T18:30:02Z CapuChat ]]>

Because Juliet is subscribed to some Romeo's family PubSub service nodes. Romeo's XMPP server will send a PubSub notification to Juliet. The notification can include an XMPP message body for backwards-compatibility with Jabber clients that are not pubsub-capable (see Message Body ).

hanging out at the Caf&#233; Napolitano hanging out at the Caf&#233; Napolitano tag:montague.lit,2008-05-08:posts-1cb57d9c-1c46-11dd-838c-001143d5d5db 2008-05-08T18:30:02Z 2008-05-08T18:30:02Z CapuChat ]]>

Note: these alternate links were not posted by the original client because some clients can't compute them themselves. These things SHOULD be inserted at server side though.

Anyone can publish a post in reply to Romeo's post. Here we assume that a reply comes from Benvolio.

Note: Inclusion of the "thr:in-reply-to" element defined in &rfc4685; indicates the post to which the user is replying. This reply includes two such elements (one pointing to the HTTP URL for the post and the other pointing to the XMPP URI for the post.

Note: The post can be a reply to more than the only one another.

Benvolio Montague xmpp:romeo@montague.lit @romeo cappuccino this late in the day? tag:montague.lit,2008-05-08:posts-c4145006-1c53-11dd-b2d5-000bcd82471e 2008-05-08T18:31:21Z 2008-05-08T18:31:21Z ]]>

Assuming that Romeo has also subscribed to the same node he will receive the reply that Benvolio sent.

When Benvolio wants to repeat a Romeo's post, his client publishes the same post under a different name. But to be able to track the repeated post original author, Benvolio's client MAY use specific "atom:author" child node, "atom:name" and "atom:uri", containing, respectively, the name of the original post author, and his XMPP URI (JID).

The client SHOULD also put an "atom:link" element with "rel" attribute set to "via" and point it to the original post.

Romeo Montague xmpp:romeo@montague.lit hanging out at the Caf&#233; Napolitano tag:montague.lit,2008-05-08:posts-1re57d3c-1q46-11dd-748r-024943d2d5rt 2008-05-08T18:30:02Z 2008-05-08T18:32:02Z ]]>

Thus, a different author JID value lets the client know the item has been repeated from another one.

It's also possible for Benvolio to add his own thougths to the repost. To do this he SHOULD wrap the original content in the "xhtml:blockquote" element and after it add his own content. Also, the client MAY post reply without quotation to the original thread to inform users about the repost.

There are two different things that carry a similar sense: the XMPP Pubsub Item ID and the "atom:id" element. This section is devoted to make a separation between them.

The pubsub Item ID MUST be used when linking to an entry with an XMPP channel (i.e. by including it in the URI with the "xmpp" schema). the Atom entry ID MUST be built according to &rfc4287; and used in aggregators with the aim of revealing of post duplicates, reposts, mentions, syndications, etc.

Note that the rules of comparing, building and security notes for "atom:id" are listed in the &rfc4287;.

Depending on service policies and the value of the "pubsub#include_body" node configuration option, PubSub Social Feed notifications SHOULD include a message "body" element for backwards-compatibility with Jabber clients that are not pubsub-capable. It is RECOMMENDED for the XML character value of the "body" element to be the same as that of the "atom:title" child of the "atom:entry".

Juliet may want to know which places are Romeo's notices related to. That's why Romeo's client MAY geotag microblog entries, using the &xep0080; protocol for storing geolocation information.

Romeo's client MUST create a "geoloc" element, with the &xep0080; reference namespace: "http://jabber.org/protocol/geoloc".

Romeo Montague xmpp:romeo@montague.lit Is lost in the forest. Need help! tag:montague.lit,2008-05-08:posts-1zr23z8a-3g12-34fh-750b-120867gjc1sqh 2008-05-08T18:43:01Z 2008-05-08T18:43:01Z 48.171761 -3.3667986 France FR Brittany ]]>

PubSub Social feeds are specified under profiles. Those profiles are constraints applied to nodes and defined by a specific PubSub type (see &xep0060;#registrar-formtypes-metadata)

All the profiles MUST base their default configuration on the Base profile .

This profile is specified by the PubSub type `urn:xmpp:social:0` and define a generic PubSub Social Feed that can be hosted on any PubSub service node or &xep0163; node.

Those restrictions MUST be used by all the other profiles defined bellow and in other XEPs based on Pubsub Social Feed.

  1. The "pubsub#notify_retract" MUST be set to `true` to provide clients the ability to track if some items were retracted and reflect such changes in the UI correctly.
  2. The "pubsub#max_items" MUST be set to the `max` value, as defined in the &xep0060;.
  3. The "pubsub#persist_items" MUST be set to `true`.
  4. The "pubsub#send_last_published_item" SHOULD be set to `never`.
  5. The "pubsub#deliver_payloads" SHOULD be set to `false`. The social content can be quite large so it is advised to let the clients to manually query the content if it is not already cached.

This profile is defined by the PubSub type `urn:xmpp:microblog:0` as defined in &xep0277; and MUST be created and configured under the PEP `urn:xmpp:microblog:0` node.

On top of the Base profile Pubsub Node Configuration the following node configuration is applied:

  1. The "pubsub#access_model" SHOULD be set to `presence` by default to allow the other presence JIDs to receive the newly published elements without an explicit subscription (using the +notify feature of &xep0163;).

This profile is defined by the PubSub type `urn:xmpp:gallery:0` and can be hosted on any PubSub service.

All the items published in a gallery node MUST only have at least one attached picture. This picture MUST be of type `enclosure` as specified in &rfc4287;.

]]>

The client SHOULD check that the comment author information (provided in the "author" element) is valid, by checking that the "publisher" item attribute value matches the "uri" element value. If there is a difference or the check can not be performed because there was not a "publisher" attribute included, the comment can be displayed, but it is RECOMMENDED to specify there is a security problem.

This document requires no interaction with &IANA;.

The ®ISTRAR; is requested to issue an initial namespace of "urn:xmpp:social:0" and "urn:xmpp:gallery:0".

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