Amazon customer service responded to my original request for assistance via e-mail, and began by indicating that they’d reset the download bit on the album with which I was having difficulty (my first purchase). I verified that I was indeed able to download the album, and then went back to read the additional information included in Amazon’s response. Near the top of the message:

It is not necessary that you have the Amazon MP3 Downloader installed to access your MP3 purchases. In the future, you can directly access the MP3 after your purchase by selecting the Skip installation and continue link located below the links for the Amazon MP3 Downloader. After selecting this link, you can just save the MP3 to your computer.

This isn’t news–Amazon’s support documentation and download disclaimers explain as much. However, as I read on:

If you wish to purchase an entire album, you are required to use the Amazon MP3 Downloader available for Windows XP or Vista and Mac OS X 10.4 or higher. If you initiate an album purchase and the Downloader is not installed on your system, you will be prompted to install the Downloader or cancel the purchase.

Please note, while shopping in the MP3 Music Download Store, you may encounter special album prices that are only available if you purchase an entire album. If you do not have the Amazon MP3 Downloader installed, you will not be able to complete your purchase. You will be able to buy songs on the album individually at the per-song price, but the discount may not apply.

So, customers are not required to use the downloader, but the downloader is required in order to purchase albums. And the downloader is only available to users of either Windows or Mac OS X. And even for users of these supported operating systems, the downloader will only work for those accessing Amazon.com directly (not via a proxy).

The result? Users who access Amazon MP3 Downloads via a proxy or unsupported operating system–Linux variants and FreeBSD come to mind–may be forced to pay a higher per-album price, for no good reason.

Amazon’s draw is that they offer music at lower prices than iTunes, and don’t pollute downloaded files with DRM or watermarks. Price (likely) being the primary draw, one would think that Amazon would want to make the target market for MP3 Downloads as far-reaching as possible, to include users of alternative operating systems. Because Amazon needn’t be concerned with DRM or device compatibility, they have no compelling reason to require that any client-side software be installed for any reason other than an improved customer experience (I.e., restartable downloads and third-party library imports).

UPDATE1: Seems that a Linux-compatible downloader is in the works. Not sure how I managed to miss that. Thank you, Amazon.com.

The first stumbling block presented itself because I lack the ability to think as quickly as I type (or click) early in the morning. I hit “Cancel” when prompted with the download dialog. I didn’t think much of it, and attempted to download the album again. No longer an option. Why? Because, according to Amazon’s system, I had already downloaded the album. And by “downloaded” I mean “clicked on the ‘Download’ button.” This caught me off guard.

Amazon’s Music downloads are already DRM-free–DRM being the one thing stopping the less-than-technically-adept from casually sharing iTunes purchases with friends–so attempting to control distribution via a one-time download policy seems like a silly approach. Users planning to illegally share Amazon MP3s are almost certainly not going to do so by either continuing to download new copies onto friends’ systems, or by providing friends with private account login information. They’re going to . . . wait for it . . . put the files on a USB drive, or maybe even a writable CD.

Bottom line: I’m not suggesting that every purchase be made available for download indefinitely, but a three-download limit or 24-hour window might just be a welcome convenience for a lot of users (as well as some Amazon customer service representatives).

The second issue is related to the Amazon MP3 Downloader, which they suggest that users install to make downloads “fast and easy.” Installation of the MP3 Downloader is a no-brainer. Operation is as simple as choosing the MP3 Downloader application as the file handler for downloads, as opposed to saving files via the standard operating system (or browser) dialog. I figured that I’d give it a shot, in the event that there ended up being some type of hidden benefit in terms of download management (I.e., the ability to pause and restart, or detect failed downloads). Turns out that it had the opposite effect.

I almost always use the ‘webs via a proxy–it’s a Good Idea. Unfortunately, the Amazon MP3 Downloader fails to detect any system-wide proxy configuration, nor does it provide a mechanism for manual configuration. This is all well and good if you either warn users ahead of time, or document the limitations of the tool. Unfortunately, it appears that Amazon has done neither. As of this writing, their troubleshooting guide contains no mention of proxy-related limitations (although, interestingly enough, the Google result set for ‘amazon mp3 downloader proxy’ places the relevant Amazon support page at the top of the list, and the excerpt does contain the word ‘proxy.’ Sure enough, some type of proxy-related guidance once existed!).

Bottom line: Let one of your developers spend an afternoon implementing some type of proxy support, or warn users ahead of time so that they can either find/use a proxy-free connection, or simply avoid using the downloader altogether.

On a positive note (these are, after all, relatively minor complaints, and I’m otherwise quite pleased with the offering): It appears that the Amazon customer service team is going to simply ‘reset’ the download status of this particular purchase, and I’m going to get my music. So, no harm done. Although I’d obviously prefer that these issues be addressed, primarily so that Amazon’s non-technical users might be spared a little time and frustration.

UPDATE1: The number above is now (12 Mar 08) displayed within the sidebar on TomTom’s main support page.  Their contact page (once linked above) no longer exists.

Not true karaoke, but an ingenious means by which the cab driver is able to placate festive/unruly/energetic/inebriated passengers. Perhaps more cab drivers should consider this tactic?

According to the San Pedro Daily, there are some flooded streets and lowlands, damaged piers and downed trees. But these things aside, there are no reports of large-scale structural damage or any loss of life.

A collection of photos and articles related to Dean’s affect on Ambergris Caye:

• Status of a bunch of popular spots and a thread dedicated to photos (ambergriscaye.com)
  
• Picture(s) of the day from 22 August 2007 (belizephotographs.com)
• Lots of photos and commentary in posts beginning mid-August (tacogirlblog.blogspot.com; link is to August archive)
• Images from 21 August 2007 (exploringbelizecontinues.blogspot.com)

Can’t wait to get back . . .

Ambergris Caye, Belize is probably my very favorite travel destination. My wife and I honeymooned there in 2004. The local population, downtown, and aquatic recreation are all top-notch. Part of the island’s charm is the fact that it’s small–you can drive (a rented golf cart) from one end of the island to the other in a little over an hour. Unfortunately, its small size and low elevation offer very little in the way of protection from hurricanes and tropical storms. Hurricane Keith, with sustained winds of 138 miles per hour, devastated the island in 2000. And just two years ago, Hurricane Wilma did no small amount of damage.

Today, Hurricane Dean threatens the Yucatan Peninsula and coast of Belize, including Ambergris Caye. I’m expecting that the first updates will come from the San Pedro Daily and AmbergrisCaye.com (most of the activity is in the official Hurricane forum, and the most active thread is here).

Here’s wishing the local population and remaining visitors well in the days and weeks to come.

Will someone at the Times please stop the bleeding and deliver a simple full-text feed? If your concern is that full-text feeds are going to affect your ad revenue, fear not. Most of us don’t see them now.

UPDATE1: Progress?

More worthwhile commentary on the problem:

• Update on the Censorship Problem on Flickr
• Non-nonsense about Flickr, Germany & restricted photos
• A German’s view on the Flickr censorship issue