Topic: Ironic if this image don't load to show image proxy sucks? (Read 872 times)
There's no reason to force readers to download huge images when they load the page. If high resolution is really necessary, you can include a link to the image.
It's too big. The limit is 2.5 MB
That sucks... Well, not much to do about it I suppose. Why did you choose for 2.5MB by the way? Good quality pictures are almost bigger than that and are slowly get bigger all the time. 
I don't know what's a forum-proxy issue and what's an initial-host issue, but those images are stored on our server which currently only has a 1Mb upload connection. We're looking to improve that in the near future.
Browsers nowadays like to make as many simultaneous requests for images as there are images on the page (this is stupid IMO). So all of your images are downloaded at once via the proxy, but your connection isn't fast enough to deliver everything before the proxy times out after a few seconds. Not being able to serve this much data quickly enough is understandable, but it still causes issues. The problem is that browsers can wait forever for servers to respond, so they're fine with issuing even hundreds of connections at a time, but the forum's server cannot wait. Each proxy connection takes up resources, so it must complete quickly. I'm not really sure how to fix this.
Be forced to do what every other admin in the world has been forced to do;
Throw more hardware at it, even though there's a software solution.
I don't know what's a forum-proxy issue and what's an initial-host issue, but those images are stored on our server which currently only has a 1Mb upload connection. We're looking to improve that in the near future.
Browsers nowadays like to make as many simultaneous requests for images as there are images on the page (this is stupid IMO). So all of your images are downloaded at once via the proxy, but your connection isn't fast enough to deliver everything before the proxy times out after a few seconds. Not being able to serve this much data quickly enough is understandable, but it still causes issues. The problem is that browsers can wait forever for servers to respond, so they're fine with issuing even hundreds of connections at a time, but the forum's server cannot wait. Each proxy connection takes up resources, so it must complete quickly. I'm not really sure how to fix this.
I don't know what's a forum-proxy issue and what's an initial-host issue, but those images are stored on our server which currently only has a 1Mb upload connection. We're looking to improve that in the near future.
Why doesn't this image work then? It's a GIF hosted on Imgur.
It's too big. The limit is 2.5 MB
That happens when the server hosting the image is too slow. Use something faster like imgur.
It doesn't rely on extensions. Example:
Why doesn't this image work then? It's a GIF hosted on Imgur. One problem I have with the image proxy is how it breaks images without an extension. If an image is served with the right MIME type, such as image/png, it should be proxied even if it has no extension or the wrong extension. Extensions are a very bad way to describe file types over the Internet. MIME types exist for a reason...
It doesn't rely on extensions. Example:
Why does this fail?
That was due to an issue with the BBcode escaping of URLs. I fixed it.
Why does this fail?
Given the funds at disposal of the forum admins, they should be able to fund a perfectly fast image proxy. It could be a good thing, *if it worked properly*. I mean how hard can it be for a proxy to download and host an image? It should be working perfectly in a matter of seconds...
Sometimes its better to just let the old stuff go and make something new...
https://bitcointalksearch.org/topic/current-requirements-523070
Given the funds at disposal of the forum admins, they should be able to fund a perfectly fast image proxy. It could be a good thing, *if it worked properly*. I mean how hard can it be for a proxy to download and host an image? It should be working perfectly in a matter of seconds...
That happens when the server hosting the image is too slow. Use something faster like imgur.
It doesn't rely on extensions. Example:
One problem I have with the image proxy is how it breaks images without an extension. If an image is served with the right MIME type, such as image/png, it should be proxied even if it has no extension or the wrong extension. Extensions are a very bad way to describe file types over the Internet. MIME types exist for a reason...
It doesn't rely on extensions. Example:
One problem I have with the image proxy is how it breaks images without an extension. If an image is served with the right MIME type, such as image/png, it should be proxied even if it has no extension or the wrong extension. Extensions are a very bad way to describe file types over the Internet. MIME types exist for a reason...
This bug breaks useful services such as Google Docs's chart API, which provides the easiest means to include LATEX in posts.
This bug breaks useful services such as Google Docs's chart API, which provides the easiest means to include LATEX in posts.
It's image host company's that are responsible for this kind of activity.
Jump to: