Let's rethink image hosting

Synthesis · Post by **Synthesis** » 07 Mar 2008, 17:19

Ok, I was thinking, since I'm on a 128k wireless connection, how to avoid waiting a long time to display threads like picture of the day and so on.

This is just an idea to help everyone have a better experience and I am sure in a month, all be a it a small percentage, the amount of images viewed here from photobucket and other intl image hosters adds up and takes a small chunk out of your intl cap.

Maybe if we find a good local image hosting site admin can even be more generous on avatar and sig limits. I'm happy with it as is anyway so that's just a thought. And what ever happened to the sigs being hosted on PCF like the avatars?

Here's a link I came across to start off with for free local image hosting.

Here's just a random image I used to test:

Off-The-Chart · Post by **Off-The-Chart** » 07 Mar 2008, 17:32

I am pro for this...

Threads like Cap's Photoshop thread can also be a nice read, but having quite a few int. images in it can hurt, as you say...

Synthesis · Post by **Synthesis** » 07 Mar 2008, 17:46

Here's just a 200kb image I am testing. There was definately a hell of a difference in speed in uploading for me. Sure, there is a possibility of the server maybe being slow but that's we we're testing it. So you may comment on how long it took compared to usual to download this image. And I just saved you 200KB of your international cap.

Post by **Ron2K** » 07 Mar 2008, 18:16

While I agree with local hosting, I do not agree with increasing the current limits. Think of the 56K/ISDN users. (Yes, there still are a few.)

Richard_ · Post by **Richard_** » 07 Mar 2008, 18:29

While I'm all for local hosting too, this unfortunately is a farce. Geolocation also sticks this site's IP slap-bang in the US:

Code: Select all

:~$ traceroute adsbb.co.za
traceroute to adsbb.co.za (66.11.230.21), 30 hops max, 40 byte packets


 1  home.gateway (192.168.1.254)  1.288 ms  0.840 ms  0.679 ms
 2  *.*.***.**-***-********-****-***-****-****.**********.co.za (**.***.*.*)  24.906 ms  18.161 ms  19.690 ms
 3  ******.***.** (***.*.***.**)  41.960 ms  36.622 ms  37.686 ms
 4  196.25.254.81 (196.25.254.81)  39.808 ms  51.725 ms  36.443 ms
 5  * * *
 6  pos2-0.cr02.ash01.pccwbtn.net (63.218.94.17)  342.277 ms  359.712 ms  339.050 ms
 7  p3-2.IR1.Ashburn-VA.us.xo.net (206.111.0.25)  352.305 ms  374.684 ms  337.814 ms
 8  * te-3-1-0.rar3.washington-dc.us.xo.net (65.106.1.10)  345.245 ms  346.032 ms
 9  ge7-0-0d0.rar1.washington-dc.us.xo.net (65.106.1.9)  341.886 ms  353.709 ms  353.003 ms
10  p0-0-0d0.RAR2.Washington-DC.us.xo.net (65.106.1.14)  344.865 ms  352.261 ms  369.017 ms
11  p6-0-0.RAR1.Chicago-IL.us.xo.net (65.106.0.45)  350.086 ms  344.803 ms  347.344 ms
12  p6-0-0.rar2.denver-co.us.xo.net (65.106.0.25)  387.771 ms  384.424 ms  370.767 ms
13  p0-0-0d0.RAR1.Denver-CO.us.xo.net (65.106.1.73)  371.203 ms  366.642 ms  374.468 ms
14  p5-2-0.rar2.seattle-wa.us.xo.net (65.106.0.53)  386.636 ms  385.211 ms  385.300 ms
15  p4-0-0.MAR2.Beaverton-OR.us.xo.net (65.106.0.146)  396.736 ms  408.588 ms  397.639 ms
16  p15-0.chr1.beaverton-or.us.xo.net (207.88.83.206)  396.157 ms  394.569 ms  399.573 ms
17  66.239.36.78.ptr.us.xo.net (66.239.36.7)  387.626 ms  389.870 ms  383.117 ms
18  p-20-20.edge-rtr01.ptldor02.iinet.com (198.145.240.161)  408.810 ms  387.803 ms  384.430 ms

Not only is the server in the US, my packets are also taking quite a field trip along the way to get to their destination.