| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- Change any "-Line", ":Line", or "*line" to "-line" throughout
the X-line code, comments, and documentation.
- Add periods to the end of some notices.
- Correct a typo in the Q-line code comments.
- Update the filter module documentation (shun addition).
Co-authored-by: Robby <robby@chatbelgie.be>
|
|
|
|
The old method of doing this was:
1. Extremely inconsistently used. Some list modes used <banlist>
and some used their own config tag.
2. Not documented in the slightest. There was a small reference to
<maxbans> for the ban mode but nothing else.
3. In some cases conflicting with other config tags. The chanfilter
module defined a <chanfilter> tag for general config whilst also
using it for the max list settings.
The new <maxlist> tag avoids these issues entirely.
|
|
|
|
|
|
- Remove the deprecated config tag checker. This checker is neither
exhaustive nor is it particularly accurate. Instead the new docs
site will contain a page detailing the breaking changes between
releases.
- Remove the insulting <die> tags in inspircd.conf.example and add
some descriptive ones in files that it is critical for the user
to edit correctly.
- Show the message from the <die> tag so the user actually knows
what they did wrong.
|
|
The library code used by this module is licensed under a non-free
license which is incompatible with the GPLv2. Combined with the
fact that it has been superceded by better algorithms like bcrypt
I have decided to remove it.
An alternate implementation of this algorithm is provided by the
m_hash_gnutls module if people *really* need to use it.
|
|
|
|
|
|
|
|
This is useful when dealing with spambots that switch method when
they receive ERR_CANNOTSENDTOCHAN.
|
|
- Implement escapes for italic, monospace, and strikethrough.
- Use the escape codes in the example MOTDs to demonstrate their
formatting effects.
- Remove support for octal escape codes. In modern computing octal
is rarely used and is confusing for users who might confuse it
for decimal.
|
|
The options for disabling these were added to keep compatibility
with previous 2.0 releases and are not needed any more.
|
|
|
|
* Improve exemptchanops in inspircd.conf.example (<options>)
and modules.conf.example; along with both helpop examples.
* Add "the" to all "requires X module" in both helpop examples.
* Refer to customprefix instead of chanprotect and halfop.
* Add SNOMASK 'r' and 'R' (OPERLOG) to both helpop examples.
* Clean up unnecessarily split SNOMASK lines in both helpop examples.
* Move chmode 'g' to be in alphabetical order in both helpops examples.
* Specify the needed mask formats for TLINE in helpop-full example.
* Remove extra '\' in RLINE mask format in helpop-full example.
Force xml format in helpop-full
* Generalize "color codes" to "formatting codes"
* Fix file name in include for example helpop-full
|
|
Within the example configs, helpops, some server sent messages, and
simple code comments: change the primary usage of "gecos" to
"real name" (or "realname" where fitting).
|
|
Separate secret and private channels on WHOIS for all users.
- Move the config parsing from the core to core_whois.
- Replace <security:operspywhois> with an oper privilege.
- Introduce <options:splitwhois> to split WHOIS channel lists.
Closes #969.
|
|
|
|
The previous name was horrible and didn't describe what the setting
actually does.
|
|
|
|
|
|
Closes #451.
|
|
These are extremely outdated. If we want to ship these then they
should be redone from scratch.
|
|
|
|
- Remind admins that not setting a DIE/RESTART password does not
disable use of those commands.
- Remove references to 1.2 and modules being able to create custom
logging methods. This was never implemented in the 2.0 branch.
- Remove references to an SASL improvement that was reverted.
- Update various InspIRCd website links to use HTTPS over HTTP.
- Update a link to the IRCv3 website to point to the new website.
|
|
This will not cause any compatibility issues as we do not rely on
this attribute internally.
|
|
|
|
64 is a rather restrictive limit especially considering how fast
channels can accumulate bans. In fact, #InspIRCd hit the ban limit
in just over a year.
Having a low limit might have made sense when memory was expensive
but the average IRC server should be able to handle this fine now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also use the behaviour behind this to fix #1290.
|
|
Rework the example services aliases.
|
|
- Split common stuff into a generic configuration file.
- Reserve all nicknames used by services by default.
- Exempt all services clients from filtering.
- Add missing aliases for services pseudoclients.
|
|
Allow listeners to be able to listen on unavailable addresses.
|
|
|
|
|
|
|
|
Undocument <power> and set the default to the server name.
|
|
|
|
- Follow best current practises by using bcrypt almost everywhere
in the example configuration files.
- Document the existence of new hashing modules in master.
|
|
|
|
|
|
|
|
|
