Multiple networks on the same client-ZNC connection #311

New Issue

2026-10-05T04:12:25+02:00

adam commented

2026-10-05 04:12:25 +02:00

Currently, you have to connect to ZNC once per network you want to join. It would be cool if it were possible to create a meta-network, so you could connect to ZNC just once, and then you specify the server in the channel name. EG:

/join #freenode/znc     -> joins #znc on Freenode
/join #mozilla/rust     -> joins #rust on Mozilla
/join #freenode/znc/foo -> joins #znc/foo on Freenode

One case I’m not sure of is ## channels, like ##hott on Freenode. Would it be ##freenode/hott or #freenode/#hott?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1442877-multiple-networks-on-the-same-client-znc-connection?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Currently, you have to connect to ZNC once per network you want to join. It would be cool if it were possible to create a meta-network, so you could connect to ZNC just once, and then you specify the server in the channel name. EG: ``` /join #freenode/znc -> joins #znc on Freenode /join #mozilla/rust -> joins #rust on Mozilla /join #freenode/znc/foo -> joins #znc/foo on Freenode ``` One case I’m not sure of is `##` channels, like `##hott` on Freenode. Would it be `##freenode/hott` or `#freenode/#hott`? ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1442877-multiple-networks-on-the-same-client-znc-connection?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:12:26 +02:00

This would require to use the same irc connection for multiple networks. Neither ZNC or the IRC Protocol are designed to do that. Although its possible, it would break almost all network-specific features.

This would require to use the same irc connection for multiple networks. Neither ZNC or the IRC Protocol are designed to do that. Although its possible, it would break almost all network-specific features.

adam commented

2026-10-05 04:12:27 +02:00

@donaukind I don’t think that’s true. ZNC would still make one connection per network, but the client would make only one connection to the network that is my ZNC server. And my ZNC network just happens to have channels with names like #freenode/znc. I don’t see any reason why the ZNC server couldn’t split requests from a single client connection to different network connections.

@donaukind I don’t think that’s true. ZNC would still make one connection per network, but the client would make only one connection to the network that is my ZNC server. And my ZNC network just happens to have channels with names like #freenode/znc. I don’t see any reason why the ZNC server couldn’t split requests from a single client connection to different network connections.

adam commented

2026-10-05 04:12:28 +02:00

See http://sourceforge.net/p/znc/feature-requests/19/#e087

See http://sourceforge.net/p/znc/feature-requests/19/#e087

adam commented

2026-10-05 04:12:28 +02:00

This may be done (and even is planned), but certainly not in this way.
What we may do, is to extend IRC protocol to handle multiple networks in the same connection. But client of course needs to understand such protocol extension.

This may be done (and even is planned), but certainly not in this way. What we may do, is to extend IRC protocol to handle multiple networks in the same connection. But client of course needs to understand such protocol extension.

adam commented

2026-10-05 04:12:29 +02:00

And it will be up to client how exactly to show several networks. Either separate windows, or such prefixes you described, or ….

And it will be up to client how exactly to show several networks. Either separate windows, or such prefixes you described, or ….

adam commented

2026-10-05 04:12:30 +02:00

@donaukind I think the anonymous comment there addresses those issues (http://sourceforge.net/p/znc/feature-requests/19/#67cc).

@DarthGandalf Cool. Sounds good to me.

@donaukind I think the anonymous comment there addresses those issues (http://sourceforge.net/p/znc/feature-requests/19/#67cc). @DarthGandalf Cool. Sounds good to me.

adam commented

2026-10-05 04:12:30 +02:00

I'd rather have #freenode/#chan and then #freenode/##chan, that will also support stuff like #othernet/&chan.
I didn't read through the SF issue, just wanted to throw it in in case it wasn't mentioned there.

I'd rather have #freenode/#chan and then #freenode/##chan, that will also support stuff like #othernet/&chan. I didn't read through the SF issue, just wanted to throw it in in case it wasn't mentioned there.

adam commented

2026-10-05 04:12:31 +02:00

I'd rather have #freenode/#chan and then #freenode/##chan, that will
also support stuff like #othernet/&chan.

Both will not happen, see above.

> I'd rather have #freenode/#chan and then #freenode/##chan, that will > also support stuff like #othernet/&chan. Both will not happen, see above.

adam commented

2026-10-05 04:12:32 +02:00

Ugh, yeah, somehow missed this

And it will be up to client how exactly to show several networks. Either separate windows, or such prefixes you described, or ….

Ugh, yeah, somehow missed this > And it will be up to client how exactly to show several networks. Either separate windows, or such prefixes you described, or ….

adam commented

2026-10-05 04:12:32 +02:00

Has anyone ever submitten this to IRCv3?

Has anyone ever submitten this to IRCv3?

adam commented

2026-10-05 04:12:33 +02:00

https://github.com/ircv3/ircv3-specifications/pull/92

https://github.com/ircv3/ircv3-specifications/pull/92

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#311