James Lu 734db841f1 clientbot: track failed KICKs with /NAMES & a timer ... Suggested by @cooper. This tracking system solves the problem of failed relay kicks causing channel desyncs, because what's seen as a successful KICK when PyLink is linked as a service might not forward successfully on clientbot network. This can be caused due to the clientbot not being opped, the target being immune or having higher access than the clientbot, etc. When a NAMES reply (delayed in this case) is received for any channel where an initial /WHO has already been received, a JOIN hook will be sent for any users on the kick queue to rejoin them on the relay.		2016-07-22 22:36:34 -07:00
..
__init__.py	Make plugins/ and protocols/ namespaces	2016-07-20 23:55:26 -07:00
clientbot.py	clientbot: track failed KICKs with /NAMES & a timer	2016-07-22 22:36:34 -07:00
hybrid.py	New import paths for properly installed pylinkirc	2016-06-20 18:18:54 -07:00
inspircd.py	classes: Move ISUPPORT-style PREFIX and capabilities handling to Protocol	2016-07-20 23:59:22 -07:00
ircs2s_common.py	Fix SQUIT handling from 2f1a338	2016-07-20 23:55:34 -07:00
nefarious.py	nefarious: add (untested) SVSNICK handler based on P10 docs	2016-07-12 21:58:08 -07:00
ts6_common.py	protocols: rename _getOutgoingNick() -> _expandPUID()	2016-07-20 23:55:34 -07:00
ts6.py	ts6: add RSFNC to supported caps	2016-07-11 23:29:44 -07:00
unreal.py	protocols: rename _getOutgoingNick() -> _expandPUID()	2016-07-20 23:55:34 -07:00