2015-11-28 02:00:27 -05:00
|
|
|
xmpp-ircd
|
2015-11-28 01:48:35 -05:00
|
|
|
----------
|
|
|
|
|
|
2015-11-28 02:00:27 -05:00
|
|
|
This is a [fork](https://github.com/moparisthebest/xmpp-ircd) of a [fork](https://github.com/julien-picalausa/telepaatti)
|
|
|
|
|
of a [fork](https://github.com/davux/telepaatti) of [telepaatti](http://23.fi/telepaatti/), which was originally written
|
|
|
|
|
as a way for one user to connect to a XMPP server from their IRC client.
|
2015-11-28 01:48:35 -05:00
|
|
|
|
|
|
|
|
This particular fork aims to be ran as an IRC server connected to a single XMPP MUC as a standard XMPP component. This
|
|
|
|
|
will hopefully allow IRC server operators to migrate to hosting a real XMPP MUC with minimal headache or complaining from
|
|
|
|
|
hardcore IRC users, and also allow XMPP MUC operators to easily add IRC support.
|
|
|
|
|
|
|
|
|
|
Usage
|
|
|
|
|
-----
|
|
|
|
|
|
2015-11-28 02:00:27 -05:00
|
|
|
./xmpp-ircd.py --muc-server=chat.example.com --component-name=irc.example.com --component-pass=irc
|
2015-11-28 01:48:35 -05:00
|
|
|
|
|
|
|
|
Will connect to 127.0.0.1:5347 and serve the MUC chat.example.com over IRC on port 6667.
|
|
|
|
|
|
|
|
|
|
prosody for example would need this component configuration for the above command:
|
|
|
|
|
|
|
|
|
|
Component "chat.example.com" "muc"
|
|
|
|
|
|
|
|
|
|
Component "irc.example.com"
|
|
|
|
|
component_secret = "irc"
|
|
|
|
|
|
|
|
|
|
Development
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
Useful documentation:
|
|
|
|
|
* https://tools.ietf.org/html/rfc1459
|
|
|
|
|
* https://xmpp.org/extensions/xep-0045.html
|
|
|
|
|
|
|
|
|
|
Useful command to watch real IRC traffic between actual client and server, connect client to localhost:4444:
|
|
|
|
|
|
|
|
|
|
socat -v TCP-LISTEN:4444,fork OPENSSL:irc.freenode.net:6697
|
|
|
|
|
|
|
|
|
|
todo:
|
|
|
|
|
* NickServ/SASL auth
|
|
|
|
|
* finish /list /whois
|
|
|
|
|
* handle XMPP disconnecting
|
|
|
|
|
* handle shutdown cleanly
|
|
|
|
|
* other IRC commands?
|
|
|
|
|
|
|
|
|
|
known issues:
|
|
|
|
|
* nick changes are hacky, can lock up gajim private messages somehow...
|
|
|
|
|
* Nicks are only unique per-channel in XMPP, but per-server in IRC, I don't know that there IS a good solution for this.
|
|
|
|
|
The main problem this brings up is with private messaging, there is no way to know who you are chatting with. Nick
|
|
|
|
|
changes are also affected, but that only prevents you from changing your nick in a channel if you are joined with any
|
|
|
|
|
other channels where the nick is taken.
|
|
|
|
|
|
|
|
|
|
License
|
|
|
|
|
-------
|
|
|
|
|
GNU/GPLv3
|
