chrishubbs.com

I ordered a HDHomeRun networked tuner and a chunk of ethernet cable from Amazon on Friday morning, June 12. The tuner was ordered from Amazon proper; the cable from whichever of their providers had it the cheapest. I opted for Amazon’s super-saver free shipping, both to save the $6 and because I didn’t have enough $$$ on the gift card I was using to pay for shipping.

Additionally, I ordered a RAM upgrade for my Mac Mini from newegg.com on Tuesday evening, June 16. It came with free shipping.

Now, as to arrival times.

The network cable shipped the same day I ordered it, and arrived in the mail on the 16th. Snappy response, well done to the Amazon retailer.

The RAM shipped from Newegg on Wednesday June 17th, and arrived this morning via USPS. 5 days, including the weekend. Not bad.

Amazon finally got around to announcing that my tuner had shipped on the evening of Tuesday the 16th. So it took them three full business days to even get around to shipping it. And the USPS tracking number they gave me says that yes, they entered the tracking number into the system on the evening of the 16th. However, the arrival scan for the package doesn’t show up until the afternoon of June 19th. So between the time they boxed it up and the time they actually got it to USPS was another three business days.

Now they’re telling me that the anticipated delivery date to my home in Iowa (from, per the tracking info, someplace in Kentucky) is not until Thursday, June 25th – a full two weeks after I ordered it, and a full nine days after they told me it shipped. I know the USPS isn’t the fastest carrier, but hey, that’s just awful.

I have had better shipping service from Amazon in the past – maybe this is just a fluke. Or maybe it’s part of a strategy to dissuade customers from actually choosing their free shipping option. Either way, it’s pretty awful.

End rant. Carry on.

Tags: rants
6 Comments – Feed

Fever° Version 1.01

Posted by Chris – June 22, 2009

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…

Tags: feedafever
1 Comment – Feed

Shaun Inman’s “Fever” a day later

Posted by Chris – June 19, 2009

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?