Hardware Reference
In-Depth Information
These messages are from a
virtual user
. The prefix for virtual users is an
*
and this user
is
status
. While ZNC is connected to multiple networks, you are only seeing the
BitlBee network at the moment. Here you can interact with BitlBee like we did in a previ-
ous section. As long as ZNC and BitlBee are running, ZNC will remain connected to
BitlBee and you can attach and detach at will. To use OTR on an actual IRC network, like
freenode, we need to attach ZNC to the other network. There are two ways to do this. We
can, as
status
reminded us, jump to that network with the following command, assum-
ing you named your freenode network
freenode
:
/msg *status JumpNetwork freenode
This will take your existing session and
jump
it over to freenode. While you may be in the
same client window, you are now talking on a different IRC network since we switched
from BitlBee to freenode. If you use GNU screen or tmux, we just performed a similar ac-
tion as we would have had we switched to a new screen. The session is still running; we
are just looking at a different instance. This method has the benefit of only using one con-
nection from your client to ZNC, but it can be a bit confusing.
Alternatively, you can open another ZNC connection. To indicate to ZNC that you want
the new session to attach to a different network, you must use a different syntax. Your
username must be in the form
username/network
and if you were sending the user-
name in the password field, as you must with ERC, the format is
username/net-
work:password
. So, in this example the username is:
zncbeagle/freenode
Using either method, connect to freenode via IRC.
