James Lu e76d31d14e relay: fixes to KICK handling, don't allow spawning new pseudoclients for trivial tasks like TOPIC or PART ... This introduces a new spawnIfMissing option in getRemoteUser, which defaults to True and toggles spawning new pseudoclients if one is not found for a certain network. In the case of TOPIC or PART being sent, we'll want this turned off because we can either 1) route these through our PyLink server SID, or 2) ignore these entirely. For KICK handling, this commit fixes kicks sent from servers or clients that don't have a pseudoclient on the target network, by tagging them in the message and routing them through our main PyLink SID. Normal kicks still behave as usual: * You have been kicked from #endlessvoid by GLo|o|/ovd (test) * You have been kicked from #endlessvoid by pylink-devel.overdrive.pw ((ChanServ/ovd) (GLo|o| (GLolol)) test) * You have been kicked from #endlessvoid by pylink-devel.overdrive.pw ((some.server.name/ovd) No reason given)		2015-07-19 23:49:50 -07:00
..
admin.py	Log command usage, 'exec' usage, successful logins, and access denied to commands in admin.py	2015-07-19 15:01:49 -07:00
commands.py	Log command usage, 'exec' usage, successful logins, and access denied to commands in admin.py	2015-07-19 15:01:49 -07:00
hooks.py	everything: Improve logging	2015-07-05 13:44:48 -07:00
relay.py	relay: fixes to KICK handling, don't allow spawning new pseudoclients for trivial tasks like TOPIC or PART	2015-07-19 23:49:50 -07:00