So, Jeremy, man... what the fuck is up with

Two things:

  1. In order to get the new site working before I released it to the public, I put the IP address for the domain directly into my hosts file. Basically, it means that I was going to the new site while everybody else was going to the old one. Then I forgot to change it back once the new site was working. Oops.

    The good news is that the new site is churning away on feeds just as it should, but you can't see it, because...

  2. Unidentified problems with my domain registrar are preventing you from being pointed to the new server when you type "" into your browser. The DNS info should have been propagated since I changed the nameserver entries a week ago. I have no clue what's going on here, and I'll be on the phone with them today.

So sorry for all the headache; just hang in there a bit longer and I'm sure this will all get worked out.

UPDATE: I've talked with my registrar and the problem should be solved within 24 hours. Check back here tomorrow!

UPDATE 2: Looks like it's up for me and Roderick. If you're still having problems, try clearing your cache on your browser and refreshing. Still getting the error screen? Try back tomorrow.

Read this article
Written on Sunday, July 22, 2007