| Age | Commit message (Collapse) | Author |
|---|
|
This was done in some places already but not consistently.
Closes #349.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Admins can now queue multiple messages and send them when they are
ready. This is fully compatible with the previous global behaviour.
Admins can now also send messages to individual servers. This is
useful for informing users of maintenance due to downtime.
|
|
|
|
|
|
|
|
I'll fix this properly in 2.1 because I don't want to make big
changes to 2.0.
Closes #384.
|
|
|
|
|
|
Closes #386.
|
|
Closes #376.
|
|
Closes #366.
|
|
|
|
InspIRCd allows us to send infinite length lines and mode changes
and will restack before sending to users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
If another module was loaded first and then later unloaded it was
possible for a deprecated module to encrypt passwords.
|
|
|
|
|
|
|
|
|
|
Closes #369.
|
|
|
|
This will be useful for doing challenge authentication on InspIRCd.
|
|
|
|
Using HMAC instead of changing the IV is a lot safer.
|
|
|
