alias: %channel% with IRCv3 vendor-specific capability & fallback to channel last spoken on #566

New Issue

2026-10-05T04:30:15+02:00

adam commented

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

It is impossible for ZNC to know which channel the user is viewing, so there is no %channel% substitution. It's tough to work around this problem, but future versions may support interacting with a client side script that informs ZNC of the user's currently active channel.

I think this might be possible with IRCv3 vendor specification, such as znc.in/current-channel.

http://ircv3.net/specs/core/capability-negotiation-3.1.html#vendor-specific

Then either clients would start supporting it or support would be added with script and znc was always told what channel the client is looking at. It might require using the @id to separate clients from each other.

Vendor-Specific capabilities should be submitted to the IRCv3 working group for consideration.

I don't think anyone else would benefit from this except maybe other bouncers or if IRCds (InspIRCd with some modules and it's aliases?) started having server-side qop/sop/hop/remove etc. commands.

I am afraid I don't have skills even for writing any kind of specification, but this is just an idea which might work.

Update on 2015-09-22: As it would take time from clients (or client scripts) to start supporting the capability (if ever) I believe having %channel% fallback to the channel where the user last sent PRIVMSG/NOTICE (including STATUSMG) would be a reasonable fallback.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

> It is impossible for ZNC to know which channel the user is viewing, so there is no %channel% substitution. It's tough to work around this problem, but future versions may support interacting with a client side script that informs ZNC of the user's currently active channel. I think this might be possible with IRCv3 vendor specification, such as `znc.in/current-channel`. - http://ircv3.net/specs/core/capability-negotiation-3.1.html#vendor-specific Then either clients would start supporting it or support would be added with script and znc was always told what channel the client is looking at. It might require using the `@id` to separate clients from each other. > Vendor-Specific capabilities should be submitted to the IRCv3 working group for consideration. I don't think anyone else would benefit from this except maybe other bouncers or if IRCds (InspIRCd with some modules and it's aliases?) started having server-side qop/sop/hop/remove etc. commands. _I am afraid I don't have skills even for writing any kind of specification, but this is just an idea which might work._ --- Update on 2015-09-22: As it would take time from clients (or client scripts) to start supporting the capability (if ever) I believe having %channel% fallback to the channel where the user last sent PRIVMSG/NOTICE (including STATUSMG) would be a reasonable fallback. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26483898-alias-channel-with-ircv3-vendor-specific-capability-fallback-to-channel-last-spoken-on?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:30:16 +02:00

I asked if it would have any kind of future if sent to IRCv3 and the answer was "maybe", so maybe if something happens with this it should be sent there for review anyway.

I asked if it would have any kind of future if sent to IRCv3 and the answer was "maybe", so maybe if something happens with this it should be sent there for review anyway.

adam commented

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

This shuld probably be asked on issue tracker: would it be possible for ZNC to assume that %channel% means the channel where I last sent PRIVMSG and mention that in the wiki as limitation?

Even so small change would help at least with my aliases and I think it could help with aliases of many other people too.

This shuld probably be asked on issue tracker: would it be possible for ZNC to assume that %channel% means the channel where I last sent PRIVMSG and mention that in the wiki as limitation? Even so small change would help at least with my aliases and I think it could help with aliases of many other people too.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#566