This morning Shaun Inman pushed out (with notice via Twitter) version 1.01 of the Fever° feed reader. First of all, major kudos to Shaun for the auto-updater built in to Fever°. (Yes, I’ll go ahead and conform to the official naming of this tool, adding the little degree symbol to the end.) Once Shaun pushes the update out, Fever° will auto-update within 24 hours. Or, you can do an instant update from the menu. Very cool, very very simple. (Here’s the changelog for V1.01.)

I’m not sure exactly what all kicked loose, because it seemed like some feeds started working even before I pulled down the 1.01 update, but since updating Fever° is kicking butt. The scrolling issues I reported in V1.0 are all fixed, and the feeds appear to all be pulling in nicely. I’m gonna run it side-by-side with Google Reader for the day to make sure they seem like they’re catching the same stuff, and if Fever° passes that test, I’ll be saying adios to GR for the foreseeable future.

Now if I could just get him to set up some sort of referral bonuses…

I’ve had a Fever install up and running for 24 hours now, and I’ve gotta compliment Shaun for working through the emailed bug reports – he responded back twice, once to acknowledge my email, and a second to ask if I had any tips on reproducing one of the errors I reported. ( I couldn’t reproduce it either.)

Where I am seeing problems, though, is in the feed updates. I thought it seemed kinda slow today activity-wise, so I just went and opened up Google Reader. Sure enough, GR has nearly 1000 unread items, just from the last 24 hours. I’ve seen maybe 200 or so in Fever today. I spot-checked a couple of feeds, and yeah, they’re missing. For instance, Andrew Sullivan over on theatlantic.com has at least a dozen updates since this morning… but Fever, even though it says it’s refreshing every 15 minutes, doesn’t have anything newer than 16 hours old.

My one fear with host-it-yourself apps like this is that all of the connectivity issues get thrown back upon the user (and webhost) to resolve – i.e. if there’s no other discernible bug, maybe it’s just something with your server. In this case, though, I think there’s something else going on.

Anybody else have any Fever reports, good or bad?

Twitter and the blogs have been abuzz today over Shaun Inman’s newest creation, called Fever. Some of you may be familiar with Shaun’s previous creation, Mint, a really nifty blog stats package that you host yourself. Inman is on familiar ground this time with Fever, creating a spiffy feed reader, full of AJAX-y goodness, suitable for hosting on your own website.

I’ve been a regular Google Reader user for years now, occasionally trying out other readers… there was that fling with Feedlounge, before it went under, and occasional dalliances with NewsGator’s line of readers… but I’ve always gone back to Google Reader. I took a look at Inman’s demo of Fever, though, over on feedafever.com, and knew it was time to give it a try.

Does the world really need another feed reader, anyway?

Creating a new RSS feed reader is no simple task. Taking accepted existing designs and improving on them requires creativity and good ideas about usability. Inman is on the right track here. But aside from the UI design, Inman has created a dual-purpose tool. On one hand, Fever is a traditional feed reader. You subscribe, it updates the feeds, you read. On the other hand, though, Fever is something like your own personal Digg. You can subscribe to all those noisy feeds, those linkdump feeds that occasionally have something interesting in them, and identify them as “Sparks”. Then Fever will aggregate them, pick out the hot topics, and present them to you in a “Hot” category, grouping them around a specific topic or link. This, to me, looks like the really slick part of Fever.

After the jump: my experience with installing Fever, importing my feed list, and some thoughts on usability and performance.