# Imgur images not rendering because server is rate limited

**URL:** https://meta.discourse.org/t/imgur-images-not-rendering-because-server-is-rate-limited/285179
**Category:** Development
**Tags:** rest-api
**Created:** [November 11, 2023, 1:55pm UTC](https://meta.discourse.org/t/imgur-images-not-rendering-because-server-is-rate-limited/285179 "2023-11-11T13:55:00Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![winston-yallow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/winston-yallow/32/339990_2.png) [@winston-yallow](https://meta.discourse.org/u/winston-yallow)
#### Post date: [November 11, 2023, 2:54pm UTC](https://meta.discourse.org/t/imgur-images-not-rendering-because-server-is-rate-limited/285179/7 "2023-11-11T14:54:23Z")

</div>

Oof, I see. This makes sense since before I ran into this, I did import 120k topics. So that must have fetched a lot of images from imgur.  
Thanks for pointing this out, I simply thought the client does all image requests!

I find it interesting that the server does these requests, I assume it is to cache them locally in case the original disappears? I will look for ways to spread the process out a bit, so that the 120k posts get build over a longer period of time to prevent the server from being blacklisted or rate limited. I mean for this server it’s not a problem, it’s just on integration. But once I do the import on prod I’d like to prevent this 😅

Continued as a new question: [How to spread out import over longer timer to prevent running into rate limits of external services](https://meta.discourse.org/t/how-to-spread-out-import-over-longer-timer-to-prevent-running-into-rate-limits-of-external-services/285186)

---

_[View the full topic](https://meta.discourse.org/t/imgur-images-not-rendering-because-server-is-rate-limited/285179)._