| Age | Commit message (Collapse) | Author |
|---|
|
We don't send this yet because its not ergonomic to do so with
the current API. Bleh.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There might be more than this so its better to just store it in a
1+ parameter vector.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #431.
|
|
|
|
Extended bans are stored without their prefix. Therefore, we should
not try to strip their prefix before matching.
Closes #288.
Co-authored-by: k4be <k4be@pirc.pl>
|
|
|
|
|
|
At some point UnrealIRCd made an undocumented change to the protocol
where the last parameter on a server-source message would not be a
timestamp. This behaviour is preserved for MODE.
|
|
|
|
|
|
Closes #406.
|
|
|
|
|
|
|
|
|
|
|
|
Oversight from commit 04e1a4f5c8c4172ca36dd79dfd0731f4aba873a5.
|
|
|
|
|
|
|
|
|
|
Having these throw is terrible for ergonomics and there are loads
of places where the exception was either silently ignored or not
handled at all. Having a function which returns an optional and
another that returns a default works a lot better imo.
|
|
|
|
This was added for (and is only used for) for unbanning users on
UnrealIRCd which is an IRCd protocol function so it should be in
IRCDProto.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
