Age | Commit message (Collapse) | Author |
|
There is no reason to do this.
|
|
|
|
Fixes #1626.
|
|
This should fix #1621.
|
|
|
|
This causes inconsistent message ids between servers.
This reverts commit 638e4bb417ebcd4f0a384ac19585620b0fde1569.
|
|
|
|
The legacy method of enabling these extensions is just a wrapper
around the capability. If the cap module is not loaded it can not
be enabled so we should not advertise it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also fixes accidentally copying incoming tags on TAGMSG when sending to
other users
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This makes debugging issues easier.
|
|
|
|
|
|
This is essentially identical to the one for the start event.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #1055.
|
|
|
|
|
|
Also, default TAGMSG to being worth 0.2 NOTICE/PRIVMSG. This should
prevent flood kicks from typing notifications.
Closes #1649.
|
|
|
|
99% of cases of this are due to misconfigurations not due to
underhanded behaviour.
|
|
|