You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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@website.net), yet a component account (e.g. pubsub.website.net) may use all of its nodes for this purpose.
In short, PubSub allows to use XMP as a publishing platform.
XMPP has an XEP extension called Publish-Subscribe (XEP-0060).
I have made an HTML software (Rivista XJP) that reads PubSub.
Please see the video presentation of 7 minutes and 44 seconds
at https://video.xmpp-it.net/w/vNqcMooy3pqRAZ8Yb8grr1
The content that is displayed by Rivista XJP is not stored in the
server that serves Rivista XJP; rather, the contents are stored, in a
standard fashion, on XMPP servers.
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@website.net
), yet a component account (e.g.pubsub.website.net
) 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.
The text was updated successfully, but these errors were encountered: