This plugin made discord ban my IP address

[GitKactus]

Plugin worked, perhaps a little too well. I've been IP banned on discord and can only use discord from my phone through mobile data. Didn't even send any messages via pidgin. Appear to have gone up against their rate limits https://discord.com/developers/docs/topics/rate-limits

Also I was hoping for a plugin that just did private messages, instead got one that showed me mostly messages from servers I have muted.

[LurkerHub]

Same here:

You are being blocked from accessing our API temporarily due to exceeding our rate limits frequently. Please read our docs at https://discord.com/developers/docs/topics/rate-limits to prevent this moving forward.

How do I disable this behaviour?

[JenoraFeuer]

This is an issue that has been around for a while; right now the only fix seems to be to disable 'Fetch unread messages when account connects' in the Advanced tab of the configuration, though you have to do that before connecting. It seems to be that pre-fetch that gets Discord upset about going over the rate limits.

Unfortunately, especially since you seem to want to use this primarily for private messages, disabling that option means that the plugin won't fetch any private messages that have arrived while you're offline. It also disables messages tagged to you (or @everyone or any group you're a part of) in other servers, but for me the biggest issue is that it doesn't grab private messages when that option is turned off. But at least the other Pidgin capabilities work.

[alexolog]

I am getting tempbanned right and left because of that. It is ridiculous that the choice is between loss of (potentially important) messages and loss of access.

@EionRobb please please please fix it!

[legofanlovessayori]

seems like that toggle does absolutely nothing cause my pidgin just spams tabs / windows when logging in (with setting toggled to off while adding the account)

(joined a lot of servers so yeah)

is it not possible to just not open chat windows automaticly

[LurkerHub]

This is an issue that has been around for a while; right now the only fix seems to be to disable 'Fetch unread messages when account connects' in the Advanced tab of the configuration, though you have to do that before connecting. It seems to be that pre-fetch that gets Discord upset about going over the rate limits.

Unfortunately, especially since you seem to want to use this primarily for private messages, disabling that option means that the plugin won't fetch any private messages that have arrived while you're offline. It also disables messages tagged to you (or @everyone or any group you're a part of) in other servers, but for me the biggest issue is that it doesn't grab private messages when that option is turned off. But at least the other Pidgin capabilities work.

It does not work. The moment somebody tags @here or @everyone on a busy channel, regardless of that setting, BAM! temporary ban and I cannot use Discord for hours.

Does anyone have an old DLL that doesn't fetch history at all?

[Metalhead33]

This is still a problem, even as of 2024 October.

It tends to happen "from time to time", but even then, it's rather annoying. It would be great if we could do something about it, maybe avoiding the @here and @everyone mentions or something.

For some reason, this wasn't a problem at all in 2022.

[sebbu2]

The thing is that AFAIK fetch unread ignore muted status on channels, while people usuallly only want to know mentions and new PM, so it uses a lotof space/bandwidth... add to that an unstable connection, status not being kept and the same data being resent... rate limits gets reached.

[alexolog]

The correct way to fix it is to support rate limits