Sometimes "broken" just isn't broken enough.

Just to recap: This is supposed to be a blog about a trip to Italy, and then a trip to Croatia where I, for the first time, met face-to-face with my long lost half-brother.

People who'd seen the blog said it was amusing. One person said it was clever. After being encouraged by those comments, it seemed smart to let other people know about it too so that they might also be amused. So I sent out some emails.

About a hundred emails and a couple of days later, I was stunned to see that I'd sent out the wrong link. Why? I was hurrying to send it out before leaving for work and I left out a critical vowel in the web address.

What to do? Well, explaining where to insert the missing letter "e" somewhere in the 50-character-long address would probably be asking a lot of my potential readers. "I know!," (I exclaimed.) "How about I just fix it so they can go to www.antsinthesnow.com and click on the blog link?" All I have to do is take the DNS and the URL and the A-record and transfer the IP address to the new host and, voila! (Oh yeah, I don't know what half of that means.)

Well, the antsinthesnow part was a good idea, but in the process of testing the changes and experimenting with the proper numbers, I effectively erased my entire site. It didn't help that the changes in question take between 1 and 72 hours to take affect, depending on who you ask, so I wouldn't know for sure until then what the real damage was. It also doesn't help that the intended web host only has email tech support.

The solution in this case is not to default to panic mode. Rather - all the while swearing, cussing and self-flagellating - the solution is to step back and let the stew cook. So at about 6:45 tonight, I clicked on the address, and guess what? It was stew! (It didn't take quite 72 hours.)

Now I have to decide whether anything is actually better than before. (Do they have pills for people who constantly try to fix things that aren't actually broken.)

---