A blog with a 2008 copyright note offers blog-fixing services. It is not related to this blog. The author is not the GotH of the FixBlog. The services differ. The author has endorsements. Good luck over there!

So, politics, business and the glamour parade mix with Second Life, FaceBook and everybody gets to go into exposing himself and herself extrovertedly and xenovertedly. The truth is a long way from the published self and fiction.

Blogs encrypting truth for limited circulation may be an oxymoron. Are they still blogs?

The means exist as I find in my research for a client. None of the personal stuff should be exposed to the world but the medium should be accessible to all. The client does not trust mere password access. So, we’ll encrypt the entries. The world can see the entries but only select users receive keys to decrypt and read the material.

How to counter bad, slanderous, libelous, defamatory Google search results that kill your carefully built-up reputation, falsely and maliciously? It’s a constant in our work but I didn’t expect the issue on page 1 of the Washington Post.

Usually acting in concert with attorneys, the battle has many levels. Getting a new correction or existing accurate information to jump to a higher rank in a search engine feels pretty good. Making the wrong information sink to double-digit or triple-digit search results generates a high.

What happend to Julie Amero could happen to bloggers. Anybody can catch spyware or a virus that sneakily opens a malicious pop-up window. You don’t have to use an old Windows school PC to run into that problem and face 40 years in jail.

Bloggers are not only at the receiving end, however. They can spread the badness quite easily, albeit unwittingly.

Sign up for a gadget here, a widget there, a map, a clock–and bang! You and your visitors may see more than you bargained for. A client had several such innocent-looking features. Figuring out which one caused the nightmare had him stumped.

FreeBSD is a good base for a blog. Some argue that you should stick with version 4. When 6.2 came out, I thought I would try it. By now, however, I forgot the difference beetween a release branch and a stable branch. I guess I’ll go with release release since it incorporates corrections that appeared since the stable release.

Why would it matter? Sometimes, I ran into unavailability problems when adding packages through sysinstall. Was it the stable version or the release version that could not be found on the FreeBSD ftp servers through sysinstall? If I only knew.

Dad made us mow the land by hand. Uphill, downhill, sideways.

The resulting upper body strength seems to last for decades. And came in handy with Date 1, formerly Candidate 1.

That frequent 30 minute workout in the heat of the summer translates nicely into mutually joyful initial impressions.

We had decided on a relationship not involving employment. I’ll do my blog thing, she’ll do her graphics and designs. We’ll cooperate symbiotically on a case-by-case basis.