I’ve said it before, and I’ll say it again, Microsoft’s Zune is FAIL.

In the wee hours of this morning, all of the 30gb model Zune music players hit a system glitch. A power cycle will not clear it. There are some reports that opening the unit and pulling the battery cables off the connector will clear the situation, but a lot of users won’t be comfortable with that.
This comes after the lowering of the price of the Zunes, and immediately after Apple stated that in 2009, the prices for macbooks and ipods will be dropping.
Not exactly good timing for this kind of news.

Don’t get me wrong. I wouldn’t carry an ipod, either. I’ve been using mp3 players for much, much longer than there has been an “ipod” at all, when all mp3 players were referred to as, well, “mp3 players”. I have been getting some really excellent mileage out of the small, flash memory-based ones that can now be bought for very little scratch, and for that reason, you aren’t afraid of a system fail (if it ever did happen), and you aren’t terribly worried about it if you happen to leave it in sight somewhere, and you don’t really mind wearing it when doing housework, yardwork, or even working out.

These days, they all seem to have a lot of the same features: an FM tuner, alarm clock album cycling, true random play, FM recording via schedule, etc. It really comes down to the interface on the device and the capacity, and if you follow it at all, you know that memory costs next to nothing now. The last round of flash-based mp3 players I got (maybe eight months ago) all have microSD slots, which allow for massive expansion, and allow you to swap out your stock of tunes and podcasts on the run.

To everyone with a 30GB Zune: Your music player has passed its “freshness date” Return it to the manufacturer and ask for an upgrade.

I’ve been getting back in touch with a bunch of long-lost people lately on Facebook, which is the time that Social Media is at its very best.

I’ve been running into some issues lately with several apps (not just this one) where some of the basic functionality just does not work with Opera.

I’ve been using the Opera browser as my primary for about six or eight months, and it’s like riding a rocket, but things like that are ridiculous. Opera is more standards-compliant than any other browser, and you run into things like this. First guesses would be shoddy programming by apps developers, but I’m also starting to wonder if maybe it’s something in the FB API, since there is a standard display message about it.
It might have to do with the widget framework that they were harrowing to developers. It might be worth writing an FB app just to try to hit the Opera barrier.

Have any suggestions for an FB app? Leave ‘em in the comments!

I saw the announcements for the full release of Wordpress 2.7 early, but didn’t get to check it out until a few minutes ago. The update kills some bugs, but also totally AJAXes the admin screen, adding a lot of flexibility and control, and updates the whole experience. I’m really excited with it so far. Check out the video that got me grabbing at my nearest shell session to get the update installed. If you have been blogging for a while with WP, you need this update. It’s the slickest 5-minute upgrade in WP’s fine history!

Last night I left work and trekked over to pick up the girls, and then stopped by the polling place on the way home. This is the first time I’ve taken the girls with me to the polls, so it was a bit of an education, after all of our talks a couple of weeks ago about the general election. They showed some concern, “But Obama already won, so why are you voting again?” “That was for The president and for several other jobs,” I explained. This was followed by a glossy overview of the House and Senate, and the basics of runoffs, recounts, and terms of office. They are suddenly at an age where they are reading all the signs and pointing things out that the signs say (which tells me that very soon, I’ll be explaining what the dials and lights are on the car dash, and will soon thereafter have two backseat drivers).

The traffic was really heavy in the area, and we got there about ten minutes before seven and quietly got in line. The queue seemed long at first, but moved very swiftly. We got about halfway through the line when they announced that the polls are closed, that everyone currently in line would be able to vote, but that anyone arriving thereafter would not be able to. This seemed fair, because the polls were scheduled to close at 7pm, and it was a few minutes after at that point. When we got to maybe 6th in line, there was the highly anticipated noise of a disgruntled latecomer, furious at not being allowed to vote. It was hard to make out any of the arguments outside the building, but all the expected noises were in accompaniment, including a very loud, “…in the cold to come down here and do my part!” Those of us still in line chuckled quietly as the polling officials and volunteers exchanged glances and suggested that they might need backup.