Aminda Suomalainen ⚧

I think this was discussed somewhere and this isn't going to happen, because it's a hack fixed by https://github.com/ircv3/ircv3-specifications/issues/162.

> If I'm interpreting this correctly, automatic *sasl setup when *nickserv password is set would be nice. But how would ZNC guess the SASL username? No, only telling _This network...

> Couldn't it just be announced the first time the module (*nickserv) is loaded? No as the user might not be connected to the network at that time and network...

Naggy is the point and there is no reason to nag when sasl is loaded so it can well do it until thatm

> The SASL module could use cap-notify so that it would know when SASL is re-introduced and can re-authenticate over SASL. https://github.com/znc/znc/issues/949

I disagree as ping/pong is not activity by the user, but the client and what if there is bad connection between the client and ZNC and ZNC is receiving PINGs...

Is there even a way to match corresponding PINGs and PONGs? To me it looks like WeeChat pings with the configured server address as argument, so everything is `PING ::1`.

Has AppImage gotten support for automatic updates or would it require deleting everything and downloading a new version from riot.im every time a new release comes?

> I've only been able to observe it saving to disk when I manage channels via the webpanel. ZNC only saves everything when you `/znc saveconfig` or change the config...

> The AUTHENTICATE command MUST be used before registration is complete and with the sasl capability enabled. To enforce the former, it is RECOMMENDED to only send CAP END when...