Technical Difficulties.

Ugh, every thing Tech on the interwebs is pissing me off, but I think it might be getting better.

First the obvious: I wanted to post that video of Mike Daisey and how he handled the assholes who fucked up his work, but it just would not work until now, and yes, I figured out why. It's too tedious to detail right now, frankly.

What pisses me off is that I had just been thinking that, y'know, all this speculation about eventually moving this blog to my own site, hey, why go through all that, Blogger's working out pretty cool, they store all the stuff, I don't have to mess with it, and what the hell, it's good enough for Post Secret right?

Fuckers.

My next bitch is Imgred.com. I shouldn't be pissed at this guy, 'cause he's trying to do a cool thing but it was kind of unclear and now I need to swap a bunch of things out.

The idea behind imgred (Image redirection) is to make it really easy to avoid Hotlinking. Hotlinking (which I am guilty of innumerable times) is when you see a cool picture on the internet, and you link it somewhere else, say a Blog or a forum, and you do so directly from the place you found it. The problem with this is the site that the picture was originally on gets dinged for bandwidth from both sites now, and sometimes that costs the person who originally put the thing on the web money. Not cool. What's considered polite is to save the picture, host it on your own site or at a picture hosting site, and link it from there. This is a pain in the ass, and frankly "Politeness" isn't in terrible abundance here on the interwebs.

So this guy, this imgred guy, he creates a code. You simply put "http://imgred.com/" before the url of the picture, link it normally, like you're Hotlinking it, the code hosts it at the imgred site, and after that, that''s the new url for the picture. He even set it up so it'd automatically create a thumbnail.

Cool, I thought, no more hotlinks or fucking around with Imageshack.

Nope, turns out, "This site was meant as a demonstration, not as a self-sufficient service. If someone on Website A wants to show an image from Website B, the image should be locally cached on Website A. It is up to the Website A programmer to develop such functionality."

So, it's a code I could use if I had a site to host stuff at, and the brain power to implement the code. That is, I could come up with my own, private, "imgred.com" for my pics I wanna "Borrow" off of the net. Well, that's cool, I guess, and while I'm sure I could figure all that out, I'm probably gonna go try and figure out "Flickr" again instead.