This not exactly correct. PC is effectively using Imgur as a CDN and that's why the site has been blacklisted. If it had only been a few images I doubt the blacklist would've been enforced but as it stands multiple themes use Imgur for quite a lot of images.Apparently Imgur has recently blacklisted us from using image hotlinks unfortunately. There is no real solution to this as it is completely out of our control. I'd recommend using another site for uploading images.
This not exactly correct. PC is effectively using Imgur as a CDN and that's why the site has been blacklisted. If it had only been a few images I doubt the blacklist would've been enforced but as it stands multiple themes use Imgur for quite a lot of images.
There's a few oversights which allowed this to happen; I was intent on serving stuff like icons to PC, so I guess I've been forced to do it now, haha.That's really... very poor design decisions when there's more controllable choices. Even 2000's web programming teaches, if you are serving "editorial line" along with your central functionality (company logos, themes, interface icons for example) then you deliver those yourself or via the CDN to which your hosting is already suscribed, not via a general use site.
Would a good first measure be to first fix the PC themes to serve from PC or Cloudflare and stuff and then get to talk to imgur? Showing a first gesture of work as an opening move kind of thing.
curl "https://i.imgur.com/fpXE2BJ.gif" -H "Referer: https://www.pokecommunity.com/showthread.php?p=9896065" -i
HTTP/2 403
retry-after: 0
content-type:
accept-ranges: bytes
date: Sun, 01 Jul 2018 02:53:09 GMT
x-served-by: cache-lax8624-LAX
x-cache: MISS
x-cache-hits: 0
x-timer: S1530413589.190726,VS0,VE0
access-control-allow-methods: GET, OPTIONS
access-control-allow-origin: *
server: cat factory 1.0
content-length: 0
curl "https://i.imgur.com/fpXE2BJ.gif" -i
HTTP/2 200
last-modified: Tue, 20 Feb 2018 18:46:48 GMT
etag: "7872661ad1b19794f9191f46c2d1d8e6"
x-amz-storage-class: STANDARD_IA
content-type: image/gif
cache-control: public, max-age=31536000
accept-ranges: bytes
date: Sun, 01 Jul 2018 02:55:15 GMT
age: 192
x-served-by: cache-iad2137-IAD, cache-lax8625-LAX
x-cache: MISS, HIT
x-cache-hits: 0, 1
x-timer: S1530413716.778418,VS0,VE1
access-control-allow-methods: GET, OPTIONS
access-control-allow-origin: *
server: cat factory 1.0
content-length: 245448
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --no-referrers
So it looks like it blocks purely based on the Referrer field of the html header. Which browsers automatically put when embedding images onto a page.
--- snip---
Last I heard, the admins have reached out to imgur and are awaiting a response from them.On Topic: Any news? Is there still hope the admins might fix this issue with imgur?
Pretty sure it's been remedied.
yep it's all fixed