As you may have gathered from reading some of my posts — especially the early ones — on this blog, my work here is not commercial in nature and is somewhat experimental.
That spirit of learning is what drove me to install a drupal website on my shared bluehost.com account several years ago. I’d read somewhere that they were very flexible in allowing you to link (and more specifically NOT link) pages within your own website. Basically, it was a nice content management system that allowed you to control your menu linking better than wordpress (at the time).
I still loved wordpress, because it seemed like it was being supported better by the development community and was ever so slightly more intuitive when it came to setup and making it look reasonable.
Well, fast forward about 5 years and I get a cryptic notice from bluehost that I’m violating their terms of service. My shared hosting account was using too many resources. All of my sites were immediately taken offline (including this one). Gah.
Anyways, busy trying to do things that have a chance of actually creating revenue some day, I really let this slide until today, when I contacted bluehost and learned what specifically was causing all the problems. With my deft mysql skills (NOT) I simply pulled the whole db, rather than reconfiguring the comments folder or default spam settings. There was a fair amount of content in the blog, but I’m not using it, and while it was keeping my shared account blocked, ALL my sites were offline and losing any credibility they’d gained in the search engine bots’ minds by being around for a while.
Anyhow, the site is back online now, still dofollow after all these years, and hopefully, will start gaining steam again sometime in the near future. This post was specifically written to trigger by ping-o-matic and let mother Google know that I’m still alive and kicking after all.