Open sjehuda opened 2 months ago
Maybe don't assume that people are familiar with this and describe it from a "how is this useful" perspective.
XMPP -> PubSub (XML) -> Atom (XML)
PubSub + Atom = Functional website hosted on XMPP
There are several observations:
Note: I am well aware that VPS can coast as low as $3 a month.
Mr. Kevin Cox of statit has made the following argument of post processing (after deployment):
I don't see the advantage of integrating this into statit.
I have a very similar workflow with pinging WebSub hubs about the feeds after a deploy. However I just do this with a curl command after the deploy step.
For which I have suggested to use PubSub nodes as both a mean of publishing and a mean of storing source files, which makes it also as a backup and synchronization solution:
Publishing node <- Public or restricted to certain JIDs
|- Item (ID: 0001)
|- Atom entry (HTML inside)
|- Item (ID: 0002)
|- Item (ID: 0003)
|-
Management node <- Private only to the account owner.
|- Item (ID: 0001)
|- Source file
|- Item (ID: 0002)
|- Item (ID: 0003)
|-
Currently, only two platforms are offering a user-friendly view of PubSub are Movim and Libervia and both are web based. Yet, the more CMS software to implement PubSub, the more desktop clients would add support for PubSub.
The basic solution I offer is not the best, yet is sensible, in a form of providing a web interface to fetch content from pubsub node and display it as HTML or as XML (converted into HTML using an XSLT stylesheet) which is readable with a feed reader.
I have elaborated on it at https://github.com/xenocrat/chyrp-lite/issues/250#issuecomment-2066270209 (CMS based on PHP).
Thursday, I am expected to participate in a virtual meeting with Backdrop CMS (also CMS based on PHP) about the matter. I would want to record the session and use it as a good presentation of explaining the matter.
I surely hope to have a CMS with support for PubSub very soon; and when there would be a working CMS of both HTML (CMS) and XML (PubSub) it would be easy to refer to it as a working example.
I think @sjehuda is an AI experiment. Are there bots filling GitHub with fake projects and creating fake issues on existing projects?
I have updated my last post.
Reported sjehuda's comments as spam, blocked user from project.
Reported sjehuda's comments as spam, blocked user from project.
...why?
I don't think @sjehuda is an AI, he contacted me via email.
But I explained to him that:
So I would suggest to unblock him, so he can edit and improve this or maybe better create one new issue.
I currently don't think this could be in scope for moin2 development until moin 2.1 though.
I confirm that @sjehuda is not a bot or a spammer. Please unmark comments.
The feature request is really important!
You can look for example here:
For example, you can contact on Psi+ XMPP MUC Room: xmpp:psi-dev@conference.jabber.ru?join
To use XMPP, there is a client list (Desktop, Mobile or Web) here:
I have unblocked @sjehuda and unhide his posts. I apologize for mistaking him as a bot.
Thank you!
We are all friends here and we are all sharing similar causes!
Please pardon me for the belated respond.
Below is a part of a correspondence which I have had with Thomas:
I hope this clearly expains the matter.
I know a little, but only very little and even I could not extract much from what you wrote, especially not "what problem are we solving here?", practical use cases, why and how somebody would want to use something like what you proposed.
Using XMPP as a hosting medium with XML files that MoinMoin already generates.
While HTML pages of MoinMoin are namely dedicated to HTTP browsers, XML can be dedicated to XMPP just as it is dedicated to HTTP feed readers.
This is useful, in general, and in particular to communities revolving around XMPP, such as Gajim, Psi, Speed Dreams and many more who maintain a wiki and want to incorporate Wiki-CMS like MoinMoin with XMPP.
That would make MoinMoin a CMS that can be also viewed and managed from XMPP alone.
Essentially, to the aforementioned XMPP communities, adding support to XMPP PubSub would allow editing MoinMoin wiki while having an interactive chat on an XMPP groupchat.
- Uniformity of data (disputable).
By "uniformity" I meant to HTML. Yet, it would be posible to upload both files to two different nodes: One node for source files (to be used for editing) and one for HTML pages (to be used for viewing).
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@moinmo.in
), yet a component account (e.g.pubsub.moinmo.in
) 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.