On-line Opinion Magazine…OK, it's a blog
Random header image... Refresh for more!

Haloscan Not Talking

Actually, according to Steve Bates, you won’t be able to communicate using Haloscan comments for about 24 hours.

2 comments

1 Steve Bates { 02.28.09 at 10:28 pm }

Actually, they got it going after about half that time.

One commenter on the service blog asked a very reasonable question, though: why was the crashed HD not in a RAID?

The new project leader (well, new since JS-Kit took over) has a pretty good attitude, seems to have inherited a mess, and has been completely candid in his communications with irate users (including me) about the nature and magnitude of the problem. I just hope his candor doesn’t get him fired by the new owners, who may be a bit more, um, corporate than the previous ones. (I’m speculating; I have no evidence of that.)

2 Bryan { 02.28.09 at 11:03 pm }

Given the cost of hardware, I’m having a hard time understanding why anyone doing anything 24/7 isn’t using RAID. I remember paying $800 for a 10 MB drive back when a new pick-up costs $7K, so skimping on hardware is rather foolish.

I hate mergers and acquisitions, the users/customers always get shafted.