This is a placeholder page. The TinyURL will be repointed at an Imgur gallery later.
I got this email from Atmel yesterday. This is the first time a company has ever emailed me to let me know that they would stop sending me promotional emails if I didn’t respond. This is way all companies should do this. It’s not like Atmel sends me a ton of email anyway, maybe one a month at most. I’m so impressed with being treated like a human that I’ll go ahead and click that YES link to ensure I keep getting info from them.
For many years, I’ve eschewed using www for my website. I’ve always redirected requests for www.duksta.org to duksta.org. Now that I’ve moved to S3, I’ve had to change that stance as you can’t have a CNAME record for your apex domain and the ANAME record is an ugly hack that’s not RFC compliant. I could sign up for Route 53 DNS service, but I don’t really need the global redundancy that Route 53 provides, nor do I want to pay for DNS service. Yeah, I’m cheap like that.
Instead of using S3’s recently released apex domain support, I’m instead putting my site behind CloudFlare. In CloudFlare, I have configured a Page Rule to redirect all requests from duksta.org/* to www.duksta.org/$1. Since I maintained my site structure in the move to Octopress/Jekyll, this has the added bonus of redirecting anyone’s old bookmarks to the right place.
Yes, I’m not truly hosting my apex domain in S3 like this, but rather redirecting it to www with CloudFlare, but it gets the job done for what I need.
After many years of being a member of the Hellyeah! family, we’ve recently been given notice that the rack in which our server has been hosted is being retired at the end of March. The guys who run the rack just can’t justify the $900/month it costs to run the rack anymore. It’s been a good run and it’s been nice having a dedicated server in a low latency data center for years, but it’s also been a hassle at times. As Emory put it so well in his email to us all about the rack closure:
These days virtualization of systems and remote management has made racking our own equipment not only exceptionally costly (by the kindness of others we have largely been immune to these costs) but inconvenient as well since we aren’t young nerds with all the time in the world for hobbies and fixing computers in the middle of the night.
Since I update this blog so infrequently, I’ve always been a fan of statically generated site content. I’ve run Moveable Type for the last ten years and it’s done quite well for me. As an information security professional, I was always worried about vulnerabilities in MT, of which there have been a few, but not so many as in WordPress. With this move into S3, I removed the last bit of attack surface for this site. I’m now using Octopress to generate the site content and jekyll-s3 to push it into S3.
So, it’s done now. Fairly painless. The hardest part was editing all my old posts that I imported from MT to standardize the random collection of paths where my post images lived.