~steering/inspircd++.git/docs, branch v2.0.26

Improve some documentation (#1483).

2018-04-16T09:02:49Z

* Improve exemptchanops in inspircd.conf.example () 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

[2.0]: Helpop: Move extban 'U' from acting to matching

2018-02-12T01:40:23Z

Already fixed in master in 8587df2

m_chanhistory: optionally exempt bots from receiving history.

2017-12-31T10:59:02Z

Sending history to some bots can cause problems as without the IRCv3 chathistory batch they have no way of knowing what messages are history and what they should respond to. Closes #1450.

Fix two minor docs issues

2017-12-22T22:44:29Z

Use HTTPS URLs in the executable file and include examples.

2017-12-16T13:13:33Z

Clarify the documentation of .

2017-12-12T20:20:33Z

Fix referring to sqloper and sqlauth as extras in modules.conf

2017-11-15T04:15:13Z

Various minor documentation fixes.

2017-11-12T12:24:57Z

- 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.

Merge pull request #1359 from genius3000/insp20+sasl_no_server

2017-11-06T11:11:22Z

2.0: Inform the client when a SASL message cannot be sent

Inform the client when a SASL message cannot be sent

2017-11-06T02:51:22Z

When SASL is properly configured with a 'target' server, we are able to inform the client when the message fails to send. Currently if a target is configured and it is offline, no response is sent. This can cause some clients to time out while waiting for a response. If a target isn't configured, behaviour will not change with this commit. The default of '*' will still send to all servers. Updated example config with 'target' variable.