Hello, again, early 2019 edition

Retrophisch.com lives again. I have wandered aimlessly in the wilds of the Internet for far too long. It was finally time to own up to one of my mantras regarding one’s online presence: own your own domain, own your own content.

History, and the way forward

When last we left this site, I had eschewed WordPress for Tumblr. Given one of the constants of life is change, it was only a matter of time before WordPress evolved to the point where I would make the leap. And it was so easy. I wonder why I took so long to do this. (Oh, right, life with three boys, and being hockey dad, Cub Scout dad, swim dad, golf dad…)

I have had a Dreamhost account for a few years. The only real use it had been seeing was serving up email for my oldest, on one of the domains I registered for him a decade or so prior. When the server this blog and its predecessor had been living on suffered a catastrophic hardware failure, it was time to make the move to Dreamhost full time and relaunch. So here we are.

WordPress installation on Dreamhost was a snap with their One-Click Install. Importing my Movable Type archive went seamlessly. Well, seamlessly after I figured out I needed to install and turn on Markdown plugins for some of its and the Tumblr archive’s posts to look as they should. Said Tumblr archive followed soon after. My Tumblr site remains up, so long as Tumblr survives as a corporate entity. Should that fail at some point, the posts live on here. Which is the whole point: owning my own content.

Years ago, Michael Hyatt blogged how he looked at his online presence as revolving around his blog/site. That was home base. Everything else—Twitter, Facebook, Instagram, what have you—were simply outposts. They were never to be one’s only online presence. While this resonated with me, having had an online presence before any of these companies came into existence, I stumbled in hewing to it. Nevertheless, thanks to catastrophic hardware failures, corporate buyouts, and creepy corporate policies, I began anew to prepare myself to giving up one or more of those entities should I feel the need arise.

Manton Reece reiterated, repeatedly, that which Hyatt promoted, and I internalized: own your own content. Manton left Twitter in 2012, but didn’t stop with posting tweets. He just did so on his own blog, in the form of snippets, or micro posts. This eventually led him to launch Micro.blog on Kickstarter two years ago. I backed this project, and was among the hundreds of original tenants of the Micro.blog ecosystem. I mainly set it up as the own-my-own-content side of my social media. You’d see these same posts on Twitter, Facebook, and elsewhere, but they lived on Micro.blog first. This became my default online presence.

Yet there was still a sense of unease behind it. Yes, it was a service I was paying for. I was the customer, not some corporation paying Manton for all my info so they could sell ads to me. You know, exactly what Twitter and Facebook do. But it still felt like another layer to deal with. It was better than what I was doing before, and I continue to enjoy the community aspects of Micro.blog, but it didn’t feel like home.

Now those posts will reside here. I ran into an issue importing my Micro.blog feed, and I’m working with Manton to resolve it. Those will cross-post to Micro.blog, and thus to Twitter (and Mastodon, for what it’s worth).

There’s still a lot of cleanup to do on the older posts. I’ve gotten through 2002 as of this post going up, which means there’s a long way to go, but it’s worth it to me.

I do not plan to delete old posts. Some of these I’ve read and winced. My thinking has changed on some issues in more than a decade since these old posts were published. With others, maybe I could have been nicer and less sarcastic. (Hey, I said maybe.) But they are what they were at that time in my life.

Much thanks is due to Webmistress and CSS master Raena for assistance in getting things looking just the way I wanted, and to Michael for bits of advice on WordPress, Dreamhost, and importing content.

Why do all this?

Because I can. Because I want to. Because I determined I am going to own my online presence and not outsource it to others. You may not feel this way. That’s cool. But this is the way I want it for me.

Own your own domain. Own your own email. Own your own content.

So what’s next?

A few years ago, when I was throwing around the idea for a new logo, a new tagline appeared in my mind: Navigating the waters of faith, family, and fiction. While that isn’t displayed overtly on the side, it is embedded in the code. So those areas will be my focus, along with the tech and nerdery I’ve long been involved with.

In the latter vein, I already have a draft about Mac portables going, based upon some recent experience, recent news, and recent blog posts by others.

I hope you stick around!

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax