Oops

[prog]

Apologies to all who saw that last post. I am sad that my browser cached the image I wanted to link to, preventing me from seeing the other image that that one website broadcasts for non-local image requests.

Throwing up now. Ugh.

Comments

[leahleaf.livejournal.com]

whoa dude what was it?

[prog.livejournal.com]

I will say "somethingawful.com" and leave the rest as an exercise to the reader.

I considered writing them to commend their prankishness but request that they use a more work-safe image, in the interests of innocent bystanders (for they practice putting "NOT WORK-SAFE" warnings before questionable links in their own content) but I think it may be safer to just drop the issue for now.

I should have warned the masses

[kyroraz.livejournal.com]

Ran into the same thing when I tried to link to a image there. Ugh. Sorry.

[cortezopossum.livejournal.com]

Somethingawful.com folks apparently have become really annoyed when folks set up image links directly to their site and have somehow been tagging popular images in a way such that they get replaced by some 'guy' (for lack of a more suitable word) with a note about 'not stealing bandwidth'. What's really annoying is that when you actually look back at said image through normal channels (i.e through their web site), that image is changed as well. I don't know if it is done via 'cookies' (i.e. can I blast my cookies and get the images back) or if remembers your IP locally.

Anyway, I'm not sure when they started it but I first noticed it about a month ago.

[prog.livejournal.com]

This wasn't a popular image, just a Photoshop Phriday entry I found funny. I assume that SA has just set up their webserver so that any image request with an HTTP Referer field set to anything other than *.somethingawful.com gets rerouted to that other image instead.