XMPP support [$70] #78
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/znc#78
Reference in new issue
Block a user
It would be nice to have one, at both sides - client and server
--- There is a **[$70 open bounty](https://www.bountysource.com/issues/683-xmpp-support?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).This should also support BOSH for using XMPP over HTTP to fix #139
Uhm, kylef, how is this related to it?
If we can get the XMPP server relaying to IRC. Then with BOSH we could use a javascript XMPP client such as http://strophe.im/strophejs/. It would be easy to build something based on-top of this into the web interface.
http://www.speeqe.com/ is a site which uses strophejs.
BOSH specification: http://xmpp.org/extensions/xep-0206.html
This would be far simpler, and modular than making an IRC<>HTTP module.
might as well throw this in: http://www.bitlbee.org/main.php/news.r.html
As this was requested a year ago, I'd like to revisit this =) I think websockets may be the answer at this point in time. Something like a JSON API that runs over a websocket would be a killer feature. Long term I'd like to see this so that IRC clients, webclients, refrigerators, etc... could link up and pull down backlog, send messages, and invoke all the other fancy IRC commands.
Personally one of the things that bothers me most about bouncers and IRC clients is the lack of integration. Of course the IRC endpoint would always continue to exist, but by offering a websocket endpoint it would be easy to write plugins for many of the popular open source IRC clients for better bouncer integration. I'd love to be able to have my IRC client actually display the timestamps as timestamps rather than as part of the message. Maybe we could work out an open spec like RSS but for IRC bouncers. Completion of this would make web based IRC clients a snap to create.
With the websocket spec finalized and support bundled in all major browsers, I think this makes the most sense.
@ericbarch Regarding timestamps, take a look at http://www.ircv3.org/extensions/server-time-3.2
following the JSON idea it should use an api similar (if not the same) as cloud IRC ( https://github.com/irccloud/irccloud-tools/wiki/API-Overview ) making it easier for client developers to support both znc and cloud irc
What is the goal of this issue? Having ZNC be a smart(?) proxy to XMPP clients connecting to XMPP or cross-connecting IRC client to XMPP or XMPP client to IRC?
This issue was opened in 2012 and the latest comments are from 2013, and I think XMPP has possibly went past the time it could have used ZNC as looking at what Conversations excepts from XMPP server there are message carbons (XEP-0280) which I think makes new messages be sent to all connected clients (as XMPP does multi-client by itself) and message management archive (XEP-0313) which is server-side history and deprecates playback buffers in my opinion.
I often link to The State of Mobile XMPP in 2016 on gultsch.de for a nice overview on how it performs nowadays.
Addition: I think I have used XMPP daily for a bit over two or three years now and saw this issue again yesterday and today I started wondering more about this as during the years I didn't think of missing ZNC to XMPP even if I use it for all my IRCing.