It's very easy to make sure ZNC keeps running, e.g. If you add channels for ZNC to join automatically, don't forget the initial '#' it's required. See the wiki for more information on modules. I answered 'yes'.Īs for user modules, I went with: chansaver, so ZNC remembers what channels I join and part keepnick, to keep trying for my primary nick nickserv to auth me with NickServ away to set me away when I detach (disconnect my clients) and save private messages, I think (documentation is unclear) awaynick to change my nick when I go away, to make it more obvious I'm not present. That means you are likely to see the same stuff several times, but also that you will always have context. Answering 'yes' to 'Would you like to keep buffers after replay?' will mean that if you connect from your computer and get to see what you missed, connecting later from your iPhone will show those same messages (no matter that they're already been replayed). The default is plenty I've turned it down to 30. 'Number of lines to buffer per channel' means that each time you connect, you'll see that many lines of channel log from just before you connected. The hostname of your shell is what you'll connect to from the outside, e.g. You should activate SSL for encryption it's no hassle. After setting the port, don't forget to forward it in your router or firewall. Some things that may not be obvious: 'y' or 'n' is enough when answering the 'yes'/'no' setup questions, or just hit Return to go with the default. The README that came with the source, and the ZNC wiki, do a pretty good job of explaining the options. Later, you can modify it by hand (it'll be somewhere like ~/.znc/configs/znc.conf), or even from IRC ( /msg *status help). Run znc -makeconf from the command line to interactively create a configuration file. With those settings, it compiled without a hitch for me. There's no need to mess with -with-openssl OS X has that covered.

configure -prefix =/usr/localĮnsure /usr/local/bin is in your PATH. You need the OS X developer tools or equivalent for this.Īfter downloading the tar file from this page, unpacking it and changing into that directory, I did. I compiled from source according to the wiki instructions. I like about ZNC that it works well with very little fuss, and that it's fairly well documented. I eventually found one I liked, on the advice of on Twitter: ZNC. I looked at a few, but they were all severely underdocumented and/or didn't work as expected. I wanted a bouncer that I could run off my OS X home server. I can also share a single apparent IRC connection between my home computer, my work computer and my phone. With iPhone IRC clients, it's especially useful, since third-party iPhone applications don't maintain their connection when you switch away from them. This means no more connecting in the middle of something and not having context. This offers various benefits and possibilities the major one for me is that I appear constantly connected and will see a scrollback of missed messages when I reconnect my client.

An IRC bouncer is basically a proxy server that you connect to IRC through.

Limechat irc support