ZNC 1.0's *q module doesn't wait until the Challenge Auth with Quakenet is complete before joining channels! It joins the channels, then acquires authentication (because challenge auth does take up to a few seconds to complete), and only then it can set usermode +x.
The effect is the user joining all his channels with his real host, then quits and instantly rejoins with the cloaked host.
As a workaround I disabled challenge authentication for the time being. (/msg *q set UseChallenge false)
ZNC 1.0's *q module doesn't wait until the Challenge Auth with Quakenet is complete before joining channels! It joins the channels, then acquires authentication (because challenge auth does take up to a few seconds to complete), and only then it can set usermode +x.
The effect is the user joining all his channels with his real host, then quits and instantly rejoins with the cloaked host.
As a workaround I disabled challenge authentication for the time being. (/msg *q set UseChallenge false)
<!-- github-sync-id:9964792 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ZNC 1.0's *q module doesn't wait until the Challenge Auth with Quakenet is complete before joining channels! It joins the channels, then acquires authentication (because challenge auth does take up to a few seconds to complete), and only then it can set usermode +x.
The effect is the user joining all his channels with his real host, then quits and instantly rejoins with the cloaked host.
As a workaround I disabled challenge authentication for the time being. (/msg *q set UseChallenge false)
+1 on that.
bump would be nice if someone could implement this