mirror of
https://github.com/Mikaela/Limnoria.git
synced 2024-11-20 01:19:26 +01:00
src/conf.py: disable strictRFC by default
strictRFC causes issues when nicks start with numbers and on some network this happens too often. For example, if nick isn't RFC-compliant, the bot cannot be used to kick user from channel. Ops cannot change this so they must op themselves and kick the user by themselves or whatever they are going to do. Some IRCds also allow you to change your nick to your UID using `/nick 0` and on others it happens when there is nick collision after netsplit.
This commit is contained in:
parent
0d4f7c655d
commit
9816c8cccb
10
src/conf.py
10
src/conf.py
@ -1059,11 +1059,11 @@ registerChannelValue(supybot.protocols.irc, 'banmask',
|
|||||||
default banmask style.""")))
|
default banmask style.""")))
|
||||||
|
|
||||||
registerGlobalValue(supybot.protocols.irc, 'strictRfc',
|
registerGlobalValue(supybot.protocols.irc, 'strictRfc',
|
||||||
registry.Boolean(True, _("""Determines whether the bot will strictly follow
|
registry.Boolean(False, _("""Determines whether the bot will strictly
|
||||||
the RFC; currently this only affects what strings are considered to be
|
follow the RFC; currently this only affects what strings are
|
||||||
nicks. If you're using a server or a network that requires you to message
|
considered to be nicks. If you're using a server or a network that
|
||||||
a nick such as services@this.network.server then you you should set this to
|
requires you to message a nick such as services@this.network.server
|
||||||
False.""")))
|
then you you should set this to False.""")))
|
||||||
|
|
||||||
registerGlobalValue(supybot.protocols.irc, 'certfile',
|
registerGlobalValue(supybot.protocols.irc, 'certfile',
|
||||||
registry.String('', _("""Determines what certificate file (if any) the bot
|
registry.String('', _("""Determines what certificate file (if any) the bot
|
||||||
|
Loading…
Reference in New Issue
Block a user