Discord Badge has rate limit error about shields HOT 13 OPEN

As far as #9862 is concerned, the last I heard from our point of contact at Discord was that he was working on identifying the team owning the rate limiting capabilities internally. However, it's been a while since I last heard from him, I've followed up linking to this new issue. Will keep you posted when I get his response.

from shields.

I've sent another follow up mail. I received one out of office automated response, and one response saying they'll escalate tomorrow. Fingers crossed 🤞🏻

from shields.

As a workaround ive made a little PHP script that uses the custom shields badge text in conjunction with Discord widget API to make the same behaviour. (You have to host it yourself)

Use this as:
http://yourwebsite.com/badge.php?id=yourserverid

Heres a working example:

Heres the code:
https://gist.github.com/TriForceX/a8332709718851ea1bf0cad15f3a2600

PS: Ive used get method to allow more ids to be added, but it can be modified.

from shields.

Same here in all my README

from shields.

Badge tested using npm run badge https://img.shields.io/discord/752506676719910963.svg?style=flat&color=informational&logo=discord&label=Discord
Output is available here

from shields.

We've been occasionally hitting the discord rate limits for some time. We've been tracking this in #9862 but it has been quite a limited issue

However, in the last few days we seem to have had a huge increase in the number of 429 calling https://discord.com errors:

As far as I can see from the metrics we haven't had a huge increase in the number of badges being requested so I think something has changed upstream. Maybe the rate limit on our token has been massively decreased. @PyvesB - is the token attached to your account? Do you have any visibility on this?

from shields.

However, it's been a while since I last heard from him, I've followed up linking to this new issue. Will keep you posted when I get his response.

Thanks a lot for your effort.

from shields.

Hope this will be resolved! :)

from shields.

We are also seeing this issue with our Discord badges at Ultralytics and it would be great to have a resolution to this, otherwise we'll have to find a replacement badge to use in our repos and docs pages.

from shields.

We observe the same problem with our Restate repositories.

from shields.

Also seeing this issue with SteamGridDB repositories, the badge has been in a non working state continuously as far as I can tell.

from shields.

People might want to check out NoPlusOne from go wiki. (Of course, The project admins will delete such comments as a matter of procedure (please don’t be offended if we delete yours). won't apply as this is not go project and I don't have the permission necessary to do it on this repo)

from shields.

We are already aware this is affecting 100% of users.

I've locked this issue due the "plus 1" comments. I think that this stage allowing anyone to comment on this issue is unhelpful.

Please feel free to subscribe to the issue for updates. We will continue to update once we know something.

from shields.