Skip to content

Microblogging

Jump to bottom
Emiel Kollof edited this page Mar 27, 2026 · 6 revisions

Microblogging (XEP-0277 / XEP-0472)

XMPP microblogging lets you publish short posts — analogous to Mastodon/Twitter toots/tweets — directly over XMPP via PubSub nodes. Posts are Atom entries stored on a PubSub service; contacts who subscribe to your urn:xmpp:microblog:0 PEP node receive them in real-time.

Status: XEP-0277 is Deferred; XEP-0472 is Experimental. Both are implemented in this plugin for the write side (post, reply, repeat, retract, subscribe, unsubscribe, comments) and the receive side (incoming PEP push events are rendered automatically with deduplication).

How it works

  • Posts live on a PubSub node (most commonly urn:xmpp:microblog:0 on a PEP service, or any XEP-0060 pubsub service).
  • Each post is an Atom entry (<entry xmlns='http://www.w3.org/2005/Atom'>).
  • XEP-0472 requires the publish-option pubsub#type=urn:xmpp:microblog:0 and the capability string urn:xmpp:pubsub-social-feed:1 to be advertised — both are handled automatically by this plugin.
  • Threaded replies use RFC 4685 thr:in-reply-to inside the Atom entry.
  • Boosts/repeats use <link rel='via'> (XEP-0472 §4.5).
  • Comments nodes are linked via <link rel='replies'> (XEP-0277 §3).

Compatible servers / clients

Software Role
Movim Full social feed — post, reply, retract, timeline
Libervia / Salut-à-Toi Full implementation
ejabberd PubSub mechanics work; no built-in social UI
Prosody + mod_pep PubSub node creation/subscription works

Short aliases (#N)

When you fetch a feed with /feed, each displayed item is assigned a short #N alias shown in green before the title (e.g. #1, #2, #3). You can use these aliases in place of the full item-id in any write command:

/feed reply #3 Nice post!
/feed repeat #3 Great content
/feed comments #3
/feed retract #3

Aliases are assigned per feed-buffer and reset when you reconnect or close WeeChat.

Commands

Publish a post

Long form (explicit service and node):

/feed post <service-jid> <node> [--open] <text>

Short form (from a feed buffer — service/node inferred):

/feed post <text>
/feed post --open <text>
/feed post -- <text>       # use '--' when body starts with a JID-like word

The --open flag sets pubsub#access_model=open so the post is publicly readable without a subscription.

Use -- as an explicit separator when the post body starts with a word containing . or @ (e.g. a URL or username) to avoid the parser treating it as a service JID:

/feed post -- hello@world.example is a great site

Examples:

# Post to your own PEP microblog
/feed post movim.eu urn:xmpp:microblog:0 Hello from WeeChat!

# Public post
/feed post movim.eu urn:xmpp:microblog:0 --open This is a public post

# Short form from a feed buffer
/feed post Hello everyone!

# Short form with body starting with a URL
/feed post -- https://example.com check this out

Failed publishes are reported in the buffer with the server error condition (e.g. forbidden, item-not-found).

Reply to a post (threaded)

Long form:

/feed reply <service-jid> <node> <item-id|#N> [--open] <text>

Short form (from a feed buffer):

/feed reply #N [--open] <text>

The reply is a new Atom entry containing thr:in-reply-to ref="<atom-id>". The ref attribute uses the Atom <id> URI of the original entry (cached from the most recent fetch). Clients such as Movim render threaded conversations from these references.

Examples:

# Long form
/feed reply movim.eu urn:xmpp:microblog:0 abc-1234 That's a great point!

# Short form using alias
/feed reply #3 That's a great point!

# Reply to a comments node item (XEP-0277)
/feed reply #3 Nice comment!

Boost / repeat a post (XEP-0472 §4.5)

Long form:

/feed repeat <service-jid> <node> <item-id> [comment]

Short form (from a feed buffer):

/feed repeat #N [comment]

Publishes a new Atom entry with <link rel='via' href='xmpp:…' ref='atom-id'/>. The ref attribute is set to the original entry's Atom <id> URI when known (cached from the most recent fetch), enabling receiving clients to resolve the full provenance chain.

An optional comment is included in the entry body.

Examples:

# Boost without comment
/feed repeat movim.eu urn:xmpp:microblog:0 abc-1234

# Boost with comment (long form)
/feed repeat movim.eu urn:xmpp:microblog:0 abc-1234 Great post, sharing this!

# Short form with alias
/feed repeat #3

# Short form with alias and comment
/feed repeat #3 Great content — everyone should read this

Retract (delete) a post

Long form:

/feed retract <service-jid> <node> <item-id>

Short form (from a feed buffer):

/feed retract #N

Sends a PubSub retract IQ with notify='true'. Subscribers receive a retraction notification; supporting clients remove the post from their timeline. Server errors (forbidden, item-not-found) are reported in the buffer.

Note: Retraction is best-effort. Contacts who already received the item may still have a local copy.

Examples:

/feed retract movim.eu urn:xmpp:microblog:0 abc-1234
/feed retract #3

Fetch comments for a post

/feed comments <service-jid> <node> <item-id|#N>
/feed comments #N    # short form from a feed buffer

If the post carries a <link rel='replies'> element (XEP-0277 §3), this opens a dedicated FEED buffer and fetches the comments node. The replies URI is cached when the post is first fetched or received via push.

If no comments link was advertised the command reports that no cached link is available — run /feed <service> <node> first to populate the cache.

When a post has a comments node, the feed buffer shows a hint:

  Comments: /feed comments #3

Examples:

/feed comments movim.eu urn:xmpp:microblog:0 abc-1234
/feed comments #3

Subscribe and unsubscribe

/feed subscribe <service-jid> <node>
/feed unsubscribe <service-jid> <node>
/feed subscriptions <service-jid>

Sends XEP-0060 subscribe/unsubscribe IQ stanzas to the service. Success and error feedback is printed in the buffer where the command was run (not always the account buffer). Errors include the XMPP error condition (e.g. not-authorized, item-not-found).

/feed subscribe news.movim.eu Phoronix
/feed unsubscribe news.movim.eu Phoronix
/feed subscriptions news.movim.eu

Reading a microblog feed

Use the standard /feed read commands:

/feed movim.eu urn:xmpp:microblog:0           # fetch last 20 posts
/feed movim.eu urn:xmpp:microblog:0 --limit 5 # fetch last 5 posts
/feed movim.eu urn:xmpp:microblog:0 --before <item-id>  # older page (RSM)
/feed movim.eu urn:xmpp:microblog:0 --latest  # clear saved cursor, fetch newest page

Each node opens in its own dedicated WeeChat buffer. The RSM cursor is persisted in LMDB so subsequent /feed calls automatically continue from where you left off. Use --latest to go back to the newest page after paging back through older items.

Deduplication

Items already rendered in a previous /feed invocation are not re-displayed. The seen-item set is persisted in LMDB so deduplication survives reconnects.

Receiving posts from contacts

When a contact publishes to their urn:xmpp:microblog:0 PEP node, the push event is delivered automatically and rendered in the WeeChat buffer for that contact. Each item displays:

  • Author name and timestamp
  • Title (bold) with #N alias in green
  • Body text
  • Thread reference (In reply to: #N or the raw item UUID)
  • Boost provenance (Repeated from: xmpp:…)
  • Comments hint (Comments: /feed comments #N) when a replies link is present
  • Category tags
  • Enclosure/attachment URLs
  • Geolocation
  • XHTML/HTML content rendered with WeeChat colors

Duplicate items (already seen via IQ fetch) are suppressed automatically.

Capability advertisement

The plugin advertises the following in its entity caps (XEP-0115) and disco#info response so social-feed-aware servers and clients can discover support:

  • urn:xmpp:microblog:0+notify — subscribe to contacts' microblog PEP nodes
  • urn:xmpp:pubsub-social-feed:1 — XEP-0472 social feed capability

See also

Clone this wiki locally