As of April 6, we have joined the Janus metanetwork. Note that this is a beta thing at the moment, and we might choose to not offer it in the future depending on how things go. Here's the information on that, contributed by stitch.
So what is “janus” anyway?
Janus is an inter-network channel linker for IRC. Networks that participate in the Janus network have the ability to “share” channels with other networks. Shared channels will appear like any other normal channel on the network.
So how does it work?
With such a setup, individual channels will have a home network. This home network is usually where the channel is registered at / founded at. All networks linked to janus will have a 2-3 letter code. When an op/operator exposes their channel to Janus, other networks can choose to link the channel to their network. For example: Bob on BobNet, with a Janus ID code of bn decides to expose #mychan to the Janus network, he would perform:
/msg Janus CREATE #mychan
And the channel will then be available within the Janus network. Sally on CowNet decides there are some cool people in Bob’s #mychan, so Sally would execute
/msg Janus LINK #mychan bn
And Sally’s CowNet will have access to #mychan from BobNet. #mychan on both networks will see all users and chat as if they were native to the network.
Do IRC operators have control over remote networks?
No, while operators on remote networks can see info about users in linked channels, they can not set K:Lines or G:Lines against remote users, kill remote users, or mess with them any other way. If an operator does kill a remote user, the killee will just automatically part the linked channels from the home network of said operator.
Are networks mandated to carry remote channels? Can home networks refuse any desired links from remote networks?
No and Yes.
I have other questions about Janus…
Send a Private Message to stitch or ask in #staticbox.