Strategies to Overcome High Request Blocks on Imgur

[pfaffman (Jay Pfaffman)]

Maybe a watched word to just disallow imgur images and/or some othe campain to train people to just drag and drop the images straight to Discourse?

@piffy

Since moving to Discourse almost 2 years ago it seems that most of the images are still undownloaded and are being hosted by Imgur (despite having the setting to download remote images checked )

Are they displaying properly? Maybe you don’t care?

@piffy

Any tips on how to work around this limit?

I think the thing you might do would be to have some proxy that made the imgur request from some other IP. It’s perhaps slighly shady, and likely against their terms of service.

Oh! But wait. Maybe a plugin that used the API would solve your problem.

Imgur API

curl --location -g 'https://api.imgur.com/3/image/{{imageHash}}' \
--header 'Authorization: Client-ID {{clientId}}'

Imgur API.

The Imgur API uses a credit allocation system to ensure fair distribution of capacity. Each application can allow approximately 1,250 uploads per day or approximately 12,500 requests per day . If the daily limit is hit five times in a month, then the app will be blocked for the rest of the month. The remaining credit limit will be shown with each requests response in the X-RateLimit-ClientRemaining HTTP header.

I think a plugin could do that. I think the code in question is in lib/file_helper.rb starting with def self.download. Or maybe make another job like pull_hotlinked_images that processed only imgur files and didn’t bother with overriding anything. Maybe once your backlog got processed you’d not get hit by rate limits on new posts.

It seems improbable that it would get moved to core, but I don’t make such decisions so don’t blame me or team if I’m wrong.