Greetings!
In XMPP, using PubSub(1) (XEP-0060), it is possible to store posts as Atom Syndication(2) entries into XMPP(3).
There are several XMPP extensions that apply it, namely XEP-0227 (4) and XEP-0472 (5) which make node xmpp:microblog:0 as a common choice to manage news for client accounts (e.g. blog@horizontal.land), yet a component account (e.g. pubsub.horizontal.land) may use all of its nodes for this purpose.
pubsub.horizontal.land/
|
|-- updates/
|-- Sombre
`-- Varied
|-- releases/
`-- events/
pubsub service/
|
|-- node/
|-- item
`-- item
|-- node/
`-- node/
I have made a script that realizes viewing PubSub node items as Atom XML feeds over HTTP(6).
- XEP-0060: Publish-Subscribe
- RFC 4287: The Atom Syndication Format
- Atom Over XMPP
- XEP-0277: Microblogging over XMPP
- XEP-0472: Pubsub Social Feed
- PubSub Over HTTP
Greetings!
In XMPP, using PubSub(1) (XEP-0060), it is possible to store posts as Atom Syndication(2) entries into XMPP(3).
There are several XMPP extensions that apply it, namely XEP-0227 (4) and XEP-0472 (5) which make node
xmpp:microblog:0as a common choice to manage news for client accounts (e.g.blog@horizontal.land), yet a component account (e.g.pubsub.horizontal.land) may use all of its nodes for this purpose.I have made a script that realizes viewing PubSub node items as Atom XML feeds over HTTP(6).