The best thing about resolving not to Really Try and Read all this stuff? I missed almost all the early bitching about the iPhone. [Yes, based on what I saw in the Keynote, I'll buy one; I'm already a Cingular customer, so I'm used to their rates and it's not going to be a huge cost increase over my Treo 650. Plus, it'll be something other than my Treo 650, which is a good thing. I keep waiting for Unit #3 to die on me.]

[And yes, I say it organIzation, like I'm from Mississauga or something.]

That said, I have felt like doing not much of anything since getting home; after some sleep to knock down the pain/dizziness, I woke up sweaty—why the hell are we pushing 80F in the last week of November? Please explain—just in time for my next medication run. Woooo. The wick still annoys the hell out of me, but it’s getting better. Part of the issue right now is swelling [from irritation] in the area behind and under my ear, which I’m treating with heat. [I just looked it up on WebMD, and maybe I should be doing that with cold. Dammit. But it feels better.] I’ll stay awake until as close to midnight as I can, take the next round of drops, and crash. [I'm so in polyphasic sleep right now, heh.]

In other news, I’ve whittled my new-item backlog in NNW down to 3003. The reason that my migration is taking a long time is because I’m having to switch from FeedLounge’s superior tag-cloud-style filing system for feeds back to a tree-like structure. I will be very, very, very honest: not wanting to leave a tag-cloud system kept me on FL for the last … six-to-eight weeks. When I first found out that Alex was leaving FeedLounge—okay, actually before it was public, back when I was spending time talking to both Alex and Scott on the phone about it, agreeing with how both of them felt about the situation [probably much to their consternation, heh]—I made some preliminary looks to moving, and everything told me that I wanted to stay with what I’d been using.

But … well, at some point, the features of actually, oh, getting your feeds to actually aggregate trump everything else. Tonight, I found that one of my RMFO-Bloggers had 15 spammy comments that were just sitting there, all because FL hadn’t been aggregating his comment feed for me.

So anyway … the transition to a tag-style architecture to a tree is a slow one. Essentially, what I’ve done with every feed I’ve cleared so far is put it into a lowest-common-denominator group in NNW, which has typically been firstname_lastname. I will, at some point in the future, begin organically grouping these folks back into trees. [I've actually started with all the RMFO-Blogs feeds that I follow.] Essentially, I’ve gotten back to a flat structure, which I’ll then go back to treeing.

Good gracious, when are more people going to start supporting tag-style architectures? It may be a hard problem—I honestly don’t know—but it makes so, so, so much sense. Kottke.org’s remaindered links? I want those in “jason_kottke” and “linklog”, because sometimes I feel like perusing all the linklogs I follow, and sometimes, I want just Jason’s editorial voice. The same way with groups of my friends—I want Jonathan and Ashley in both “cabal” and “creekmores”, because sometimes I want to catch up with all my friends, and sometimes, I just want to know about what’s going on down the road from me. And best of all, I want my Bruins-related feeds from boston.com in “boston”, “bruins”, “hockey”, “nhl”, and “sports”, depending on what mood I’m in. [Why the bifurcation of "hockey" and "nhl"? Hell, I follow and eat/live/breathe college hockey, people.]

When one first encounters tag-style architectures, it seems a bit much, but so can treeing … you can get very, very specific with trees. Why do I prefer tag-style architectures? They slice horizontally and vertically.

So anyway, incoherent rambling over. I’m suck it up with going away from tag-style. I’m in mourning, but not enough to switch back. Right now, I’m fixing everything in NNW, essentially doing all my feed-reading at home [which is fine, because I'm busy at work], and then hoping to go to FeedDemon soon and have this setup all completely done so the OPML import into FD is a thing of simplicity when I’m ready for it.

Leave all the questions that I’m sure you’ll have in the comments. I’ll answer at-length soon. But in short, enough has proven to be enough.

From my end, Scott’s got until 1800 CDT today to at least respond or I’m gone [barring something wholly understandable, like a medical emergency]. As the first release honoree for FL, I hope that sends the appropriate message—enough is enough. In the words of The Cardigans, “If this is communication, I disconnect.”

Update: It appears that Scott’s been having travel issues, and I’m glad that he’s doing the one-month service credit. That’s a fair resolution. Now to make sure that there’s a backup when he’s on travel …

[Yes, I needed an ego-stroke today, and I wasn't above doing it myself.]

[[Okay, yes, we all just went there together with the obvious joke relating to my domain name. Let's move along, huh?]]

[[[Oh, get out of here.]]]

I’ve talked with both of them pretty extensively on the subject. I understand why both of them have made the choices that they’ve made here. Alex, thanks for building a killer UI for the front-end. Scott, thanks for continuing to offer FL. I know that it could have gone either way, and I would have understood either decision path … but man, I’m glad not to have to migrate to another tool.

I’ll be interested to see 1) how the FL community reacts and 2) how Scott carries FL forward from here.

Something I meant to write about but didn’t: I might suggest registering FeedLounge.info as a wholly off-site, emergency-case info site about FL outages. I have rocksmyfaeoff.info on a whole other server and my folks know to check there when the site’s unreachable.

If you want to do it and want a place to host it, I’d be happy to host it gratis.

They took my suggestion and made it awesome. FeedLounge.info is now going to be a status log for FeedLounge, which will be helpful on the quite rare occasions when FL.com is unreachable. Plus, feedlounge.info is faster to type than feedlounge.com/support/status/.

Best as I can tell, they’ve automated it as much as is possible, which is always a good thing. Status is necessary, but status over progress is never a good idea [unless you work for the government, and then it's SNAFU].

Happy to be a tiny part of it, guys.

Anyhow, so FeedLounge had some downtime, related to a minor oversight that ended up being a colossal Charlie-Foxtrot: Alex’s server was, for a bunch of understandable but inexcusable reasons, the single-point-of failure for DNS authority for FeedLounge.com. When Alex’s server burned up, it all went to shit—FeedLounge the server was running fine, but no one could reach it. The DNS system was unable to route around the damage because there was a single point of failure.

I think Alex is pretty clear, in retrospect, that he didn’t address this well enough the first time, so he did, as he termed it, an “O’Grady style Q&A” to answer the questions regarding FeedLounge’s outage. I want to slice-and-dice to the relevant parts:

Why didn’t you also check this for feedlounge.com?

Unfortunately, the answer is really simple – we forgot. We moved the feedlounge.com web site to a dedicated server in a data center in New Jersey last summer around the same time we move the ‘Lounge onto our big servers in our rack space in San Francisco.

Since feedlounge.com was no longer on boxes at the Austin data center, we didn’t think to check the DNS records for feedlounge.com.

Do you now feel that was monumentally stupid?

Um, yeah. And then some.

Are you saying that if this had happened a week ago, it wouldn’t have caused any trouble?

Most likely, yes. We’d have replaced the fried box just like we’ve done, but the backup DNS servers would have shouldered the load while we did so.

Sounds like you guys should have paid more attention to this.

Agreed. Lesson learned – the hard way.

…

So what do you do now?

Besides offering an apology to our users, there isn’t much we can do. We have to wait for the changes we’ve already made to take effect.

…

I’m not satisfied or happy about this.

Trust me, we’re not either.

Ok, now what?

It was a bad day for FeedLounge. With apologies to our users, we fix the problem and move forward. As we do, we’ll continue to work hard to make FeedLounge as reliable as possible and continue building the features our users are asking for.

That’s really all they can do. The guys just learned a painful—and, probably, unprofitable—lesson. We’re at the “mistakes were made” portion of the program. As a user of the system, it’s easy for me to be upset—and yes, I was inconvenienced by this. But I talked to Alex (and some to Scott) while it was on-going, and so I knew what the problems were and that it would be a pain to fix them. DNS is a royal pain in my ass, and downtime is, too.

While there’s room to be disappointed in the early responses given—telling users to hack their DNS isn’t a good solution; I’m reasonably handy with computers, and I didn’t know how to do it straight off—those are simply the responses that you unthinkingly give when you’re reacting rather than acting. To be fair to the guys, they had a lot of reacting to do—”I’ve tried A! I’ve tried B!” Sometimes you have to do what Deke Slayton—at least I think it was him—referred to as “the JC maneuver”: “Take your hands off the controls and put it in the hands of a su-per-nat-ur-al pow-er.”

Some days, you’re the cow, and some days, you’re the pasture. FeedLounge was definitely the pasture recently, but remember … fertilized pasture grows really good grass.

• Feed List API
• Notification API

I could definitely find value in this in generating a blogroll, if nothing else. I just gave mine a test, and it gave me a good little start. [I'd link it, but it has Susan's full name, and I don't like linking her full name publicly. She doesn't like it, either. There's probably other folks there who don't want their full names used, as they may be pseudonym-blogging, so ... ]

Also getting some love in all this is Matt Walters. Congrats for the named release, Matt.

How many people were involved in the building of Feedlounge?

It was primarily me and my partner Scott. Brian, an intern at Scott’s consulting business, did a bit of work on it too, especially as we were getting started last year. We recently added another team member to focus on performance and scalability and allow Scott and I to return our focus to building a great application.

Who? We want to know, Alex. [By "we", I mean myself and Chris Meller, of course.]

[Hey, it's the old reporter in me that comes out from time to time that asks these questions.]

Exactly. I pay for good experience. I use FL on three computers every day [work PC, Mac mini G4, and iBook G4], and my workflow is the same for each machine. I don’t have to think when using FL—I just use the freakin’ product. I can slash-and-burn through a whole lot more feeds with FL than with any other reader I’ve used, and I’ve been (ab)using feed readers for a few years.

I would cry piteously if FL went under. It’s as essential to me as my Internet connection, and it becomes more integral every day.

1. I, as a FeedLounge user, get fresher feed data. This is where the rubber really meets the road!
2. Content publishers who send 304 get fresher visits from FeedLounge users. Don’t think that other Web aggregators won’t mimic this idea as they expand, either.
3. Aggregators and 304-aware publishers both get huge bandwidth savings from not having to send data back and forth. [See Anne van Kesteren's discussion of 304 for a funny personification of the exchange between aggregator and server.]
4. Content publishers who aren’t 304-aware will have positive incentive to get that way. [They already have bandwidth-savings as an incentive, but the blogosphere is notorious for getting secondary effects like this to get CTOs to reconsider problems they're presently ignoring.]

Kudos for the idea, Alex and Scott. I hope Bloglines and the rest of the folks in this space will adopt this approach.

Things got fixed, and Alex and Scott addressed everyone’s concerns fairly well. If you read through the replies, you see that most everyone was pretty level-headed about it. Why? I think it’s because Alex and Scott have learned—probably the hard way—that they have to be personable, real, and open with their customers. Now, Alex might be looking at this and blinking a little, but I’d encourage him to read the gamut of responses that he’s made to folks as time’s gone by … and he’d see that his earlier sharp edge has definitely been broken.

Seth Godin’s entry about the culture of dissatisfaction hit home as I considered all this in retrospect:

The problem with this emerging culture, aside from the fact that we’re unhappy all the time, is that it doesn’t give marketers a chance to build products for the long haul, to invest in the processes and products and even operating systems that pay off over time. The problem is that when brands fizz out so fast, it’s hard to invest in anything except building the next hot brand.

Is there an answer?

Talk to people who live in Vegas and you’ll discover that most of the hard-working folks who have been here more than a decade (the cab drivers and the doctors and the rest) aren’t so swayed by the billboards and the promises. Instead, they embrace the qualities that come from relationships. A relationship with a front-line worker (ask for “Bob”) or a relationship with a provider or an organization that has come through for them.

It seems to me that insulation from discontent comes from building a relationship. From real people. Relationships that make us feel counted upon, respected, trusted and valued cut through the ennui of dissatisfaction. We got ourselves into this mess by acting like smart marketers, and as marketers we can get out of it by acting like people.

Consider also the case of Six Apart: back when it was just Ben and Mena, flubs and false starts were greeted with mild dissension and understanding. Then, when the MT3.0 licensing scheme was announced, the growing corporate vail around 6A ended up making the backlash easier to spew.

I think the lesson to be drawn here is damn simple: it pays to stay personal, because it’s a hell of a lot easier to be mad at “the man” than it is any individual. Note that, in every entry I write about FeedLounge, I always write it as “Alex and Scott”. If they keep on being successful, it’ll be because they continue to develop a good product and continue to be personable with their customers.

It’s a hard balance to strike, to be sure—time spent building relationships with customers is not spent quashing bugs or coding features. Users have to accept that the relationship time is fleeting, but they have to work to cultivate as they can, because any relationship is a two-way street. However, I’m fairly convinced that personality trumps commoditization. Hasn’t Apple been teaching us that all these years?

Well, I know what the reason is, and it’s a case of tools influencing me. The tipping point for me today was looking at the entry touting the narrative shift change over at Dan Benjamin’s Hivelogic, a Weblog I read for a while, but stopped reading—probably partially due to Dan’s use of second-person narrative. As I was following Dan Cederholm’s rabbit trail to the Hivelogic paradigm shift, it suddenly hit me: everyone comes up with these cool little site names, and I quickly shift them back to people’s names when I add them to FeedLounge. For example, Hivelogic is titled “Dan Benjamin’s Hivelogic”, which tells me both the name of the writer and the name of the site.

I’m not wholly consistent in doing this—I’ll admit that I’ve gone too far in forcing a name-only convention; I’ll repent—but I really seem to like it. And so I present you … Geof F. Morris’s Indiana Jones School of Management.

[So meta, it hurts.]

Wow. Just when I thought my night wasn’t going to get any better after watching my beloved Chargers defeat our hated rival … it did.

Has anyone seen my jaw?

Let’s examine some reasonable motivations for doing this:

1. Finding FL praise. This has got to help you at 2245 when you know you’ve still got bugs to quash and energy to do it. I get the feeling that Alex and Scott do what they do because they love it even more than they love getting paid for it; knowing that people love the products of their work has to stoke their fires to do an even better job. [Pause for a moment and consider being married to either of these two. What wonderful women they must be to put up with their husband's slavish devotions to their creative work.]
2. Finding FL criticism and bugs. Constructive criticism is good, and sometimes, it comes with bug reports. Sometimes, it’s design criticism that maybe they should address [and sometimes I address it for them if I know the answer]. Not everyone wants to file bug reports on a forum, either [although you can see on the update log that they quash bugs ruthlessly and also log it publicly, which I also think is awesome]. What I really love is that neither one of them seems eager or willing to jump on the hand grenades of the critics, and that FL lovers like me aren’t doing so, either. That said, linking to them is good—you want to present a full face of your product, and doing that means that you want to highlight the faults [even if people are misinformed or wrong].
3. Increasing the ambient findability of FL users. I think that FL users are, in some way, looking for a community; with a willful choice of using PunBB, I don’t think Alex and Scott want a community to develop in their forums—and being focused is fine and great, and I support that!—but I think FL afficianados can use this to slowly find each other, much in the same way that Mac users do.

I wasn’t sure that I’d be all gushy about Alex’s log at first, but I really am enjoying it a lot. Thanks, buddy.

That said, I find the service to be very much worth that pricing level. I’d probably pay more to them, but then I’ve been using FL for months and am about as irrational about it as your average junkie is about his heroin. I wish I were kidding, but I’m not.

Anyhow, just a reminder: FL goes from alpha to beta in a week!

I must now construct my shrine to Scott Sanders.

Oi. This is what happens when I leave it alone for four days…

I bet Alex is happy that he’d gotten all that PostgreSQL experience in porting Tasks and TasksProâ„¢ over to it …

Oh, and autodiscovery’s finally supported. [I know why it wasn't, but man ... phew. This makes my life easier.]