As I said in my original post, I never really thought much of blogs and their content. My view was perfectly elucidated by Camille Paglia in an interview with salon.com.

Several people were complaining that they were unable to add comments due to my anti-blogspam software. I have reset it – hope you all have better luck now.

other peoples’ web sites. They’ve done things are have really crisp hi rez pictures instead of this unending egoposting that you’re now looking at.

I bought the ecto blogging software for OSX. I’m really enjoying it and getting the hang of using it instead of the MT tool itself.

Hi, If you visit my site using FF or Safari you’ll probably think the site is fine. If you’re using IE it looks terrible.

Mantra: This is why you always make a backup I took a look at my Wordpress blog engine dashboard and noticed that there was a new version out. I applied this upgrade to my local blog copy on my PowerBook and it looked fine. I did the same thing to the site you’re reading and it messed up in a large way, a much larger way than I was interested in hacking on this morning. Issues I had: Repeated appearances of “Warning: Illegal offset” in sidebars Plugin Listing showed the word “Array” all over the place ( i.e. PHP was printing some variable that was an array, versus its contents ).

I’ve been silent. This started out for a very plain reason: I was finally going to move stevengharms.com to fronting another web site. My current hosting provider, however, has been absolutely un-helpful in the process of moving. You see, I show this flag on my domain: Registrar Status: clientDeleteProhibited Registrar Status: clientRenewProhibited Registrar Status: clientTransferProhibited Registrar Status: clientUpdateProhibited To move, I need this removed. My hosting provider, personalsites.org has proved entirely un-responsive to support entreaties. 5 support cases 7 voice mails Countless “I’m on line” web site chats AOL IM Yahoo! IM Mail to his personal site Mail to the admin site It was during a “live chat” session 2 weeks ago that the administrator, Adam Stewart, said he would clear my lock.

Thanks for following me across to my new site, note the new .net domain. I’ve not written for so long owing to my fear of having to migrate more data or lose more data should the lost stevengharms.com die that I’ve completely fallen out of the habit of writing. So far the folks at hostgator have meen a dream to work with, I opened 3 different support cases with respect to getting things set up and going and all three were addressed and dealt with between the hourse of 9 and 5. Totally, professional, friendly, and smooth.

According to Wordpress this will be by 1,003rd post which means that like most numerically-significant tripodometer rolls you notice it just a few clicks past the “momentous” moment. I remember when I rolled my old Blazer’s trip past 100K. I was on the lower deck of I-35 headed southbound across the river. I looked to my right and saw the Memorial Stadium, the lit up tower, and the lights of downtown in that 0th mile. It was memorable. But on this site, the 1000th post seems to have been: “One man’s DITMTLOD is anothers, “eh”?”. Well I can’t say that was particularly enlightening reading, but probably par for the course of those that come here.

I have been wanting to get the Vim Editor working as a tool for blogging. I’d discussed this a time or two with my friend Daniel Miessler, and he brought up a critical thing that was missing for him in migrating away from Textmate: the ability to do an “I’m feeling lucky” hotlink onto a word as one is composing. I had to admit, this was a pretty compelling feature provided by Textmate’s “Hyperlink Helper” bundle. Its lack definitely hindered my drive to blog in vim. To that end, I have created my first Vim plugin and port this sexy capability to Vim.

As I mentioned elsewhere, my friend Daniel Miessler said that he would be ready to give up Textmate for Vim but were it for the level of blogging support. I have, hopefully, made it easier to do so. In fact, I’m writing this blog post and using my fork of Vimblog to manage it. Here’s how this post was made: :Blog np created a new post Moved down to the Categs line and then: :Blog cl /Techno to match the right line. Hit enter. Vimblog just copied the category name to the yank clipboard for me and then… p to paste it in G to the end of the file o to start typing Typed Daniel Miessler v2b\gifl did a Google I’m feeling Lucky to his site and wrapped it in a markdown link More editing :Blog draft (because it’s still alpha-grade code) so I could check it out in Wordpress Took a screen-shot of vim to put in the post :Blog um ~/Desk/vimb Vimblog pasted the url link to the image that makes this work: Published this post with :Blog publish

I recently migrated my blog from Octopress 2 to Octopress 3 and thought I’d provide a write-up on the migration process. The process covers changing over with the least amount of fuss. I provide code to help automate things as well as code to help sanitize your data. This process can be completed in 6 steps. Background Jekyll is a static-file publishing platform. It’s designed to help you create a “Plain Old Web Site” with consistent look and feel. You write a plain-text document of content, run a program, and Jekyll wraps the page with template styling, footers, headers, etc. It helps turn “a heap of text documents” into a coherent site.

Big things have been happened in my life since I last wrote, I suppose it’s time that the tale were told. But, first, I had to upgrade to Hugo. I had been using Jekyll + Octopress for several years but the speed of Ruby doing static generation made it really hard to do enjoy writing and seing the output of my labor. Hugo, built on Go, is screaming fast and removes a bit of the “Meh” out of blogging. Hopefully I can

In preparation for my integration of my extracted Facebook content, I needed to help my blogging platform, hugo, be able to help me test and evaluate the data. I also needed some help in being able to verify dead links in my 18 year archive. I’ve now added the ability to browse posts by year as well as by tag.

Recently I was looking through my Twitter archive, and realized that I had failed to port some images and that some of the tweets were really not that interesting. Building off of the work I had completed within the last week, I was able to get some data about which items needed to be culled. Also, while doing that, I found a few posts that had come loose from their images. I remedied that while working on this project.

Now tweets can be visited here.

Additional changes:

• Tweets that have an image now have a handy camera icon
• I added a year-and-month based navigation