To extend my apology further, Fran  

In my mind, the fact that there's no commenting system right now in the OPML Editor blogs (notwithstanding the Haloscan solution) makes doing something significant with the OPML Editor blog much more difficult and hit-or-miss than with WordPress or Moveable Type, for example.

It works for Dave, though. But he's got a whole community constantly trying to get his attention. If he wants to know people's responses to him, it's easy to find out.

Conversely, for people like me, I'm not really trying to be part of the conversation. I just want to publicly log my noodling so that (1) if someone stumbles on it and finds it helpful, I've done a mitzvah, and (2) if my computer crashes and burns and all my backups are destroyed by a flood, I haven't lost all record of the tidbits I've accumulated (for whatever that's worth). In that model, I'm not seeking the other side of the conversation (by subscribing to your feed, for example), but I want anyone who wants to ask a question or leave a comment to be able to reach me (without having to post my email address, although that's easy enough to find anyway).

I'm not sure why I deviated from my habit of remaining strictly non-personal in my blog posts. Honestly, I didn't think anyone was listening to me think aloud. In any event, please understand that I was thinking only of the OPML Editor, and not the people who are using it.

Sorry, Fran. I was just shooting my mouth off with that comment. Obviously, I'm not reading every OPML blog - so my generalization was ill-informed. By the way, I included myself in the irrelevant category, if that make you feel any better. 

Okay, I've put in my two cents on the new OPML Community Server Howto. 

Listening to Dave's podcast from today... Oh, crap! :-[ 

Bug, not bug 

Maybe I've been throwing the "bug" word around too carelessly. Even when it's in quotes.

The point is that any issue in the community server where there does not appear to be a server running on port 80 can be addressed as Kosso and I have said - don't include a setting for user.opmlServer.ipAddressPort80 in your opmlStartupCommands.txt. That's it. Very simple.

I'm not even sure that a new HOWTO is necessary, but I've made some changes to Kosso's writeup. (They're mostly cosmetic or intended to simplify or clarify.)

Revised draft