invite-notify is ratified and unrequested. moho handles an INVITE addressed to
itself (backend/irc/incoming.rs:584) but sees nothing when somebody else is invited
to a channel it is in — which is the case the capability exists for, and which every
other protocol here reports.
What is needed
Request invite-notify and handle the resulting INVITE lines as a room event,
the way join and part already are.
Filed as a room event, not a mention — see the reasoning in #144's fix: a line about
somebody is not a line addressed to them.
Done looks like: somebody inviting a third person to the channel is visible.
Found by the 2026-09-10 coverage review, which measured IRC against the IRCv3
capability registry rather than against a feature list. moho requests 12 capabilities
plus SASL, covering 15 of the 25 client-relevant ratified extensions — WeeChat
supports around 35. This is one of the ten missing ones, filed separately because each
is independently doable.
`invite-notify` is ratified and unrequested. moho handles an `INVITE` addressed to
itself (`backend/irc/incoming.rs:584`) but sees nothing when somebody else is invited
to a channel it is in — which is the case the capability exists for, and which every
other protocol here reports.
**What is needed**
- Request `invite-notify` and handle the resulting `INVITE` lines as a room event,
the way join and part already are.
- Filed as a room event, not a mention — see the reasoning in #144's fix: a line about
somebody is not a line addressed to them.
**Done looks like:** somebody inviting a third person to the channel is visible.
Found by the 2026-09-10 coverage review, which measured IRC against the IRCv3
capability registry rather than against a feature list. moho requests 12 capabilities
plus SASL, covering **15 of the 25 client-relevant ratified extensions** — WeeChat
supports around 35. This is one of the ten missing ones, filed separately because each
is independently doable.
Done in nobilis de0ad86, with the client half in moho 4fd3bc6.
invite-notify is requested and granted on Libera. An invite addressed to you still goes to the server tab; one addressed to somebody else goes to the channel it is about, because that is news about a room you are in.
Filed as a room event rather than a mention, following the rule from the closing-client bug: a line written about somebody is not a line addressed to them.
Done in nobilis [de0ad86](https://git.salastil.com/Salastil/nobilis/commit/de0ad86), with the client half in moho [4fd3bc6](https://git.salastil.com/Salastil/moho/commit/4fd3bc6).
`invite-notify` is requested and granted on Libera. An invite addressed to you still goes to the server tab; one addressed to somebody else goes to the channel it is about, because that is news about a room you are in.
Filed as a room event rather than a mention, following the rule from the closing-client bug: a line written *about* somebody is not a line addressed to them.
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.
invite-notifyis ratified and unrequested. moho handles anINVITEaddressed toitself (
backend/irc/incoming.rs:584) but sees nothing when somebody else is invitedto a channel it is in — which is the case the capability exists for, and which every
other protocol here reports.
What is needed
invite-notifyand handle the resultingINVITElines as a room event,the way join and part already are.
somebody is not a line addressed to them.
Done looks like: somebody inviting a third person to the channel is visible.
Found by the 2026-09-10 coverage review, which measured IRC against the IRCv3
capability registry rather than against a feature list. moho requests 12 capabilities
plus SASL, covering 15 of the 25 client-relevant ratified extensions — WeeChat
supports around 35. This is one of the ten missing ones, filed separately because each
is independently doable.
Done in nobilis de0ad86, with the client half in moho 4fd3bc6.
invite-notifyis requested and granted on Libera. An invite addressed to you still goes to the server tab; one addressed to somebody else goes to the channel it is about, because that is news about a room you are in.Filed as a room event rather than a mention, following the rule from the closing-client bug: a line written about somebody is not a line addressed to them.