CAP LS 302 is what moho sends (nobilis/src/backend/irc/connect.rs:614), and asking
for version 302 turns on cap-notify implicitly - the server is then entitled to send CAP NEW when something becomes available and CAP DEL when it goes away.
Only CAP ACK is matched (nobilis/src/backend/irc/incoming.rs:629). NEW and DEL
fall through the router and nothing happens.
So the capability set is whatever was true in the first second of the connection, for
the life of the connection. Services coming back up and offering SASL again, a network
enabling draft/chathistory, an operator turning something off - none of it is noticed.
The DEL half is the worse one: moho goes on believing it holds a capability the server
has withdrawn, and keeps using it.
HexChat, WeeChat and Halloy all act on both.
`CAP LS 302` is what moho sends (`nobilis/src/backend/irc/connect.rs:614`), and asking
for version 302 turns on `cap-notify` implicitly - the server is then entitled to send
`CAP NEW` when something becomes available and `CAP DEL` when it goes away.
Only `CAP ACK` is matched (`nobilis/src/backend/irc/incoming.rs:629`). `NEW` and `DEL`
fall through the router and nothing happens.
So the capability set is whatever was true in the first second of the connection, for
the life of the connection. Services coming back up and offering SASL again, a network
enabling `draft/chathistory`, an operator turning something off - none of it is noticed.
The `DEL` half is the worse one: moho goes on believing it holds a capability the server
has withdrawn, and keeps using it.
HexChat, WeeChat and Halloy all act on both.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
CAP LS 302is what moho sends (nobilis/src/backend/irc/connect.rs:614), and askingfor version 302 turns on
cap-notifyimplicitly - the server is then entitled to sendCAP NEWwhen something becomes available andCAP DELwhen it goes away.Only
CAP ACKis matched (nobilis/src/backend/irc/incoming.rs:629).NEWandDELfall through the router and nothing happens.
So the capability set is whatever was true in the first second of the connection, for
the life of the connection. Services coming back up and offering SASL again, a network
enabling
draft/chathistory, an operator turning something off - none of it is noticed.The
DELhalf is the worse one: moho goes on believing it holds a capability the serverhas withdrawn, and keeps using it.
HexChat, WeeChat and Halloy all act on both.
Finished — https://git.salastil.com/Salastil/nobilis/commit/e8e3c6f
Bump: https://git.salastil.com/Salastil/moho/commit/0fb0d1a