I've noticed that when I connect to a Freenode ZNC on my phone client, I get kicked from Freenode due to an excess flood when the client is running in the background whilst joining and attaching the 22 channels.
How do I solve this? It's getting mildly irritating.
I've noticed that when I connect to a Freenode ZNC on my phone client, I get kicked from Freenode due to an excess flood when the client is running in the background whilst joining and attaching the 22 channels.
How do I solve this? It's getting mildly irritating.
##
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1441032-any-method-to-throttle-a-client-attaching-to-znc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:29562267 -->
I've noticed that when I connect to a Freenode ZNC on my phone client,
I get kicked from Freenode due to an excess flood when the client is
running in the background whilst joining and attaching the 22 channels.
How do I solve this? It's getting mildly irritating.
Upgrade, ZNC has flood protection since 1.0
17.03.2014 14:05, rymate1234 пишет:
> I've noticed that when I connect to a Freenode ZNC on my phone client,
> I get kicked from Freenode due to an excess flood when the client is
> running in the background whilst joining and attaching the 22 channels.
>
> How do I solve this? It's getting mildly irritating.
>
> —
> Reply to this email directly or view it on GitHub
> https://github.com/znc/znc/issues/511.
<!-- github-comment-id:37818706 -->
I believe this has been fixed with 1.6.0, but if it still happens the previous workaround /znc *controlpanel set maxjoins $me 5 still works or removing autojoin from the client (which you should do when you use chansaver).
I believe this has been fixed with 1.6.0, but if it still happens the previous workaround `/znc *controlpanel set maxjoins $me 5` still works or removing autojoin from the client (which you should do when you use chansaver).
<!-- github-comment-id:138906914 -->
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.
I've noticed that when I connect to a Freenode ZNC on my phone client, I get kicked from Freenode due to an excess flood when the client is running in the background whilst joining and attaching the 22 channels.
How do I solve this? It's getting mildly irritating.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1441032-any-method-to-throttle-a-client-attaching-to-znc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).Upgrade, ZNC has flood protection since 1.0
17.03.2014 14:05, rymate1234 пишет:
I believe this has been fixed with 1.6.0, but if it still happens the previous workaround
/znc *controlpanel set maxjoins $me 5still works or removing autojoin from the client (which you should do when you use chansaver).