connecting to irc floods irc server

[kermit]

An IRC server will boot pidgin for flooding When the number of channels to JOIN plus buddies to ISON is high enough, as pidgin sends them all in a burst.

[kermit]

This is much more of a problem with the new Freenode... I can only autojoin about 7 channels now.

[kermit]

A hack to get around this problem is to make one auto-join channel called #channel1,#channel2,#channel3 etc, and remove the individual ones, so that it's sent on one JOIN line instead of several.

[rekkanoryo]

The irc-more plugin in the Purple Plugin Pack now has a field to specify autojoin channels. Supply the channels as a comma-separated list (such as #pidgin,#pidgin-commits,...,#test). This will help the autojoin floods. That said, yes, we probably do need some sort of throttling in our IRC plugin.

[kermit]

The comma list of channels method only works for the initial connect, automatic reconnects still flood me off.

[BW~Merlin]

I have just run into this problem today, was already using the IRC plugins and even tried removing a few of the channels I don't use much. The initial login is generally ok but if you disconnect for what ever reason you can not get back in because of excess flooding (can a flood ever not in excess?).

[BW~Merlin]

I have spoken to some guys on #freenode and they say the new server software has lowered the flood limit a little and that if pidgin could include a limit on the channel join rate that should solve the issue.

[elb]

Ticket #11726 has been marked as a duplicate of this ticket.

[elb@…]

(In ​b9fd37553a90f47c560be425179d044468a21f96):
Remove periodic WHO on IRC.

I believe I have left enough functionality here that a misguided libpurple client can continue to trigger WHO from its own UI.

References #11089, #14602 Fixes #14955

[kip]

Thanks elb.

[BW~Merlin]

For me this issue is still not fixed. If I get disconnected from freenode I am unable to rejoin and have to exit pidgin completely and restart it.

[elb]

This bug is also not closed. That change referenced this ticket because it certainly will help flooding issues, but it did not fix the on-join flooding issue.

[kip]

For me, this is still a problem in Pidgin 2.10.4. I found that exiting Pidgin and restarting it did not solve it. I realized there was something more going on when I tried changing my IP address and saw the flood temporary ban message persist. After I removed some of the autojoin channels and restarted the client, it worked.

[CiaranG]

They don't even have to be autojoin channels, you simply have to /join "too many" (not many at all, perhaps 8) channels, and then temporarily lose your connection. On re-connection, you will be repeatedly booted until you close some of those channel windows.

[sthibaul]

Still an issue with pidgin 2.10. That limits the number of chans I can afford on freenode, I'm afraid I'll have to change IM client to continue working.

[elb]

Ticket #15623 has been marked as a duplicate of this ticket.

[rakotomandimby]

Pidgin 2.10.7 on Fedora 18 still have this problem too.

If someone used with Pidgin source code ever know what file to edit, maybe some volonteer could try something and submit a patch.

No? ;-)

[nodiscc]

Confirming this bug persists in pidgin 2.10.7-2+b1 in Debian. Is there ongoing work on this?

Thanks

[elb]

Ticket #15912 has been marked as a duplicate of this ticket.

[datallah]

Ticket #16256 has been marked as a duplicate of this ticket.

[itech20]

I've hit this consistently for some time now. I can confirm that the following trivial patch, adding a half second delay to every IRC channel join, has resolved it for me:

​https://gist.github.com/imcleod/77f38d11af11b2413ada

[hroncok]

This is still an issue in 2.10.11.

[reinierpost]

This is still an issue today. I'm using the current Pidgin (2.10.12) on Windows 8.1. With over 10 channels open, reconnecting fails due to excess flood.

Arguably, this is a freenode bug, as I'm not actually flooding on any channels (in fact I'm not sending any messages to them at all), but the only reason for me to install Pidgin is to use it as an IRC client for freenode, so it would be really nice if this were fixed on the Pidgin side.

[reinierpost]

Will this fix it? ​https://gist.github.com/imcleod/77f38d11af11b2413ada

[hroncok]

Yes, it does.

It makes Piding unrepsonsive for a while, but it workarounds the issue.

Build for Fedora: ​https://copr.fedorainfracloud.org/coprs/churchyard/pidgin-antiflood/

[reinierpost]

I asked on freenode, first on #pidgin (they said a patch is welcomed), then on #freenode (they said to wait 2 secs between each channel join, and that Pidgin's IRC support is never going to work well, it's full of old bugs and doesn't play nice. I'm switching from Pidgin to Hexchat as a result).

But thanks anyway! I may be using Pidgin in the future, but I'm not going to work with Pidgins compiled from source.

[elb]

Ticket #15740 has been marked as a duplicate of this ticket.

[hroncok]

This is 6 years old and only got 4 upvotes. Do people having this issue upvote this?

[vorburger]

Upvoted it... this is quite a PITA when using Pidgin on FreeNode ...

[electrofelix]

Disabling the account, closing all open channel windows and re-enabling allows me to work around it, presumably this results in a small delay occurring as pidgin re-creates the chat window for each channel autojoin.

[arximboldi]

This bug makes me sad... I love using Pidgin for chat so I can keep all my messaging in the same app.