Battleground God This is brilliant.  5:41:03 PM    

The Doc Searls Weblog : Monday, February 18, 2002: "If it's a fact that most blogs suck, it is neither a useful nor an interesting one. Unless, of course, you're writing a story about why blogs suck." Doc, once again, nails it.  5:21:28 PM    

Yahoo! News - Pope Has Performed 3 Exorcisms, One Last September. Good to see he's keeping busy...  1:29:30 PM    

Ok, it's all fixed now. For now. Here's what I learned in the last 24 hours:

1. Moving Radio from one machine to another is a miserable task. You have to update all references to the path to your data in the myriad of places it exists. The included script to fix this (which I found out about belatedly) does not work properly with Radio and I did find someone who had updated it for Radio but it still did not solve the problems. In the end, Radio worked by nothing I could do would make the Manila/Blogger bridge tool work so I couldn't update my blogger blog at the same time any longer.
2. If you give up on this kind of venture and revert back to your older copy, any blog entries you make with the other copy are blown away entirely as the older copy simply sends up what it knows about. This is not entirely unexpected but it would be nice if the software noticed that there was stuff on the server it didn't know about and offered to transfer it down to your local database or at least warn you that it's going to blow it all away.
3. Sometimes upstreaming doesn't work and you have to kick it hard. As far as I can tell, I was having DNS issues getting to plant.blogger.com which was mucking up the entire upstreaming process. When I replaced that with an IP address (a temporarly solution) it worked again and my blogger site was being updated while the radio one wasn't. Quitting and restarting Radio and forcing an update by editing some entries finally got it working again.
4. Radio's purpose to make blogging easier for the masses has a long way to go. Once something goes wrong, you have to be a technical type to solve it. If I hadn't been a Frontier developer in days of yore and an all-around geek, I doubt I would have been able to fix the problems I had and would have had to reinstall from scratch. Not user friendly by a long shot.

Hey, don't get me wrong, I still like radio and am glad I paid for it. Doesn't mean I can't be critical...  12:25:39 PM    

Now all of my TCP streams are being closed unexpectedly. No clue what that means or what to do about it. I don't have time now to go search through the discussions and other tech support files at the Radio site. So, this has to sit until later. (I tried one more thing and it seems to have worked, a bit)  11:43:01 AM    

So, among the entries that got toasted are a number of rants on my part about radio being a bitch to move around. I moved it to my desktop and everything died. I updated all the path names and yet things still behaved very badly. I realized that Radio is not written to be a *good* OS X application. Being a UNIX system, the radio files should *not* be stored in /Applications/Radio Userland/ but rather in my home directory. This way, they can be referenced as ~/radio/whatever/ and if I move things to a new system, that will still work if I keep the relative path the same. And this is how UNIX systems do things. UNIX programs never store their configuration data in /usr/bin/ and so forth.  11:37:05 AM    

This weekends Missing Blog Entries.  11:19:31 AM    

Wow... Radio blew away all entries I made yesterday and this morning when I reverted to the laptop again. Not entirely unexpected which is why I copied the stuff I'd written that I wanted to keep. I'll get it back up here shortly.  11:16:27 AM    

I rolled back to the Radio on my laptop and gave up on moving it over to my desktop system for now. Now I wonder how Radio will react if and when it notices that updates happened to the Radio site that it did not make...

If you are reading this on raggedcastle.com, then we're back and updating on that site as well. There are entries on the Radio side that are not on the raggedcastle side but until further notice, both sites will be updated at the same time from here on out.  11:12:31 AM