I Build Pacific Rim Jaegers

Introduction:  These jaegers i built using  jaeger designer and also made a background for some of them.

blueprint #2
the blueprint for alabama 12 (front view).
JaegerPoster
the first jaeger built for the U.S. it was built for new york and is now helping to build skyscrapers.
blueprint #3
the blueprint for alabama 12 (back view)
sniper ronin
built for long-ranged combat
crimson tide
roll tide roll!!!!!!!!!!!!!!!!!
gipsy danger 2.0
the second gipsy danger (in my imagination) if you do not know what i am talking about see pacific rim (just realized this, i put the wrong legs (and arms!) on it the legs are cherno alpha’s and i don’t know what jaegar the arms belong to)!
blueprint #1
the blueprint for alabama 48 (i think)
shih han
shih han’s jaegar.
cherno alpha 2.0
the second cherno alpha

tacit tacit lucky saber brawler crimson scimitar coronado spirit

bessie's jaeger
bessie’s jaeger
alabama 8
t’was the strongest jaeger ever built but it rusted quickly, so when it went out into the waves to fight a kaiju it rusted to the core but fortunatly the crew was rescued by alabama 48
alabama 48
this jaeger helped rescue the crew of alabama 8.
alabama 51
as the name sugusts it is the only mark-7 jaeger IN SERVICE. there have been others.
alabama 45
this jaeger was moved to hawaii after alabama 50 was moved to japan.
alabama 11
this jaeger froze in alaska.
alabama 12
this jaeger froze in alaska
alabama 49
this is a rogue jaeger it was accidentally turned into a living organism!

alabama 32 alabama 10 alabama 9 alabama 7 alabama 6 alabama 5 alabama 4

the old jaeger built for alabama.
the grand old jaeger built for alabama.

alabama 2

The New Blog Ian (Back Where the Old Blog Ian Was)

Blogger Logo
Blogger, which has slowly turned to crap.

On January 24, 2004 @ 15:30 I created Blog Ian to chronicle my son’s journey through this world. At the time, he was four months old. I happily ran it on Blogger software running on one of my own Web servers. Then, in 2010 Google—which had bought Blogger in 2003—decreed that all Blogger blogs must run on blogspot.com.

I didn’t like entrusting control of my data to Google/Blogger, but I complied and moved Blog Ian and a couple other blogs over there. There were a few bumps in the transition, but I was basically satisfied with Blogger even as I began to use WordPress for more and more of my blogging and basic Website design needs. It’s gotten to the point now that whenever I need a quick-n-dirty Website, I slap together a WordPress installation in, like, 20 minutes.

Until…

Until the day (and I don’t even know exactly when) when Blogger decided to delete all of the images I’d uploaded between 2010 (when I moved to blogspot.com) and 2014. Dozens of images were suddenly missing. I still don’t know exactly why beyond some sort of weird cluster-crap among Blogger, Google+, and Picasa (and PicasaWeb). You see, Blogger, unbeknownst to me, was storing my new, uploaded images in PicasaWeb. Best I can guess, there was some shift in my Google account—perhaps when I activated Google plus—that disconnected Blog Ian from its PicasaWeb album.

I spent an hour or so yesterday trying to figure out exactly how it happened—following leads suggested here—but I was not able to track down Blogger’s crap move.

So, Good-Bye Blogger

And so that motivates me to bid adieu to Blogger. WordPress is a superior blogging platform. Why stick with Blogger when it’s going to do crappy stuff like this?

Many of my images are permanently lost, best I can tell. I still had all my pre-2010 images, from back when Blogger was good software. In fact, they were all waiting for me back on the Web server I’d originally used for the self-hosted Blogger! It’s taken me the better part of the day to move everything, but I think I’m going to be happier with WordPress as Blog Ian‘s new home.

Of course, there hasn’t been much activity on Blog Ian since Facebook took over social media, but still…