pidgin-telegram-1.4.7 failure to connect: RPC_CALL_FAIL 420: FLOOD_WAIT_333

[UnixRonin]

x11-plugins/pidgin-telegram-1.4.7 in net-im/pidgin-2.14.8 is currently failing to connect, giving the following error:

RPC_CALL_FAIL 420: FLOOD_WAIT_333

Is this a known problem related to a Telegram protocol change?

[blacklight]

I can confirm the issue - I have been experiencing it on my bitlbee instances since yesterday.

[cstruck]

+1

[webmeister]

See #575 (comment) for a possible workaround to restore (limited) functionality.

[Monsterovich]

Deleting the state file hasn't resolved the issue permanently.

[blacklight]

Goodbye, Telegram.

Just a few days ago they forced developers to show ads in their bots and channels. Now, this. It can't be a coincidence.

If these guys want to force me to use their official client, I'll just move on to another app.

I can go through the effort of reverse engineering and hacking libpurple for e.g. Messenger and WhatsApp, because all of my friends use them. But Telegram...? I can abandon it today, and I won't lose the ability to reach out to my contacts.

If they have joined the club of apps that are all like "you need to watch our ads, you need to use our client, you need to give us the ability to track your behaviour on the platform", then I'm out. The world is full of such shitty messaging apps, we don't need another one of them.

At the very least, I'd expect some apologies from the Telegram developers for breaking a whole layer of integrations with no notice at all.

[UnixRonin]

It appears the issue here is that Telegram has decided to block all "old" clients. This includes anything using tdlib < 1.7.0.

[UnixRonin]

This problem self-resolved after a couple of days. However, in the future, telegram-purple may become unsupported unless updated to use tdlib 1.7.0 or higher.

[bodqhrohro]

telegram-purple may become unsupported unless updated to use tdlib 1.7.0 or higher.

telegram-purple does not use TDlib, and never would. The TDlib-specific restrictions are not applicable to it. The MTProto layer ones may though.

And also, after the December 1 breakage, 1.7.0 didn't work too, the minimum required version was 1.7.9 from git, which wasn't even released at the time, and that caused a major frustration among developers.