Please show your support, and together we can bring a great show back!

Some further recommended links:

THE PETITION

Another Petition

Save jPod Digg link

The Save jPod Petition Digg Link

Digg.com is an extremely powerful tool for getting the word out. The more diggs we get, the more exposure we have, and the more power we get!

 I have a dream....

I have a dream that one day we will unite as a country to care for the deserving ones who cannot care for themselves. We will provide health care for our elderly and not force them into poverty with rising pharmaceutical prices for medicines that enable them to simply live.

I have a dream that we will welcome our military home with joy and gratitude and not force our beliefs upon them about a war they fought while we watched it on the news.

I have a dream that one day I will not fear sending my children to a public school.

I have a dream that myself and others like me can speak freely and innocently, with no malice in our hearts, and not be labeled as a person who hates simply because of the words we choose.

I have a dream that people will rise above those words thereby taking away their power to harm.

Powerful words indeed, let us remember and renew that dream.

Original Source 

However, I propose we change the name from Bluetooth to BlueHeadache, because that's what occurs when you try to connect the freaking devices. I have a Bluetooth and Wi-Fi capable PocketPC Phone (the HTC Alpine), and recently purchased Bluetooth Jabra Stereo Headphones with A2DP and a Bluetooth GPS receiver. The GPS still doesn't work after a week of trial and error, though on the bright side, it only took two days to get the headphones working! It involved a registry hack and a kernel-level patch. Seriously, you'd think it'd be marginally easier to achieve 'wireless freedom'. Its certainly understandable that ensuring compatibility with a wide range of devices is not simple, but they could have done a better job.

The way the profiles/services system looks good on paper, but when hardware vendors don't bother adhering to a more stringent set of common standards, the results are pure frustration. On top of that, there is not much you can do, because on the computer side, the components are limited in the tweaking sense, and if you're hooking up to something like a GPS receiver...well, there's really nothing you can do when the damn phone can't detect the correct serial profile for the GPS.

There are revisions, specifically Bluetooth 1.2, 2.0, and even a proposed 3.0, but they are not in consumer products yet, and it may be a while before they will be. One can only hope they managed to improve compatibility between devices. On the bright side, barring the instances when both my phone and headphones flat out refuse to work (and that happens randomly), it sure is fun having wireless audio...also disregarding the fact that it stutters when I use the phone, and when I walk out of a room. Once I managed to get the remote buttons on my headphones to work using the AVRCP profile, it is very convenient to listen to music. There is still the matter of my now useless GPS receiver though...the damn thing won't even work with my laptop's Bluetooth adapter.