From cc4890184cc00ebc736697cbe5609c7e14bf386c Mon Sep 17 00:00:00 2001 From: James Lu Date: Mon, 31 Jul 2017 00:19:26 +0800 Subject: [PATCH] faq: be slightly less excited --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 6f7811b..373aab2 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -54,7 +54,7 @@ PyLink provides, in no particular order: ### My IRCd SQUITs the relay server with errors like "Bad nickname introduced"! -First, check whether the SQUIT message includes the nick that triggered the netsplit. If this nick includes any characters not allowed in regular IRC, such as the slash ("/"), or is otherwise an invalid nick (e.g. beginning with a hyphen or number), this likely indicates a bug in PyLink Relay. These problems should be reported on the issue tracker! +First, check whether the SQUIT message includes the nick that triggered the netsplit. If this nick includes any characters not allowed in regular IRC, such as the slash ("/"), or is otherwise an invalid nick (e.g. beginning with a hyphen or number), this likely indicates a bug in PyLink Relay. These problems should be reported on the issue tracker. However, if the nick mentioned is legal on IRC, this issue is likely caused by a max nick length misconfiguration: i.e. the relay server is introducing nicks too long for the target network. This can be fixed by setting the `maxnicklen` option in the affected network's PyLink `server:` block to the same value as that network's `005` `NICKLEN` (that is, the `NICKLEN=` value in `/raw version`).