Considering the shenanigans imgur has been pulling recently, I don't think it's likely to get any better.Yeah, for example in the funny images thread, here's my first post after the move:
https://forum.questionablequesting.com/posts/7415256/
A bunch of other images posted after that do appear to be proxied correctly.
Other people linking from imgur seem to also not get proxied (images work in reply, not in regular post).
Perhaps imgur is blocking the new host? If so then I'll find another re-hosting site. But imgur is very convenient for anonymous hosting so it would be nice if it could work.
Yeah, this is clearly the basic issue. The problem is that this started happening after the server move, and the requests should be identical before and after on the software level, since the software was just copied over. This suggests that imgur is also examining the traffic source to dispatch requests, and they won't fulfill requests from the new server specifically. (This sort of thing is a relatively common tactic for sites that want to defeat web scrapers.) Unfortunately there's not much I can actually do about this, without going to a lot of trouble to set up a proxy or something.alethiophile: Someone suggested the problem is the way that Imgur redirects direct links to images into links to the pages hosting those images - e.g. if you click on https://i.imgur.com/fSbAvaz.png, you will be automatically redirected to https://imgur.com/fSbAvaz.
Now, I can see how that redirect would mess up loading the embedded image. The question, then, becomes why do the images work when loaded in the editor. My guess would be that Imgur don't want to block hotlinking, so they look at some aspect of the incoming query to determine whether the request is an embedded image or a followed link, and only redirect it if its a link. In which case the problem is that the query issued by the image proxy looks more like a followed link than an embedded image.
So..?I'm hoping to change the setup of how we handle images after the XF2 upgrade, so as to obviate the issue.
It has nothing to do with how images are handled, imgur just refuses to work with us.
@alethiophile thought the problem could be fixed after the XF2 migration. We've been on XF2 for most of a year now. It's not unreasonable to expect an update.It has nothing to do with how images are handled, imgur just refuses to work with us.
Sure, if someone has an image and wants to upload it somewhere to share, they can just pick a host that isn't Imgur. But Imgur remains a very popular hosting site for everybody else, and not being able to post stuff that other people upload there on QQ is Really Fucking Annoying. (Yes, you can rehost and image from there to somewhere else. But that's a lot of hassle compared to 'copy image location -> paste URL into editor'.)Just switch to Imgchest already. Everyone should have done that when Imgur banned all NSFW stuff.
In addition to the imgur issues, Imgbb (which I switched to after Imgur stopped working) has now also stopped proxying images in at least some cases - do we know if this is the same underlying cause?
Is ImgBB purging NSFW images? Cause otherwise no, it's not the same cause.In addition to the imgur issues, Imgbb (which I switched to after Imgur stopped working) has now also stopped proxying images in at least some cases - do we know if this is the same underlying cause?
For instance, I just tried to post the below over in the Dark Humour image thread and it was repeatedly broken outside of replies and the Edit Post window. (I finally got it to proxy by just switching to using Imgchest instead, but who knows how long it'll be til that stops working too...)
![]()
I used the "Insert Image" option in the top bar, and pasted in the address of the actual jpg itself, https://i.ibb.co/FLhXqLF3/image.jpg. I note that opening the spoiler now, a good 9 hours later, it does display the image from imgBB properly proxied, whereas when I posted that spoiler box contained a broken-image icon; it seems like the proxy is just being very, *very* slow sometimes?Are you sure you were actually embedding it properly to begin with? Cause I've noticed that people have a tendency to try to embed the image page rather than the image itself.
it was pissing me off so much that i cant even find proper words to describe it, just use this site: https://imgchest.com/I used the "Insert Image" option in the top bar, and pasted in the address of the actual jpg itself, https://i.ibb.co/FLhXqLF3/image.jpg. I note that opening the spoiler now, a good 9 hours later, it does display the image from imgBB properly proxied, whereas when I posted that spoiler box contained a broken-image icon; it seems like the proxy is just being very, *very* slow sometimes?