Add support for cap account-tag #366

New Issue

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

adam commented

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

https://github.com/ircv3/ircv3-specifications/blob/master/extensions/account-tag-3.2.md

Possibly related: #316 .

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

https://github.com/ircv3/ircv3-specifications/blob/master/extensions/account-tag-3.2.md Possibly related: #316 . ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3362794-add-support-for-cap-account-tag?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 closed this issue

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

adam commented

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

#315 is also related.

The issue blocking this is those related is that there is as of yet no support for https://github.com/ircv3/ircv3-specifications/blob/master/extensions/cap-notify-3.2.md in any(?) ircd. As a result znc can only blindly offer these capabilities to clients as they connect, even if the server they're connected to doesn't offer them.

#315 is also related. The issue blocking this is those related is that there is as of yet no support for https://github.com/ircv3/ircv3-specifications/blob/master/extensions/cap-notify-3.2.md in any(?) ircd. As a result znc can only blindly offer these capabilities to clients as they connect, even if the server they're connected to doesn't offer them.

adam commented

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

#603 also has same issue if you ask me, but it might not even need support outside ZNC and client though.

#603 also has same issue if you ask me, but it might not even need support outside ZNC and client though.

adam commented

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

Ideally #603 would be replaced with something cap-notify aware or be a part of ZNC itself, but at the moment it's different in that it's useful already between the client and ZNC. (Assuming you have a client that asks for it)

Ideally #603 would be replaced with something cap-notify aware or be a part of ZNC itself, but at the moment it's different in that it's useful already between the client and ZNC. (Assuming you have a client that asks for it)

adam commented

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

Assuming that working PRIVMSG means working self-message, my client asks for it and works with it.

WeeChat doesn't ask any capabilities by default and if user needs them, they must configure them by hand. Either /set irc.server_default.capabilities znc.in/server-time-iso,self-message or /set irc.server.<network>.capabilities znc.in/server-time-iso,self-message.

2014-07-28 21:54:13+0300 Option "irc.server_default.capabilities":
2014-07-28 21:54:13+0300   description: comma-separated list of client capabilities to enable for server if they are available; capabilities supported by WeeChat are: multi-prefix, userhost-in-names, away-notify (example: "multi-prefix,userhost-in-names,away-notify")
2014-07-28 21:54:13+0300   type: string
2014-07-28 21:54:13+0300   values: any string
2014-07-28 21:54:13+0300   default value: ""
2014-07-28 21:54:13+0300   current value: "multi-prefix,userhost-in-names,znc.in/server-time-iso,away-notify,self-message"

(This should probably have gone to #603, shouldn't this?)

Assuming that working PRIVMSG means working self-message, my client asks for it and works with it. WeeChat doesn't ask any capabilities by default and if user needs them, they must configure them by hand. Either `/set irc.server_default.capabilities znc.in/server-time-iso,self-message` or `/set irc.server.<network>.capabilities znc.in/server-time-iso,self-message`. ``` 2014-07-28 21:54:13+0300 Option "irc.server_default.capabilities": 2014-07-28 21:54:13+0300 description: comma-separated list of client capabilities to enable for server if they are available; capabilities supported by WeeChat are: multi-prefix, userhost-in-names, away-notify (example: "multi-prefix,userhost-in-names,away-notify") 2014-07-28 21:54:13+0300 type: string 2014-07-28 21:54:13+0300 values: any string 2014-07-28 21:54:13+0300 default value: "" 2014-07-28 21:54:13+0300 current value: "multi-prefix,userhost-in-names,znc.in/server-time-iso,away-notify,self-message" ``` (This should probably have gone to #603, shouldn't this?)

adam commented

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

How is cap-notify today? Charybdis 3.5test1 supports it and it's important part of IRCv3.2 and SASL REAUTH. IRCv3.2 is aiming to be released until end of this month.

How is cap-notify today? Charybdis 3.5test1 supports it and it's important part of IRCv3.2 and SASL REAUTH. IRCv3.2 is aiming to be released until end of this month.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#366