There are actually a whole bunch of reasons why image hosting sites are shit. For one thing, you get cunt sites like instagram which deliberately encourage users to fuck their pictures up with stupid crappy "filters", and brainwash them into thinking that this is somehow "trendy/cool/arty" or some other crappy buzzword, when in reality it is just plain shit. Then there is the problem that a lot of them don't allow glamour photos at all, while those that do allow them are all run by stupid Americans who don't know the difference between glamour and porn and think that once you go as far as showing nipples you might as well have pics of some woman with two donkeys' dicks up her arse on the same bloody page. Note to any American image hosting providers who happen to read this: In the UK we have a clear distinction between glamour and porn. Stop trying to impose your cultural values on the rest of the world.
However, that particular reason does not apply in the case of the majority of photos... The following one, however, does, because every image hosting site does the same fucking thing. The specific URLs may vary, but the principle is a general one. Let's take twitpic as an example, though they're all as bad as each other...
Displaying an image in the browser is very simple. All you need to do is retrieve one image file, and that's all. Like this:
You absolutely DO NOT need all this fucking shit which twitpic blurges at you. All the delay involved in making lots of connections to a whole bunch of different servers which then do slow scripty things, when all you need is ONE connection to ONE server to retrieve ONE file with NO scripting involved. All the pissing about because the cunting thing makes you wait until it has loaded, rendered and executed every single bit of bullshit code before it renders the bit you're actually interested in, ie. the pic itself. Not one bit of this fucking shit does anything useful, all any of it does is slow things down, get in the way, and make the image hosting site a cunt.
All that FUCKING BOLLOCKS when all that you need is just one line of it... and not the whole of the line at that. Look at this...
All we are doing here is retrieving a picture, right? One simple image, posted in public on a public site where anyone can see it. All you need to achieve such a simple aim is this...
So what the juddering fuck is all this twatwanking shite in aid of?
FUCKSAKE!!! Key? Expires? Key pair ID? Signature??? And look at the fucking length of it too! To achieve what? Fuck all, that's what. It's a fucking picture. Just fucking serve the cunting thing. Fuck this stupid pissing about "signing" the HTTP request with enough bits to secure a financial transaction to the value of the combined GDP of several intergalactic civilisations. What the pissing fuck are they playing at?
What does it actually do? In short, it makes it so that after 15 minutes the fucking link will stop working, and you can't get one that does work without opening twitpic itself so your browser can execute all that bullshit code again and generate a fresh signature. And no, just chopping the shit off altogether doesn't work...
Which means that if you try and post a link to the picture on a different website, you'll think it's worked, but after 15 minutes it'll pack up and nobody else will be able to see it. You can post a link to the page which loads all the fuckarsed bullshit code before it shows you the picture, but you can't post a link to the picture itself.
Why have they done this? Because they are FUCKING CUNTS. They know bloody well that people are only interested in the picture and don't want all the other fucking shite. So instead of doing the right thing and making sure that the picture is all people get, as they would if they were decent human beings, they do the opposite, and implement measures to ensure that people get all the fucking shite shoved down their throats whether they want it or not... They respond to people not wanting something by making sure that they can't avoid what they don't want. Because they are not decent human beings, they are shitheaded arsefelching wankers.
That huge bunch of GET requests contains plenty else to complain about, as well, such as the numerous pieces of tracking shite and the fucking ad servers, but the one that I consider particularly worth commenting on is another which is specific to image hosting sites:
A flash applet for uploading images. You cunts.
What the fuck is this fucking shite of making people use flash applets to upload stuff? You can do it natively in the browser. You've been able to do it natively in the browser for fucking I don't know how long, probably forever. All it needs is an HTML INPUT tag of type "file". You DON'T FUCKING NEED flash at all. All it does is be fucking annoying by providing another means for things to not work. Those sites whose failure to recognise this goes as far as not even bothering to provide an INPUT tag as fallback need their fucking arses kicked from here to Thursday. Fucking cunts.
(Weirdly, on returning to this page over 2 years later I find that now the raw link with the shit chopped off does work. Whether that means the server has been reprogrammed by people who are not cunts, or just that the expiry cuntery itself expires, I don't know, but there are so many fucking sites that do this shit that the example is still a valid illustration of the principle even if this specific instance isn't like that any more.)
Back to Crap Stuff
Back to Pigeon's Nest
Be kind to pigeons