-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMPP: Post to PubSub #3300
Comments
I beg your pardon. Please move this to getpelican/pelican-plugins/issues |
That would be really cool. Especially if a comment section could be done that way too. |
NodesYes, comments can also be managed in a similar manner. Perhaps XEP-0248 PubSub Collection Nodes would be useful for comments, though it might not be necessary.
We can allocate them by nodes
XMPP ClientsIn what fashion did you think to handle comments? I suppose we can synchronize comments from HTTP and from XMPP. For comments via XMPP, we might want XMPP clients (like Movim and Libervia) to handle. Other clients: Once Pelican has PubSub support, it would be easy to persuade Dino, Cheogram, Converse, Gajim, Kaindan, monocles, Psi etc. to allow PubSub for comments and reactions. More InformationWe have a good discussion at Chyrp Lite (PHP CMS) I have also made a proposal for scheme for managing CMS in node |
Please be aware of the following implementations. Reading from PubSubSee code at: codeberg.org Sending to PubSubSee function I am willing to handle the XMPP code for you if you want. |
This is way over my head, I just happen to host my own Pelican and XMPP server and would really like to see an XMPP renaissance. Unfortunately, other than with licensing, I don’t think I can help much here. Would love to see how it all plays together though! To make things even more connected, Libervia has some code to bridge XMPP PubSub with ActivityPub: |
|
Feature Request
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@getpelican.com
), yet a component account (e.g.pubsub.getpelican.com
) may use all of its nodes for this purpose.I have made a script using the slixmpp library that realizes viewing PubSub node items as Atom XML feeds over HTTP.
I am willing to assist to add this feature.
The text was updated successfully, but these errors were encountered: