You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.
Some of this stuff is needed for other features, so here goes:
Base Extensions
Capability Negotiation
multi-prefix Extension
sasl Extension
Optional Extensions
account-notify Extension
away-notify Extension
extended-join Extension
tls Extension
There is already the beginnings of CAP in there (to add SASL support), but it needs fleshed out into a proper system rather than a hack to get one feature working. Obviously SASL is also implemented, but will need tweaked a little when CAP support gets changed.
multi-prefix is the only other base extension, and it's very useful anyway. extended-join and account-notify are the two main optionals that we need, but away-notify would allow us to extend our API for IRC users, and perhaps let us consider a generic away/inactivity API (Mumble has an idle timer, we can implement client-side inactivity for servers/protocols without support, but this is a different discussion).
I see no use for tls given that we support specifying SSL in the config already.
There is nothing in IRCv3.2 that we especially need right now, so it can go in a future ticket.
Some of this stuff is needed for other features, so here goes:
Base Extensions
multi-prefix
Extensionsasl
ExtensionOptional Extensions
account-notify
Extensionaway-notify
Extensionextended-join
Extensiontls
ExtensionThere is already the beginnings of
CAP
in there (to add SASL support), but it needs fleshed out into a proper system rather than a hack to get one feature working. Obviously SASL is also implemented, but will need tweaked a little whenCAP
support gets changed.multi-prefix
is the only other base extension, and it's very useful anyway.extended-join
andaccount-notify
are the two main optionals that we need, butaway-notify
would allow us to extend our API for IRC users, and perhaps let us consider a generic away/inactivity API (Mumble has an idle timer, we can implement client-side inactivity for servers/protocols without support, but this is a different discussion).I see no use for
tls
given that we support specifying SSL in the config already.There is nothing in IRCv3.2 that we especially need right now, so it can go in a future ticket.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: