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.
0 Comments
Leave a Reply. |