From 2a18d07a2e028a22f555c98f2d20830cf035d7bd Mon Sep 17 00:00:00 2001 From: James Vega Date: Wed, 18 Nov 2009 20:02:53 -0500 Subject: [PATCH] Default to strict RFC compliance. It's better to force people to use an RFC nick and change it after they connect than to let non-RFC nicks get used and not be able to connect to the network. Signed-off-by: James Vega (cherry picked from commit 07e283f4502db87cac55217f4567ad4feb418d44) --- src/conf.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/conf.py b/src/conf.py index 1e620e858..b00b495c4 100644 --- a/src/conf.py +++ b/src/conf.py @@ -953,7 +953,7 @@ registerChannelValue(supybot.protocols.irc, 'banmask', default banmask style.""")) registerGlobalValue(supybot.protocols.irc, 'strictRfc', - registry.Boolean(False, """Determines whether the bot will strictly follow + registry.Boolean(True, """Determines whether the bot will strictly follow the RFC; currently this only affects what strings are considered to be nicks. If you're using a server or a network that requires you to message a nick such as services@this.network.server then you you should set this to