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
Publishing posts to PubSub, either a dedicated PubSub service (e.g. pubsub.ekyllrb.com) or to a personal account (e.g. george@ekyllrb.com).
Motivation
Why do you want to see this feature in Jekyll?
More exposure, (1) be it to people communicating on my XMPP server and then check the dedicated PubSub service, or (2) be it by people communicating with other people and then they check their PubSub nodes of each other.
What makes you sure that it should not be implemented at the plugin level, but in Jekyll core?
Because this would allow people that do ot have a website nor server that are open for incomming connections - for whatever reason - to publish contents using their own XMPP account alone. No server of their own would be needed to publish whatever they want.
What use cases does it support?
Website administrators (obviously)
Real users! (New audience: Any one)
NOTE: Please be mindful of the Jekyll philosophy (https://jekyllrb.com/philosophy/), particularly Section 5. Think about if 90% of the users would benefit from your feature request, and whether your feature would be better off in a plugin.
With clause 2 in mind, over 110% of the users would benefit from this feature request!
Guide-level explanation
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 urn:xmpp:microblog:0 as a common choice to manage news for client accounts (e.g. blog@jekyllrb.com), yet a component account (e.g. pubsub.jekyllrb.com) may use all of its nodes for this purpose.
A Ruby library that might be utilized would be XMPP4R.
I have made a script that realizes viewing PubSub node items as Atom XML feeds over HTTP.
Summary
Publishing posts to PubSub, either a dedicated PubSub service (e.g.
pubsub.ekyllrb.com
) or to a personal account (e.g.george@ekyllrb.com
).Motivation
Because this would allow people that do ot have a website nor server that are open for incomming connections - for whatever reason - to publish contents using their own XMPP account alone. No server of their own would be needed to publish whatever they want.
With clause 2 in mind, over 110% of the users would benefit from this feature request!
Guide-level explanation
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
urn:xmpp:microblog:0
as a common choice to manage news for client accounts (e.g.blog@jekyllrb.com
), yet a component account (e.g.pubsub.jekyllrb.com
) may use all of its nodes for this purpose.A Ruby library that might be utilized would be XMPP4R.
I have made a script that realizes viewing PubSub node items as Atom XML feeds over HTTP.
XEP-0060: Publish-Subscribe
RFC 4287: The Atom Syndication Format
Atom Over XMPP
XEP-0277: Microblogging over XMPP
XEP-0472: Pubsub Social Feed
XMPP4R
PubSub Over HTTP
Reference-level explanation
Publish items to XMPP PubSub nodes as Atom format. See the references to Movim and to PubSub Over HTTP above.
Drawbacks
None.
Unresolved Questions
None
The text was updated successfully, but these errors were encountered: